NodeBB-ActivityPub Bridge Test Instance

@jens this is why i put "clever" in quotation marks. like, yes, that's just how references work, no problems there.the problem is that you are taking something that isn't activity+json and sticking it in an activity+json document.more precisely, the media type no longer applies to the *entire* document; there is a fragment of the document that has a different media type (like the hypothetical schemadotorg+json i was talking about earlier)

@cwebber activitypub is a polycule for webservers

@tchambers if you mean the google doc, i still fail to see how it's "far better ux":- what you call "option a" would not work without pre-registration, and would be terrible ux outside of browsers- what you call "option b" is basically what mastodon already does, as best as i can tell... although it has issues outside of mastodon [1] [2]- what you call "option c" would not work at all, because localStorage is not shared cross-origin[1]: https://github.com/mastodon/mastodon/issues/26995[2]: https://github.com/mastodon/mastodon/issues/34908

@natalie yeah i don’t fully agree with all their decisions but i understand why they made themvirtual host support would probably be quite feasible to retrofit onto existing fedi codebases but i doubt it’ll get done anytime soon

We're happy to help using Bounce if y'all want it rolled out earlier

i mean i guess this is why profiles exist, right

@silverpill @steve @raucao I have already described in the GitHub issue the options available to us. One is to make no normative changes and simply issue updated guidance. The other is to completely rewrite the context document to undefine the "as" term prefix, so that the canonical and conformant form changes from as:Public to the full identifier. (Plain JSON consumers still need to consider JSON-LD when producers augment the context.)

@tedu a fix was just merged: https://github.com/mastodon/mastodon/pull/34996

@swaggboi @specter it’s called sbtv or something i think

@eblu i think the hard part is getting everyone on roughly the same page with identity and how to make use of it. you could generate a keypair and have your browser sign http messages, or you could wait until fedcm is ready and offload that to an explicit “identity provider” service.for the publishing apis, it’s mostly a matter of which ones you support. a micropub endpoint, an activitypub outbox, etc. — you might need to use a strategy pattern to make this pluggable.

oh also re: onboarding, the analogous thing would be asking people where on planet earth they would like to live. first you have to pick a country (server software) then a city/town (specific instance). the answer isn't "funnel everyone into one place". that's like saying everyone should just live in one city, or everyone should start in the same city. you're trying to get people to move from sf to berlin, but what if they don't like berlin? what if they don't like germany either?

Everyone complains about the "vibe" of the social network they're already on. While something like an algorithm or custom feeds can aid in curating a vibe, if you follow, have followers, and block folks across networks, you end up creating a vibe for yourself.Why should we allow a platform to dictate the vibe you want? Seems backward in a people-first network.

Love to hear it!

@codl didn't look familiar at first but i checked my watch history and yeah u rite

@raphael i’m not sure how feasible it is to standardize “skills” descriptions, but the goal would indeed be to find some mapping between natural language and machine-parseable assertions/claims. there is some prior work from 2002 but i don’t really find it as an adequate solution: http://rdfs.org/resume-rdf/

@raphael really, that's kind of the whole point of a "fragment" identifier, it identifies a "fragment" of the resource, and its semantics are determined by the media type.for text/html, a fragment corresponds to an id= attribute or otherwise can be read by javascript. see https://www.iana.org/assignments/media-types/text/html for "Fragment identifier considerations"

honestly the hardest part of getting started is constantly being interrupted just before you reach activation energy

@decay Big Bill Hell's License is an all time classic. FUCK YOU, OPEN-SOURCE! for those not familiar: https://lifning.info/BBHL

@Wuzzy They do indeed admit to all of that in the privacy policy. Ultimately though, none of that shakes my trust in the _people_ working at Vivaldi.I've been using the browser for ~9.5 years; so far, to my eyes at least, they have been transparent with their intentions, and extremely consistent at following through with them; after all, actions speak louder than words.And while it would be nice if Vivaldi were FOSS, I'm not holding my breath over that matter - and hey, they're source available, fwiw ¯\_(ツ)_/¯@leeloo

@0x4d6165 the patent describes some kind of evil cellular teddy bear that is racist and manipulates children into buying mcdonalds