Hacker News Reader

This is a joke. I think people just use the word decentralised as a blunt and nothing else matters. No access control, no problem it is decentralised. No content filtering, no problem it is decentralised. And so on. Decentralised is the new religion.

View on HN

There already is access control. Only admins can accept patches, for instance (though a bug we've just made a fix for [0] meant if someone else tried doing it the entire patch system for that project would break). Programmatic content-filtering is really the bread-and-butter of Radicle. Ad-hoc content-filtering is a bit harder, but as I mentioned elsewhere still possible.

[0] https://github.com/radicle-dev/radicle/pull/552

Where do you store who is ad admin?

We store their public key on the machine. They can add (or remove) admins. Every input is signed, and (when relevant) the author is checked for authorization.

What if I need more fine grained access control?

Radicle is a full-fledge (fledling of a) programming language, so you can really do as you wish with access control. Here's the module for authorization [0], and in this module [1] you can see an example of it being used.

[0] https://github.com/radicle-dev/radicle/blob/master/rad/prelu... [1] https://github.com/radicle-dev/radicle/blob/master/rad/monad...

Reply on news.ycombinator.com