this post was submitted on 25 Jul 2023
48 points (96.2% liked)

Selfhosted

40113 readers
996 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
48
If I were to set up a self hosted Gitea instance right now, how would I be impacted down the line when they implement federation? (lemmy.world)
submitted 1 year ago by Kalcifer@lemmy.world to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

Would I have to do anything on my end, or would everything be set up automatically when the update is pushed?

you are viewing a single comment's thread
view the rest of the comments
[–] ShittyKopper@lemmy.blahaj.zone 0 points 1 year ago* (last edited 1 year ago) (2 children)

You'd have to be significantly more careful with backups, as it's really easy to effectively "burn" a domain from federating over AP ever again (at least to instances that federated with it before), but otherwise it should be reasonably automatic as federation gets implemented piece by piece.

[–] SomeRandomWords@lemmy.blahaj.zone 3 points 1 year ago (1 children)

As someone who has very little experience with ActivityPub but is always interested in learning more, what's the risk of "burn"ing a domain? Does it come from certs or signatures changing on the same domain, causing it to no longer be accepted or something?

[–] ShittyKopper@lemmy.blahaj.zone 1 points 1 year ago

it's partly because everything has public/private certificates, but also partly because there isn't much synchronization going on after the initial "push". if you shut an instance down and modify the database directly without informing other instances (say, you remove an account) then other instances will not be able to tell and will drift out of date, essentially making that specific thing unusable for any instance that has previously interacted with it. if you expand that out to, say, wiping and re-creating an entire database, then you end up with so much uncertainty that you may as well start over from a fresh domain

[–] SomeRandomWords@lemmy.blahaj.zone 0 points 1 year ago

As someone who has very little experience with ActivityPub but is always interested in learning more, what's the risk of "burn"ing a domain? Does it come from certs or signatures changing on the same domain, causing it to no longer be accepted or something?