News for hackers. Stuff that matters.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by Velocifyer on Wednesday September 23, 2026 @12:06PM (#49818184)
My main wish is if radicle had a way to make issues online, without installing the software. Runing a piece of software is a high barrier of entry to make a bug report, which the entire reason I use codeberg instead.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by someonebaggy on Wednesday September 23, 2026 @12:32PM (#49818648)
That's a downside of all decentralised software, isn't it? If there's a convenient access point, that access point is also a point of centralisation. To be distributed, you have to be running the software yourself. The big problem is that the software always ends up being inconvenient. People have no problem using bittorrent because the software is actually usable.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by tancop on Thursday September 24, 2026 @02:08AM (#49826810)
> If there's a convenient access point, that access point is also a point of centralisation

I don't think that's true. Bitcoin and Ethereum are very decentralized but most casual users don't run a node and do everything with a gateway. ATProto/Bluesky is the same.

What they have in common is shared global state, using a blockchain or PLC. That means everyone gets a full view of the network (outside of censoring relays) and user account are portable. You can go with a commercial provider for convenience but always have the option of self hosting if they raise prices or censor you.

That option is more important than the share or users who self host right now.

Re:Radicle: Disclosure of Vulnerability in the Network Protocol by someonebaggy on Thursday September 24, 2026 @06:55AM (#49828876)
Ethereum is an interesting case for this, because there's a default node address in Metamask, and that's obviously the one that most people are using. It also costs money, forcing enshittification.

Not sure about bitcoin - I run my own node for that (as I said, running the software). If you have a light client I think you have to have your own server?

Look at IPFS though. Extremely slow to access files but since everyone used ipfs.io gateway which cached all files ever accessed, nobody noticed the underlying decentralised system actually sucked.

Re:Radicle: Disclosure of Vulnerability in the Network Protocol by Groxx on Wednesday September 23, 2026 @01:15PM (#49819375)
Like onion/ipfs/many others, I'd expect gateways to pop up if it grows relatively popular. If LLM scrapers don't destroy them immediately, at least.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by hirako2000 on Wednesday September 23, 2026 @02:07PM (#49820148)
They have public repositories on GitHub.

https://github.com/radicle-dev

Re:Radicle: Disclosure of Vulnerability in the Network Protocol by AuthAuth on Wednesday September 23, 2026 @03:10PM (#49821008)
My main wish is a way to search the repositories on a node. Or a way to have tags. The whole network is like a blackbox of projects unless you can get an outside link.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by gsaslis on Wednesday September 23, 2026 @04:41PM (#49822265)
If the node runs an HTTP API (radicle-httpd) backed by an indexer (radicle-search), you can.

Try https://radicle.network/explore and set index.radicle.garden as your search seed.

Re:Radicle: Disclosure of Vulnerability in the Network Protocol by maninak on Wednesday September 23, 2026 @04:57PM (#49822481)
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by AuthAuth on Wednesday September 23, 2026 @06:48PM (#49823696)
Thanks this is exactly what I was needing.
Re:Radicle: Disclosure of Vulnerability in the Network Protocol by 2color on Thursday September 24, 2026 @04:46AM (#49827974)
We have a prototype demonstrating writes from the web:

https://radicle.zulipchat.com/#narrow/channel/369278-Explore...

This is definitely on our radar.