home.social

#ocap — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ocap, aggregated by home.social.

  1. The potential power of agents can't really be overstated. Systems that in aggregate can change the way we work at basically every level.

    People are worried about AI for damn good reasons. AI companies power their business through our private information. But it doesn't have to be that way. Fossil fuel companies do awful things to the earth, but that doesn't make electricity bad. AI companies are evil, but AI isn't bad on its own.

    If we want good AI that means good privacy, and good security. It means that a program that is there to record my voice and transcribe it doesn't need to have access to my personal photos. We need models of computing that are designed around consent, and build for small, singular tasks that compose.

    That's why the capabilities model is so necessary and we see so much work from different people and projects going into it.

    With Smart Contracts, it's necessary. With AI agents, we need it yesterday.

    2/2

    #Programming #AI #OCAP #Capabilities #Agents #SmartContracts

  2. The main idea around object capabilities, decades before cryptocurrencies and all that, was around the idea of so-called "smart contracts", which really boils down to "Code that does financial and legal things on our behalf", and the core takeaway from that was that if you don't have a serious computer security model, there's no real way to do this right.

    When I say serious computer security model, for non-tech folks, I don't mean "Install the latest virus scanner.", I mean you need complete assurance that a program that's meant to do one thing can't do something else- not "should not" or "won't try", I mean "can't", as in even if the person who wrote this program is pure evil, the thing they want to do won't happen.

    And the best way we know how to do that is the object capabilities model. It's not the only way, but we've learned in the last ~35 years that it's the only practical way.

    Now let's talk about AI and LLMs...

    1/

    #Programming #AI #OCAP #Capabilities #Agents #SmartContracts

  3. I read this article on how easy it is to make an agent and my first thought was "Holy shit that *is* easy". My second thought was "Holy shit, we need object capabilities systems *now* if we're going to live in a world with agents"

    fly.io/blog/everyone-write-an-

    #LLM #Agents #OCAP #ObjectCapabiltieis

  4. Today I set up a recurring donation to #Spritely ! I consider it an investment in a friendlier network connected software stack.
    If you're interested in #networking , #decentralization , #infosec , #ocap , or even #web3 , then it's a project worth looking into.
    Also their mascots are very cute.

  5. also found this for #sel4 #microkernel. i havent watched beyond the first lecture yet though, as i keep discovering so many more new concepts. i barely knew "object capabilites" (aka #ocap i think) before this. i thought pausing this and going back to the other series would be worth it.
    youtube.com/playlist?list=PLto

  6. Are there personal / small community org applications of #operationsResearch? :moomin_hmm:
    Something that keeps popping into my mind is: #Cybersyn but #OCAP .
    I guess #valueflows is kind of like this? But that's just a vocabulary.
    (No, cryptocurrencies are not what I'm looking for.)

  7. @nonlinear ...anywho it never seemed to me that AP even intended to be an all encompassing "seamless integration between services" but rather just the data exchange amd interaction component...the evolution of RSS into something more fully interactive if you will.

    What I think you are envisioning with "seamless integration" probably requires AP plus other open standards like #IndeAuth for authentication, something based on #OCAP like what @cwebber has long been advocating for authorizarion, and some agreed upon extensions to AP (maybe an AS vocabulary too?) to federate social graphs between instances/applications...and maybe for apps requiring better privacy and security we need to look at a rathere differewnt approach like #Veilid

  8. Watched layer8.space/@douglascrockford (youtube.com/watch?v=vMDHpPN_p0) to see if update on Misty crockford.com/misty/ new #ocap language from @douglascrockford (says vaporware in preso, so guess spec-only so far) but interesting, accounting for history, pragmatic but demanding throughout, recommended.

    Love Crockford's very low key way of dealing with questionable questions. I can wrap my mind around that!

    Hadn't really thought of EDVAC report en.wikipedia.org/wiki/First_Dr being crucial #publicdomain moment...

  9. I'm watching a documentary about a fraud involving multiple shell companies, improper circular ownership and payments, debt avoidance, multinational holdings, and more. I know that I'm showing my #CapabilityTheory and #ActorProgramming / #ocap roots here, but I'm imagining how this fraud would have been prevented by smart contracts.

    I'm not talking about blockchains! I'm talking about capability-safe actors -- hunks of program code with limited enumerated rights -- ratifying the clauses of a contract as money and control changes hands. A smart contract could have detected and prevented about half of the improper transactions outright.

  10. people keep suggesting #OCAP will solve all of #ActivityPub's problems but literally how does it solve the most basic problem of "any asshole can respond to or boost a post"

    yes i read the OcapPub article, it's incredibly vague and doesn't seem to address the issue that you don't need to be able to resolve a capability to refer to it

    what am i missing

  11. Support for magic-wormhole based invites in magic-folder is now release (still marked experimental).

    More detail here: magic-folder.readthedocs.io/en or "pip install magic-folder" and play via the command-line.

    Note you'll need a Tahoe-LAFS client for the magic-folder daemon to use. (See tahoe-lafs.readthedocs.io/en/l for that part).

    #magic-folder #magic-wormhole #tahoe-lafs #ocap

  12. Finishing my #OCAP training today on #Indigenous #Data stewardship and protection. Fun slide near the end and thanks to the #FNIGC and #AlgonquinCollege for the learning opportunity.

  13. Last was an important talk by Aaron Franks on #FirstNations #data sovereignty and #OCAP at the Canadian Open Data Society. I continue to be impressed by the depth of OCAP, and this talk gives a great overview of that framework. Anyone who deals with people data should familiarize themselves with this approach to get a sense of the investment necessary to ethically engage with people data. Highly recommend youtube.com/watch?v=8rcTI9HlDk (7/7)

  14. @birch agreed... long term blocking is not the answer. My main goal here at this point is awareness. Medium term the best mitigation is to encourage people to switch their accounts to manually approve follow requests and also for instance admins to disable automatic approval of new accounts or to disable open registrations entirely...getting into a different mindset about sharing and reach and so on.

    Ultimately the solution to these kinds of issues will rely on protocol level changes...perhaps implementing an #OCAP (object capabilities) permission model or a revamp/new protocol. The "fedi founders" aren't standing still but it will take time.

  15. One of the things I already love about the #ocap / #ocapn #spritely community is the cross-generational diversity and support: it feels like people of all ages are welcome and respected for what they can bring.