shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

#relay

0 posts0 participants0 posts today

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

graphql.orgGraphQL | A query language for your API

My relay instance for the #Fediverse evolved in a great way - more than 120 instances are already connected to boost your posts across the Fediverse.

If you're running #snac / #snac2, #Mastodon, #Pleroma or any other software on the #ActivityPub protocol that supports relay instances - feel free to join the relay! Hopefully #GoToSocial also supports relay services soon! Of course #IPv6 is supported (for IPV6 only instances).

fedi-relay.gyptazy.com

Continued thread

@torproject same with #obfs4 bridges: there is no option to say like ports=80,443 or similar, which makes it cumbersome to get said bridges.

And trying to get places to #DontBlockTor that criminalize the use of #Tor is foolish at best.

I've just been notified that one of our production servers is going to be relocated to a different data hall by our infrastructure provider with about 2 weeks notice. Annoyingly it's the server that runs 3 of our web nodes for MastodonAppUK, Universeodon and the Universeodon relay.

I'm not expecting this to cause any public disruption, but will be spending this weekend getting things ready so I can migrate the traffic over prior to the server move happening. There may be some short notice maintenance over the coming weeks to ensure I can accommodate this and it doesn't cause an outage on move day.

Continued thread

Comme mentionné dans le post précédent, les actions ont démarré avec l'ajout de marque-pages et stickers contre #Bolloré dans les livres #Hachette (dont #Vivendi est l'actionnaire majoritaire) des magasins #Relay dans les gares de France.

desarmerbollore.net/news/opera

Pour les journées d'actions contre l'empire Bolloré, vous pouvez reproduire ce geste simple dans le Relay le plus près de chez vous. La note interne dévoilée par des personnes employées chez Relay témoigne de l'efficacité du geste !

La carte des maisons d'éditions, médias, réseaux sociaux, points de diffusion appartenant au groupe Bolloré : desarmerbollore.net/news/carte

It appears that my Mastodon server relay connection to infosec.exchange is no longer functional... no content being delivered for a few days. I know that site has been experiencing problems of various kinds based on posts from @jerry, as operating large Fediverse instances is challenging.

Any suggestions for relays I should I use instead? I'm not looking for a 'whole Fediverse' feed (like mastodon.social), but sites that carry a wide selection of tech traffic would be useful.