I know a lot of people on Fedi don’t like Nostr, but I just released the latest version of HAVEN. I feel especially proud of this one, not because it’s the best, cleanest of most exiciting code I’ve ever written (It isn't), but because it’s humbling to contribute to a project that Nostr Monitors shows as representing between 8 and 13% of all active Nostr relays. Real humans running infrastructure to enable social media. I dig it.
Search results
Running a single user (or small) instance in the Fediverse? Relay instances acting as a spreading proxy can help you to find your content and also to make your posts visible to others - and you can easily join with #Mastodon, #snac and many other ones!
The https://fedi-relay.gyptazy.com relay is mostly for tech related content and just got updates to the manpageblog design.
#mastodon #snac #relay #activitypub #fediverse #federated #bsd #devops #proxmox #ipv6 #opensource #community #debian #python
We're migrating Hackers' Pub to a pretty unconventional tech stack, and I'm honestly excited about it!
Thanks to my friend @xiniha, we're diving into #Solid, #SolidStart, #Pothos, #GraphQL, and #Relay. In a world dominated by Next.js and React, this feels refreshingly different. And yes, we're sticking with #Deno instead of Node.js too.
Some might call it contrarian, but I like to think of it as exploring what's possible beyond the mainstream. Sometimes the road less traveled leads to interesting places.
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.
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).
Wir haben soeben ein #ActivityPub #Relay für das #Fediverse erstellt: https://relay.kanoa.de
Alle #MastoAdmin|s aus dem deutschen Raum sind herzlich willkommen
In some way the #Fediverse feels like the true #Metaverse of a #Cyberpunk #Dystopia. Or #Utopia?
A #consciousness stream of #hypermedia connected across #relay nodes - available for #all to see.
Are we #screaming into the #darkness? Is there #anybody out there?
#Wetware for hire, #Meatsacks for sale. Be #Whoever #you want to be - #anything to #escape from #Twitter #Hell
The #Fediverse is growing and we're welcoming more and more new single user instances but #federation can become challenging.
With #Relay instances, single user and smaller instances can quickly become federated and grow which is supported by many Fediverse applications like #snac #snac2 #Mastodon #Pleroma etc.
More information at:
https://fedi-relay.gyptazy.com
#fedi #community #fediworld #federated #opensource #fedirelay
Here is my xmas present to all the #Mastoadmin of small instances: the new #FediBuzz #relay! https://relay.fedi.buzz/