Mark Wieczorek

I am so sick of #email.

Email clients are getting worse. Messages aren't being delivered because of "spam filtering". Email providers refuse to explain why messages aren't delivered when the raw email is fine. There is a high percentage of DKIM failures on microsoft-run servers. US government addresses have high rates of DMARC failures. And it is impossible to run your own email server if you care about deliverability.

How is this going to end? Will we fix email, or switch to something else?

RE: @hannorein@mastodon.social

If the AAS can afford to pay a ridiculous salary like this for a CEO, they can certainly make their publications and job announcements website free to the community.

@numerique_gouv@social.numerique.gouv.fr Où se trouve votre serveur peertube ?

@RGrunblatt@social.sciences.re @numerique_gouv@social.numerique.gouv.fr Merci ! je ne savais pas qu'il en avait un. Je viens de lui demander si le @numerique_gouv@social.numerique.gouv.fr pourrait héberger d'autres chaines, comme pour @cnes@social.numerique.gouv.fr

@65dBnoise@mastodon.social @blog In general, I would expect that most images in a blog post be original. I think our biggest problem is simply for the cover image. We require a cover image (for consistency with our template), and the cover image is sometimes just filler with little meaning. AI is also filler with no meaning.

If we were to attribute a DOI (we plan on doing this later), then I'd have no problem in using the same AI policies as for our journal: https://planetary-research.org/use-of-artificial-intelligence

@65dBnoise@mastodon.social @blog At the present time, illustrations are user provided and blog posts are unmoderated. We also have zero budget for illustrations, and no illustrators have contacted us to provide such a service for free (I have already asked science illustrators with no luck).

I am actually looking for advice on how to deal with this. The blog could explicitly prohibit AI imagery, we could discourage it, or have better transparency.