'/%3e%3cpath%20d='M50.3943%2022.237V39.5876H43.5185V22.7481C43.5185%2019.2029%2042.0411%2017.3949%2039.036%2017.3949C35.7325%2017.3949%2034.0778%2019.5338%2034.0778%2023.7585V32.9759H27.2434V23.7585C27.2434%2019.5338%2025.5857%2017.3949%2022.2822%2017.3949C19.2949%2017.3949%2017.8027%2019.2029%2017.8027%2022.7481V39.5876H10.9298V22.237C10.9298%2018.6918%2011.835%2015.8754%2013.6453%2013.7877C15.5128%2011.7049%2017.9623%2010.6355%2021.0028%2010.6355C24.522%2010.6355%2027.1813%2011.9885%2028.9542%2014.6917L30.665%2017.5633L32.3788%2014.6917C34.1517%2011.9885%2036.811%2010.6355%2040.3243%2010.6355C43.3619%2010.6355%2045.8114%2011.7049%2047.6847%2013.7877C49.4931%2015.8734%2050.3963%2018.6899%2050.3943%2022.237Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_89_8'%20x1='30.5'%20y1='0'%20x2='30.5'%20y2='65'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%236364FF'/%3e%3cstop%20offset='1'%20stop-color='%23563ACC'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
#relay
Excited to see @tor_ama host a session to answer all your burning questions about #Tor #relay operations.
https://www.reddit.com/r/TOR/comments/1krv4rt/tor_operators_ask_me_anything_13062025/
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.
Join us tomorrow for another #Tor #relay operator meetup: 
May 10 @ 18.00 UTC.
Check out the agenda and add your topics: https://forum.torproject.org/t/tor-relays-next-tor-relay-operator-meetup-saturday-may-10th-1800-utc/18771
It's time for another #Tor #relay operator meetup: Mark your calendars for May 10 @ 18.00 UTC. 
Find the agenda here and add your topics: https://forum.torproject.org/t/tor-relays-next-tor-relay-operator-meetup-saturday-may-10th-1800-utc/18771
#ActivityPub #Relay #Fediverse
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).
Design Constraints Bring Lockbox to Life - One of the most paradoxical aspects of creating art is the fact that constraints, ... - https://hackaday.com/2025/04/27/design-constraints-bring-lockbox-to-life/ #passivecomponents #combination #woodworking #lockbox #keypad #relay #lock #art
How a Tiny Relay Became a USB Swiss Army Knife - Meet the little board that could: [alcor6502]’s tiny USB relay controller, now evo... - https://hackaday.com/2025/04/05/how-a-tiny-relay-became-a-usb-swiss-army-knife/ #microcontrollers #swissarmyknife #computerhacks #linuxhacks #swissknife #pcbhacks #boot0 #relay #servo #stm32 #news #uart #usb
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
This is an Activity Relay for fediverse instances.
You may subscribe to this relay with the address: https://relay.adtension.com/actor
To host your own relay, you may download the code at this address: https://git.pleroma.social/pleroma/relay
A topical or community Fediverse Relays — ex: a Paleogenetics relay server, or an animal photography relay server, or a company focused relay server, etc —
Would be similar to the old PlanetPlanet river-of-news feed-reader blogs.
https://web.archive.org/web/20171029175722/http://www.planetplanet.org/
A topical or community Fediverse Relays could be very useful (in addition to generic ones).
Ex: a Paleogenetics relay server, or an animal photography relay server, or a company focused relay server, etc
Especially for single-user, community, team, organization, themed, etc server instances
It would also help save storage space on server instances, by the relay being selective in what it shares.
New video! I'm hacking an automotive relay into my desoldering station to circumvent the long wiring activating the vacuum pump.
YouTube: https://youtu.be/bUXVoJblRGA
PeerTube: https://makertube.net/w/iic1m8JD1K3Mo1fxMvc7Dz
A question to all the #fediverse people #selfhosting their instance or being a part of a small one:
Are you joined with any #relay? I was thinking of that, but I don't know if it's a good decision.
That’s why Azzamo is building a global network of reliable, fast relays across multiple continents.
Europe: wss://relay.azzamo.net Americas: wss://us.azzamo.net Asia: wss://asia.azzamo.netWhere are you connecting from? Drop your country below!
#Azzamo #grownostr #paidrelay #relay
The #Fediverse is free, free of censorship, federated and full of great content!
Also the Fediverse - instance admins randomly blocking whole instances just because a single users feel offended of a post by a single instance user. Blocking whole instances is just a finger snip away, censoring unwanted content and parenting users of instances. Defederating just because of… ok no clue :) Using content warner for any possible content just to annoy or aeemmm make it more interesting to other users. Thanks, I’m old enough :) Seeing all the spam because it’s just a thing of 5 minutes automation to create randomly new instances on different domains (or subdomains from dynamic-ip hosters) and to fill the network with automated content.
Sometimes, pros can easily switch into cons… luckily more and more single user instances are raising up for exactly this reasons and can still easily federate by using relays…
One thing I like about that period in which the System Operator could literally see what you typed; the Age of UUCP and Usenet, way before www, is that there was something on those federated networks that we shall not easily get nor easily gain again;
**TRUST**
Inherited Trust of the period was so beautiful. All the Networks are open and there were no trolls that could do any real damage.
Many decades have gone by, but I've now finally had contact with an actual Operator of a Usenet node. Thank you for your reaction
Do understand that all federated networks need relays, many, so that reach is increased, otherwise you'll end up having to wait hours to days before posts reach wider audiences
Excerpt:
{
One of the biggest advantages of relays is that they help smaller instances thrive. When a new or niche server joins the Fediverse, it often starts as a quiet place with limited interaction. Relays can dramatically change this dynamic. By participating in a relay, a small server’s content reaches a larger audience. This doesn’t just give more visibility to the server – it helps its users feel more integrated into the broader Fediverse community. People are more likely to stay active on their instance when they see others engaging with their posts.
}
Low reachability means you will have to wait long times, just like I did in the UUCP days. We could only afford one dialup session of 60 minutes per week to upr2.clu.net.
So our reach / ping time was 7 days!!!