@neilk @manlycoffee some people feel like they don't want diarrhea and that health can only come from pure food.therefore they yell at the deli worker who makes their sandwich to stop putting dogshit in it.

@evanprodromou@socialwebfoundation.org I was curious what your package does that mine doesn't, so I threw qwen at it. I've cut out much of the fluff, but the gist (feel free to skip it): > ## What the package does that NodeBB doesn't > > - rel query parameter — passes rel to the server for server-side link filtering (NodeBB always fetches all links and filters client-side). > - First-class aliases and properties accessors (NodeBB buries them in _raw). > - link(rel, type) selector with exact media-type matching (NodeBB filters inline with assertAccept substring matching). > - Frozen/immutable result objects. > - Zero dependencies, native fetch. > > ## What NodeBB does that the package doesn't > > - Caching (positive 24h, negative 10min) + split-domain cache-bypass under strict. > - 5s timeout. > - Content-type validation with an application/octet-stream → JSON.parse fallback for non-compliant servers (package just calls res.json() and throws). > - Subject handling: fixes missing acct:/did: scheme, extracts subjectHostname, computes splitDomain. > - strict mode (rejects cross-domain subjects). > - actorUri extraction (rel=self filtered by accepted ActivityPub types) and publicKey extraction. > - false-on-failure semantics (callers do result || {...}). > - Hostname round-trip validation (new URL('https://'+host)/ check) and cache-key normalization. > > ## Latent bug in the package > > It uses static URL.parse() for URL inputs — deprecated since Node 10 and slated for removal. It still works on this Node 23 build, but it's a ticking time-bomb on the Node versions it targets (22/24/26). It reads like NodeBB's webfinger parsing is more battle-tested because I've had to handle funky webfinger responses from slightly out-of-spec servers. There's potential for me to use your package as a low-level fetcher though.

@deadsuperhero nice, I had made a User story about the importing part https://github.com/swicg/activitypub-api/issues/51I like the idea of lining it to registration and software/instance picker

@pfefferle @django fyi, this is probably an issue worth you both knowing about for wordpress activitypub.

@evan@cosocial.ca what about non-mentioned replies? I guess it wouldn't be received then

@commonshub I looked through your whole website and I left with very little idea of what you are actually providing. Is it suppose to be a forum?

@julian@fietkau.social that's a great idea! I should adopt that, there's no downside.

Anch'io uso friendica, mi piace l' interfaccia old-style (sono un fan della linea di comando quindi qualsiasi cosa di grafico per me è comunque avanzato). Sono iscritto da poco per cui molte funzionalità non le ho neanche usate. Lo uso da browser perché raccoon a me non funziona (quando parte va su Google play e lì si inchioda), sporadicamente uso fedilab, ma preferisco comunque il browser sia da PC che da android (usando hermit)