@9e40c531 Yeah, I've started to dig in to it a couple of times, but have always got caught against that coordinator bit. I'm pretty sure you can run your own coordinator, but the documentation is all written to use theirs (I imagine using their coordinator is part of their revenue structure).
@Dissident Sound Depends on your ISP.
I work for a small ISP that will happily give out static addresses and subnets (for a cost). But some ISPs are restrictive.
If you have the technical knowhow, you can use a dynamic DNS service like DynDNS to help even in the absence of a static IP. Or you can use something like ngrok. The solution I'm building is in line with the latter (but specialized to ActivityPub).
@b05df304 there's a lot that can be done statically: webfinger, collections (followers, following), user profiles, outbox. I can see how that would be useful for folks. Have you written up your methods?
One of the challenges that I'm working on is empowering people with consumer-class internet access (i.e., dynamic addresses) to run their own Fediverse servers. The Publish/Publisher and websocket components I've added to #SofaPub move in that direction.
This allows someone with broad connectivity to re-publish connections from users who are more limited.
This is a big addition and I haven't published it to crates.io yet. But the code is at https://gitlab.com/justindthomas/sofapub.
#ActivityPub #Rust
https://ser.endipito.us/system/media_attachments/files/111/186/104/001/187/366/original/0319a0a19831f065.mp4
Notes by Justin Thomas 🛡 | export