Just wanted to chime in on mention of ACL's (but by no means an expert).
In a W3C mailing list post which @cwebber called "Maybe the most important thing I've ever written (at least about computing)" ...
https://octodon.social/@cwebber/105330906551541225
https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html
... there's a section called "ACL's considered harmful" and reference to this PDF paper:
https://waterken.sourceforge.net/aclsdont/current.pdf
Christine since started https://spritely.institute and is working on #ObjectCapabilities and #OCapN.
#Twitter is just another example of why Ambien authority is bad. *ba-dum-tss*
#CapabilityBasedSecurityJokes #ObjectCapabilities #OCaps #OCap
#twitter #capabilitybasedsecurityjokes #objectcapabilities #ocaps #ocap
@aral @cancel there's some recognition and of a possible solution to this problem using #objectCapabilities #ocaps #ocappub
https://gitlab.com/spritely/ocappub/blob/master/README.org
#objectcapabilities #ocaps #ocappub
Note that there are different approaches than ACL, most notably #Spritely working on #ObjectCapabilities
Christine Webber once tried to reach out to #Solid team to talk pros and cons, but there was no real interest or response to that.
https://forum.solidproject.org/t/solid-acls-and-the-future/3489
#spritely #objectcapabilities #solid
Though there's a lot of nice info on that page, but technically it should be considered "deprecated" and work continued at https://spritely.institute
But it is very exciting stuff. I recently introduced #Erlang / #Elixir community to it, and asking for #ObjectCapabilities impls in these languages.
https://elixirforum.com/t/elixir-and-object-capabilities/52311
#erlang #elixir #objectcapabilities
Though probably incredibly busy with a release tomorrow.. having seen that @josevalim is on the #Fediverse (welcome 👋 ) maybe I dare to gently ping about #ObjectCapabilities plus https://spritely.institute and https://spritelyproject.org by @cwebber et al.
It feels to me that #Erlang / #Elixir of all languages shouldn't miss out on exciting new paradigms like this.
Here's repost of the URL where I gave a heads-up to Elixir forum: https://elixirforum.com/t/elixir-and-object-capabilities/52311
#fediverse #objectcapabilities #erlang #elixir
The old #Erlang implementation of Cap'n Proto protocol may also give some clues.
I pinged the developer for awareness of #Spritely work: https://github.com/kaos/ecapnp/issues/6
Though https://capnproto.org will need to be adjusted to comply with #Goblins later on, it is a mature #ObjectCapabilities implementation currently in use.
#erlang #spritely #goblins #objectcapabilities
Anyone know of #Erlang or #Elixir projects that entered the realms of #ObjectCapabilities?
https://elixirforum.com/t/elixir-and-object-capabilities/52311
Thinking of #Spritely in the back of my head :)
#erlang #elixir #objectcapabilities #spritely
Anyone know of #Erlang or #Elixir projects that entered the realms of #ObjectCapabilities?
Thinking of #Spritely in the back of my head :)
#erlang #elixir #objectcapabilities #spritely
I'm starting to read ideas about using #ObjectCapabilities to manage harassment on the fediverse. I'm pessimistic so far, although I could be surprised.
Specifically, I think OCaps will be effective at stopping people from punching down, but will also prevent spontaneous connections and stop people from punching up. That would be fine for a Facebook replacement, but not a Twitter replacement.
I'm aware not everyone wants a Twitter replacement, but I'll still be on the network that is one.