• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: April 9th, 2024

help-circle

  • iltg@sh.itjust.workstoSelfhosted@lemmy.worldContinuwuity
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    2
    ·
    20 hours ago

    while i don’t want to throw shade on the developers’ intentions, nor have any real proof of what data is being kept, a fetch request bears by minimum the source ip (which can be geolocated) and the fact that the homeserver exists and runs continuwuity.

    i’d suggest a matrix channel as alternative, so hosters can opt-in by joining. plus, by leveraging the matrix protocol, such announcements become federated push notifications, meaning they could come from any homeserver (limiting ip logging) and don’t imply the continued existence of such deployment, or the software which is being run

    even converting such mechanism to an opt-out “auto-join announcements channel” would be more privacy respecting






  • why wouldn’t it be? you can send emails from web uis too. you can share diffs however you desire. you can have a remote for each developer, and push/pull changes to each other. the github mindset kind of ruined the resilience and distributedness of git: one central remote, one account authority, one central place where discussing MRs… ever forgejo is not as good as decentralized git: what’s a forgejo identity?

    meanwhile git has been decentralized and distributed since day one, linux is still developed in a decentralized and distributed way and forgepub is just not ready and not even close.

    sending emails with an attached diff to many ppl is too hard? make a nice offline gui doing that and we’re distributed. github was a psyop to make us un-learn git, making it better is silly, like wasting decades searching for “good cigarettes”