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
Ok, I already see this when I look on lemmy.world instead of my own instance so obviously something is up with my main account for some reason...
Edit: And comments appear fine too. I did have a previous Lemmy instance set up before that I messed up and deleted / started from scratch again where I had the same account name, could it be related to that somehow? Any ideas appreciated!
I seem to recall from reading a GitHub issue that a public cert and private key is generated for your user account upon creation. Once you start federating and interacting with other instances, the cert is distributed. When you delete the instance and start all over from scratch with the same username, now there’s a different public cert and the remote instances no longer trust your username.
I’ll try to find the GitHub issue that discusses this issue.
Did you purge your database when you destroyed the old instance? I'm not sure how Lemmy handles instances and databases under the hood but I suppose a database from a different instance might cause problems.
I'm fairly certain I deleted the VM and started completely fresh.
Ah ok. So the only thing left behind really is your name which again I suppose could cause problems out in the ActivityPub world but that's way too deep into the development of Lemmy for me so I'm only speculating. Basically my random theory is if @[email protected] is somehow tied to a particular instance ID and now that instance ID is different, I'm not sure how ActivityPub handles that or if that even matters.