Posts by by_caballero@mastodon.social
 (DIR) Post #AS0cg72MDLjZpUjq3U by by_caballero@mastodon.social
       2023-01-25T15:58:21Z
       
       0 likes, 0 repeats
       
       @silverpill have you given any thought to making a monero snap for metamask rather than rolling your own browser extension? they even have a grants program, although that might be flooded with competition at the moment
       
 (DIR) Post #ASuvJLT6IgV137bkJ6 by by_caballero@mastodon.social
       2023-02-21T21:46:28Z
       
       0 likes, 0 repeats
       
       @seldo also lowkey plagiarism, another cornerstone of white-dood culture
       
 (DIR) Post #AYphcsfR7hkHLz2Ch6 by by_caballero@mastodon.social
       2023-08-17T20:33:09Z
       
       0 likes, 0 repeats
       
       @wjmaggos @emilymbender does the phrase "linux kernel mailing list" evoke any cultural conditioning that might be pertinent here?
       
 (DIR) Post #AYuq4SSLwJGdarNKFs by by_caballero@mastodon.social
       2023-08-20T08:00:47Z
       
       1 likes, 0 repeats
       
       @filipesm @grillchen @molly0xfff while escrow dynamics are pertinent in many fund-raising cases, the "quadratic" scheme is actually more like many-X fund-matching based on crowd-dynamics. the Radical XChange folks (Glen Weyl et al) are responsible for getting the gitcoin crowd psyched on it, AFAIK.
       
 (DIR) Post #AjHrqxu2LONZxSPxPk by by_caballero@mastodon.social
       2024-06-19T10:16:57Z
       
       0 likes, 0 repeats
       
       @ariadne Hey, I generally agree with this whole thread but i'm lacking context. which primitives do you mean?  Does "notarization" mean moderation metadata per-post? Is this about follower-only publishing or follower-only replying?
       
 (DIR) Post #AjHrqyzOIyFxKLvkOm by by_caballero@mastodon.social
       2024-06-19T10:18:13Z
       
       1 likes, 0 repeats
       
       @ariadne I think it's easier to get better authN/authZ layering and primitives built into other implementations first, and get Masto to at least honor/parse/display those properties SECOND (might require paying someone to make the masto PR?). The THIRD step, getting masto to offer its users the same privacy model internally/natively is a multi-yr project, tho.
       
 (DIR) Post #AjHrr0wd2DEdOMeZN2 by by_caballero@mastodon.social
       2024-06-19T10:19:03Z
       
       0 likes, 0 repeats
       
       @ariadne (hopefully this comes across as violently agreeing and not as mansplaining your own thread back to you 😅)
       
 (DIR) Post #AjLnGN68pAbofHbGnQ by by_caballero@mastodon.social
       2024-06-27T10:47:59Z
       
       0 likes, 0 repeats
       
       @smallsees @erlend @dmitri Ideally yes, target state is "status quo", but it's a little unknown how many of today's implementations accidentally hard-code assumptions to the contrary.  The reason we worked on a Roadmap first and broke out just the Actor-independent URL part second is to make *explicit* and *testable* behavior that should already be possible in ActivityPub's specification of the Actor Object... but maybe not always in practice today.
       
 (DIR) Post #Am5bsMVcIGADtTIdW4 by by_caballero@mastodon.social
       2024-09-17T09:01:06Z
       
       0 likes, 0 repeats
       
       @aral oh, you mean Larry "billion-dollar investor in saudi-xitter" Ellison?https://variety.com/2022/digital/news/musk-twitter-larry-ellison-financing-1235258991/
       
 (DIR) Post #An2g7xOGGiH79TSFe4 by by_caballero@mastodon.social
       2024-10-15T18:05:54Z
       
       0 likes, 0 repeats
       
       @arcanicanis @silverpill @bnewbold @erlend sadly there isn't much support for DID URLs in the wild, as that whole set of features is optional and few DID method specifications even mention (whether mandatory or optional) how implementations could dereference DID URLs... I would mention that one of the formal objections complained about this unspecified behavior and thus the DID WG has prioritized the DID Resolution spec, which might help a little:https://w3c.github.io/did-resolution/#dereferencing
       
 (DIR) Post #An2g7yYZvq7cllI0Mi by by_caballero@mastodon.social
       2024-10-15T18:07:14Z
       
       1 likes, 0 repeats
       
       @arcanicanis @silverpill @bnewbold @erlend One useful piece of prior art to look at would be did:cheqd, both the method and the production implementation (and maybe even the veramo plug-in!). the cheqd team has really been driving a lot of the effort to do something grown-up with DID URLs in prod and in standardized ways...https://docs.cheqd.io/product/sdk/veramo-plugin/did-linked-resources
       
 (DIR) Post #An2g80Q90AZ0YBMIUq by by_caballero@mastodon.social
       2024-10-15T18:13:13Z
       
       1 likes, 0 repeats
       
       @arcanicanis @silverpill @bnewbold @erlend FEP-e3e9 snuck in "DID URL syntax" to a standalone "permalink service", such that everything after the ? would model what a DID-URL permalink for nomadic content could look like; what comes before the ? is a traditional HTTPS URL in the FEP, but could also be a gateway that takes a DID as a path... (i.e. https://indexer.example/did/plc/53ogl5ixuq44t73wuqawpa33?...)
       
 (DIR) Post #AnEzugI8rM2jKw3gbQ by by_caballero@mastodon.social
       2024-10-21T18:46:33Z
       
       0 likes, 0 repeats
       
       @silverpill @arcanicanis @erlend @bnewbold why is support for more did methods an assumed goal? for whom and in which use cases is a non http protocol handler justified? why is did:key important? why is ap:// the best possible url scheme for the AP protocol? it feels like we're talking at a general level and yet so many usecase-specific requirements and goals keep sneaking in
       
 (DIR) Post #AsOHUV5axkh1sGBwlE by by_caballero@mastodon.social
       2025-03-24T19:43:33Z
       
       0 likes, 0 repeats
       
       @silverpill @darius forgive me for being so relentlessly editorial but maybe there is a practical outcome of this discussion, like a style guide or terminological/editorial convention that could be mentioned in the FEP-a4ed? i agree that there are stages of adoption and "seamlessly extends without breaking federation or degrading UX for users of other implements" is a property worth naming (and perhaps even requiring of FEP-defined extenions!)
       
 (DIR) Post #AujJSBRSVRKD6B6znk by by_caballero@mastodon.social
       2025-06-02T17:35:48Z
       
       0 likes, 0 repeats
       
       @tchambers @benpate @silverpill @samsethi see also https://www.x402.org/
       
 (DIR) Post #AvEJ05OEpds3wLgniK by by_caballero@mastodon.social
       2025-06-17T18:15:02Z
       
       0 likes, 0 repeats
       
       Well, it depends what you mean by IPFS! IPFS is already a hashlink system (and URL scheme, and registered protocol), and is referenced as an interchangeable/cross-interoperable hashlink scheme in the hashlink spec:https://datatracker.ietf.org/doc/html/draft-sporny-hashlink-07#appendix-B.2I think what you mean by "IPFS" is the IPFS DHT (with all its censorship-resistance properties and discoverability/networking pain points), which is not actually a mandatory way of dereferencing ipfs:// URLs anymore!@silverpill @adam @mark
       
 (DIR) Post #AvEMzXiwOwNZLLMxzE by by_caballero@mastodon.social
       2025-06-17T18:34:08Z
       
       0 likes, 0 repeats
       
       @silverpill @adam @mark manu was proposing that so that Adobe could use hashlinks in C2PA, but I'm guessing no WG accepted it as work item, and/or adobe lost interest. I don't know if Manu/DB uses hashlinks in prod for their own clients?
       
 (DIR) Post #AvEMzYty1QnEzpXHoO by by_caballero@mastodon.social
       2025-06-17T18:44:06Z
       
       0 likes, 0 repeats
       
       @silverpill @adam @mark If you're recommending them in the FEP you can always link to the abandoned internet-draft as a reference, but I don't entirely understand what "apgateways" and hashlinks give you that IPFS gateways don't also provide out of the box, since there are already an ipfs:// scheme (badly specified as it may be) and GET endpoints already built into implementations in multiple languages? you can configure an IPFS node to pin all its own CIDs indefinitely and set TTL for others.
       
 (DIR) Post #AvEMzdZwdIkRVBCrnU by by_caballero@mastodon.social
       2025-06-17T18:46:17Z
       
       0 likes, 0 repeats
       
       @silverpill @adam @mark There are other options, too: named-information hashes (an older form of CID that has a normative RFC to normref!) already have a /.well-known/ GET routehttps://www.rfc-editor.org/rfc/rfc6920.html#section-4and DASL, a very AtProto-compatible subset of IPFS, has a similar mechanism if all you need is a GET route/endpoint that serves CIDs:https://dasl.ing/rasl.html