Notices by bumblefudge (by_caballero@mastodon.social)

well that's neat
https://nesbitt.io/2026/01/25/pkgfed-activitypub-for-package-releases.html

@evan the game studio? i think the studio itself is on instagram but if you're asking about the disco elysium people that don't work there anymore i could've sworn at least one was on here...

@benpate @evan @thisismissem @julian @naturzukunft all joking aside I think c2s requires emelia and Aaron's rfc on the OAuth side, and some equally complex discovery mechanism based on alternate AuthZ (presumably something based on certificate-ized Object Capabilities?) if we wanna stay composable and not-100%-dependent on oauth...

@benpate @evan @thisismissem @julian @naturzukunft SWICG c2s task force wen (or will the payments task force just naturally become the c2s tf over time)

@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?

@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.

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.2

I 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

@tchambers @benpate @silverpill @samsethi see also https://www.x402.org/

@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!)

@pfefferle @julian it happens to the best of us! and me at least every third time

@pfefferle @julian was this intended as a private mention perhaps?

@scott I don't consider wages (even above market ones) profit. profit is what you extract from the wages of others by owning the business

@raphael you don't have to throw out the entire market baby with the profit-maximizing backwater, was my point. if all labor is paid at rates transparent and public you don't need to pay "market rates", you just need to pay something sustainable and acceptable to all parties, ideally decided transparently and updated over time in a public process. that's not exactly outside of price discovery but it's at least not coupled tightly to it.

@raphael to put it another way, i actually think fediverse and capitalism don't mix, but i'd still pay 100/yr for an account on a server that reinvents all its excess revenue in open-source contributions, for example.

@raphael capitalism is profit-maximization -- thus johannes' apt point that people often donate to or overpay for services they trust not to be profit-maximizing from trustful foundation-like groups of people :D

@hrefna Yeah that thread was a wreck, I feel for everyone involved (and like, already followed most people involved on both platforms!). It is a tricky balance because I agree that it's a bad look and alienating people, but I also agree that perceived/soft-power aside, he doesn't have that much FORMAL power-- anyone could just tjoin he CG and start lobbying for anything they want. I've been trying for over a year to crowdsource a CG charter that formalizes any of this...

@evan no one moves here for the storied local cuisine. i recommend Volkskammer if you really wanna go local (masochistically)

@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

@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

@pfefferle @linos @darnell I'm more worried about the query parameter in an IRI than I am about the Move activity having its target on the same domain! I'm no JSON-LD wizard but I wonder if that's valid as a URI to stick in an `actor.id`, and even if it's valid, I'd worry other implementations botching it or dropping the `?...` somehow, because of some unwitting behavior of underlying HTTP validation libraries or whatever