I was introducing someone I know to #Mastodon a few years back, starting with:
"So let's find a server that suits your niche interests. What are you looking for?"
...thinking that I knew all the fedi communities pretty well.
They responded cheekily "Is there a european-foreign-policy server?"
Of course I came up short, and they ended up making an account on a generalist server.
But fedi has grown a lot since!
So happy that eupolicy.social, respublicae.eu and social.network.europa.eu exist 🔥
#ResPublicae accounts now have over 70,000 followers (not unique).
Under the hood, Mastodon keeps track of many more users who for some reason interacted with our instance. Over time that becomes rather wasteful, so we've finally activated regular data purging. Such #MastoAdmin hygiene saves us 200 GB in storage.
Our source is broken again, we'll reconsider the alternatives. (Such as self-hosting or switching to a Nitter source.)
And we're now on v3.5.10.
More information on the importance of the v3.5.9 release:
#ResPublicae has been upgraded to Mastodon v3.5.9, a security release.
The upgrade was painless. Thank you #MastoDev and especially @Claire[@]sitedethib.com for offering backports to pre-v4 releases and for the clear instructions.
While the details of CVE-2023-36459 have not been published yet, the title suggests the vulnerability may be exploitable even on an instance like ours where no third party can directly post anything.
To reduce truncation errors, we caved and increased the character limit for posts to 2000 characters.
It's easy to tell the server was a bit busier.
We're only able to get the 20 most recent posts from #RSSHub, so any account which posted more than that in the past ~2 weeks will have some posts missing. Some posts also get a bit messed up in the data conversion, so please be patient. (Most issues are already reported upstream.)
Please send patches or donations at https://pleromabot.robertoszek.xyz/pleroma-bot/!
So it finally happened. The #TwitterAPI access used to update #ResPublicae was cut off, all requests get an HTTP 401 response. Some discussion at
The list currently includes:
(Probably it's not complete. Updates can be made on the Wikidata items.)
@HistoPol Thanks! Most #ResPublicae mirrors are hosted without the original account's explicit cooperation. Hopefully, more MEPs and #EU institutions will notice the benefits of the fediverse and take the lead themselves, so at some point we become redundant.
@JohanEmpa In case you do pre-emptive blocks: lists of accounts may help.
Other possibilities exist. The principle of least astonishment could be a guiding factor:
We could mark posts from certain accounts unlisted if they regularly post to hashtags in ways which don't belong.
We could also forcefully add CWs to posts, but so far we don't. It's hard to come up with a CW which would be applicable for all accounts, or for entire classes of accounts equally. A catch-all CW like "From birdsite 🐦" is broadly correct but also potentially unhelpful.
Some accounts with no followers are sometimes considered problematic too, even though they're hard to find. Someone may accidentally stumble on something they were not prepared for.
I've surveyed a few accounts from known-controversial quarters and I've marked a few as forced-sensitive. I've also disabled mirroring RTs where they're mostly not about EU policy.
The #EuropeanParliament has a page on "Appropriate behaviour rules":
The Rules of Procedure, at Rule 10(1), state that:
«The conduct of Members shall be characterised by mutual respect and shall be based on the values and principles laid down in the Treaties, and particularly in the Charter of Fundamental Rights. Members shall respect Parliament’s dignity and shall not harm its reputation.»
Rule 176 deals with sanctions.
Admin and host of respublicae.eu. Controlled by @nemobis.
The profile and banner photos are CC-0 by W.carter and GrandCelinien.
A Mastodon forum for the discussion of European Union matters. Not run by the EU.