The two measures for voting on blocking AI bots to composr.app and prioritising the v11 branch on our git repositories have closed. Read more for the results.
I read the release notes for 11 beta8, but didn't even know these measures were in voting, I guess since they weren't mentioned in the news there. I suppose it's fair to mainly want voting to be done by people who are actively engaged and checking the forums.
Hello. I sent out a mass newsletter about it to all composr.app members and everyone who subscribed through the install screen of Composr CMS. Did you not receive it? If not, I'll see if something went wrong (and please let me know if you're getting other types of e-mails from the site).
Sorry for the late reply. I'm getting notification e-mails for comment replies, so e-mail in general from the site is working for me. I did not previously have "New blog/news article added" e-mails enabled, and I just enabled those now. But I was already signed up for "Receive newsletters and other site updates," and I definitely didn't receive a mass e-mail about the measures.
Sorry for the late reply. I'm getting notification e-mails for comment replies, so e-mail in general from the site is working for me. I did not previously have "New blog/news article added" e-mails enabled, and I just enabled those now. But I was already signed up for "Receive newsletters and other site updates," and I definitely didn't receive a mass e-mail about the measures.
Hello. I checked into it.
Unfortunately, I cannot determine directly if the newsletter went out to you or not because mail logs do not go that far back.
However, I did find something interesting. There might be a bug in the newsletter system. Your e-mail address does not show up in the list of "Send to site members" subscribers on the back-end even though you have an e-mail set and you have "receive site newsletters" ticked on your profile.
I am going to look into this. If it is indeed a bug, I'll fix it. And then I will also have to revoke the results of those polls since it's very likely other people didn't get the e-mail either… and we will have to re-conduct voting on those measures.
I found two reasons why you didn't get the e-mail:
1) A bug in Composr (now fixed on composr.app; will be pushed to 11 beta9). The newsletter system was respecting the setting for allowing e-mails from other members… it should have been respecting the setting for allowing e-mails from staff.
2) My server had issues sending e-mails to you. I'm not sure why. Gmail is complaining my server has an invalid PTR record. But I ran a test by sending an e-mail to my own Gmail account, and it worked just fine.
…I just overrode the bounce and sent a test e-mail to you. And it seemed to went through that time. So it might have been a one-off issue.
I can confirm I received your test email this evening. Like I said, I've gotten plenty of other e-mails from the site in general. Not sure what's going on with the PTR record, but all of the SPF/DKIM/etc appear to have checked out on the emails I received tonight. Glad to hear you located and fixed a newsletter bug! Thanks for looking into it.
News: Results of two measures
The two measures for voting on blocking AI bots to composr.app and prioritising the v11 branch on our git repositories have closed. Read more for the results.
Unfortunately, I cannot determine directly if the newsletter went out to you or not because mail logs do not go that far back.
However, I did find something interesting. There might be a bug in the newsletter system. Your e-mail address does not show up in the list of "Send to site members" subscribers on the back-end even though you have an e-mail set and you have "receive site newsletters" ticked on your profile.
I am going to look into this. If it is indeed a bug, I'll fix it. And then I will also have to revoke the results of those polls since it's very likely other people didn't get the e-mail either… and we will have to re-conduct voting on those measures.
I will update you.
1) A bug in Composr (now fixed on composr.app; will be pushed to 11 beta9). The newsletter system was respecting the setting for allowing e-mails from other members… it should have been respecting the setting for allowing e-mails from staff.
2) My server had issues sending e-mails to you. I'm not sure why. Gmail is complaining my server has an invalid PTR record. But I ran a test by sending an e-mail to my own Gmail account, and it worked just fine.
…I just overrode the bounce and sent a test e-mail to you. And it seemed to went through that time. So it might have been a one-off issue.