c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.7K
active users

Really, #Europarlement, I see nine social media buttons at the bottom of your site at:

europarl.europa.eu/portal/en

All to non public values driven, #privacy disrespecting #socialmedia platforms.

How is it possible that there is no #Mastodon button? Mastodon the only truly decentralized, public value driven, #opensource and independent social media platform.

How wil the #EU reach #DigitalSovereignty and #StrategicAutonomy when its #parlement gives such a bad example.

Practice what you preach!

@janvlug I too look forward to all such similar non-US gov't bodies gaining trust in , strongly favoring it over US platforms like X, Bluesky, etc.

I'm a , and want to see more Canadian gov't agencies spreading their wings on Mastodon. Or other such , federated services, after *thoroughly testing it for the suitability* to their needs: eg. , , and .

I myself will probably install my own Mastodon server some day, however when I look at all the possible servers today (ruby-based Mastodon, Misskey, etc), I'm not too happy with the *packaging* of the software. Where are the packages for all these servers? I'm hoping that eventually will do more for their software packaging - that one seems the most appealing. I have a need that the maintenance must be made easier and reliable for the sysadmins/devops administering it at the server level, *with easy security updates*.

@sbb @janvlug

I haven't looked into hosting Mastodon (and have no plans to do so.) But if I were, the first thing I'd look for would be Mastodon in a Docker (or similar) container. It's easier to get current updates and you can even automate that with Watchtower (though I haven;t tried that either.) My containers are all strictly local so I don't need to worry as much about security updates and update occasionally for features.

#Debian fan here, BTW.

Bhante Subharo :xmpp:

@HankB @janvlug Also BTW: relies on several certs (e.g. chat.domain.com, conference.domain.com, upload.domain.com, proxy.domain.com); is really annoying to self-host on a LAN. auto-renewing these in the cloud is much more sane.

@sbb @HankB @janvlug You can have a single wildcard cert covering all those names... Also consider using `example.com` when needing a fake name.