@jwildeboer Is forgefed far enough along already that instances are already federating PRs and the such? I was under the impression it's still very much WIP.
Dear GitHub users. Forgejo exists (and is the software behind Codeberg). Radicle exists. Sourcehut exists. You’re welcome to join! And with forgefed we also have a federated approach. We were building all of that while you were sleeping ;) Maybe you are now ready to help us build a better, more decentralised code sharing future?
To avoid self-hosting a full-fledged code forge, you might want to simply store issues in the git repo itself. Have you tried using git-bug, git-issue, or some other decentralized bug tracker?
* https://github.com/git-bug/git-bug
* https://github.com/dspinellis/git-issue
Last time I tried git-bug I failed to import my issues from GitHub and gave up, but maybe it works now, it seems there is a new & more active maintainer.
#GiveUpGitHub #git #BugTracking #issues #SelfHosting #GitBug
@glyph Here's the thing! Red means the two nodes don't have accurate information about each other and green means they do. Random nodes connect every 2 seconds to sync and gossip sync state with each other. Then a random node updates every 4 seconds.
https://ranger.mauve.moe/comapeo-state-gossip-sim/
Source: https://github.com/RangerMauve/comapeo-state-gossip-sim/tree/default
@glyph Here's the thing! Red means the two nodes don't have accurate information about each other and green means they do. Random nodes connect every 2 seconds to sync and gossip sync state with each other. Then a random node updates every 4 seconds.
https://ranger.mauve.moe/comapeo-state-gossip-sim/
Source: https://github.com/RangerMauve/comapeo-state-gossip-sim/tree/default
@burnitdown @anildash @forgejo From what I understand speaking to folks like @rabble the Nazi problem is less of an issue than you'd expect on the major apps/relays.
I don't think it's fair to assume the worst of everyone or think there's one size fits all for users of a platform/technology. It's okay if the risk is too high for your needs but it is not quite as extreme as you seem to be assuming.
@burnitdown @anildash @forgejo So is the fediverse depending on where you go. 😅 Nostr is more known for bitcoin maximalists. They're defs less strict about moderation on public relays compared to fedi instances. It's a fundamentally different dynamic to fediblocking though IMO.
@anildash I really hoped that the federated code collaboration stuff GitTea / @forgejo have been working on for years would be more widespread by now. Or even the Nostr stuff so we wouldn't need to tie identity to servers. https://nostrgit.org/
I'm personally working on migrating to https://radicle.xyz/
@glyph Yeah sure! This is for my work on comapeo: https://github.com/digidem/comapeo-core/issues/1016#issuecomment-3161858309
We want to keep track of when a remote archive server knows it's been removed from the group so we can stop bothering to sync with it.
Gosling: Build Anonymous, Secure, and Metadata-Resistant Peer-to-Peer Applications using Tor Onion Services has been released on media.ccc.de and YouTube #why2025 #Wonderfulcreations #Brachium #why2025eng https://media.ccc.de/v/why2025-95-gosling-build-anonymous-secure-and-metadata-resistant-peer-to-peer-applications-using-tor-onion-services https://www.youtube.com/watch?v=jRBP3AO3iq4 https://program.why2025.org/why2025/talk/TMS3DC/
@lutindiscret @c3voc_releases @VeilidNetwork This is new to me, ty for the link!
remember when gtk had themes other than "landlord gray" and "landlord gray but with the lights off"? i miss that
@kayla Yeah! @distributedpress and @sutty
We made a minimal AcrivityPub inbox you can use in your static site generator flow, and your site becomes the ActivityPub identity. Also got moderation features lole blocklists/allpwlists and approval queues.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Yap with me and send me cool links relating to my interests. 👍