Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
That seems like an oversight. ActivityPub should rely on some sort of certificate or cryptographic signature instead of a domain which might have to occasionally change.
ActivityPub does use cryptographic keys for Actors ("users" in this case) - so even in theory if you were to destroy your instance and then set it up on the same domain and recreate the user, things would be quite broken still... But unfortunately it still does rely on the domain name itself, so I agree.
I think the problem is, without the domain name, there is no way for you to lookup who
@russjr08would be, or where to send data to them. The domain effectively acts as a mailing address (a well suited analogy considering that ActivityPub also uses inboxes/outboxes) so that Instance A always knows that User B can be found on Instance B.I doubt its an impossible challenge to solve, but probably quite a difficult one I'm sure.