Technical Discussion

NodeBB now sneaks in a mention to the category/community, and this gets pre-filled in the Mastodon composer. I tested it against piefed's crust instance, and the response from Mastodon to my post on NodeBB successfully made its way to crust for distribution @rimu@piefed.social [image: 1772652313700-020a80cf-d0b0-4fbf-aa5a-20b951a109ef-image.jpeg]

@hongminhee @silverpill ah, wait, i remember now -- the issue is that Codeberg Pages doesn't set CORS headers at all, which means javascript jsonld parsers like the one on the playground won't work.although per https://codeberg.org/git-pages/git-pages#:~:text=CORS it seems that a _headers file might allow manually enabling CORS for the site?

@rimu > Mastodon is terrible for the types of discussions developers need to haveSure. But this seems to be an objection to the fact that dev discussions are federated at all. If anything, what I'm proposing would result in less out-of-context interjections in dev discussions from newbies using microposting apps, because they wouldn't see most of them by default.#FediDevs

@hongminhee @movim that said, i'm not that hopeful for xmpp-as-social-media given AP already has better momentum than most (only really exceeded by atproto?) and an instance migrating to C2S does not disrupt their access to the non-C2S AP network the same way moving to XMPP without a bridge or nomadic identity would (the initial migration would require the actor ID to change, with something like a as:Move migration)that said, there is an opening in the Federated Discord Replacement area where i think XMPP can slot in extremely well if the user experience can be done right. the architecture of one space always being in one "instance" solves a lot of the jank alternatives like Matrix suffer from. i also did a thread on that (quoted) if you're wondering about what i feel is missing there. that said, i think y'all (movim) are doing a great job working on that alreadyRE: not-brain.d.on-t.work/notes/ailzlw7e50r9jgpy

@julian I really tried. Maybe should have reached for AI. I'll look into that web+ap:// scheme, thank you!

Well there are systems that try to use both. Most notably Bridgy Fed and Wafrn. But none are ATproto based or built from the start on ATproto tech

以前から、東アジアにもFediConのようなイベントがあればいいなと言い続けてきました。独自のカンファレンスはまだ難しそうですが、小さな一歩として考えていることがあります。 @COSCUP@floss.social 2026（台北、8月8日〜9日）がコミュニティトラックの提案を受け付けています。FOSDEMのSocial Web devroomのような感じで、Social Webトラックを開けないかなと思っているところです。 まだ構想段階ですが、ActivityPubやフェディバース、ソーシャルウェブ全般に取り組んでいて、発表や共同オーガナイズに興味があるという方がいれば、ぜひ話しかけてください。 https://floss.social/@COSCUP/116152356550445285 #SocialWeb #ActivityPub #fediverse #フェディバース #COSCUP #fedidev

@trwnh@mastodon.social Yes—Fedify is database-agnostic, so tracking which IDs are already in use is the application's responsibility. Fedify handles the federation layer, but the data model and storage are entirely up to the application built on top of it.

@quaff @hongminhee thats the main issue, "the spec" doesn't have the coverage to have an implementation to cover it all. there are a ton of things that are under defined in it or that you need to point to some other spec that points to some other spec etc. thats sorta at the heart of this whole meta conversation thats been taking place recently

@jihyeok are you working on the ability to have remote drawings federate into it?

@evan that makes sense. I've just updated NodeBB to allow for the use of a manual override marker. The limit and even the marker is now customizable per-instance, and I do use the ellipsis when truncating text. Hopefully that resolves the engagement issue while still preserving the intent of b2b8 As for the use of an LLM to generate a summary, I think I will defer on that, since that might be a source of surprise for those not expecting the invocation of a LLM

@scottjenson> How critical is it that these message are encrypted?If you're going to do DMs at all, it ought to be in the roadmap from day one. A SocialCG taskforce is actively working on E2EE DMs for ActivityPub, using MLS (cc @evan), so you don't need to do it alone.> If we were to make some UX changes as a first pass WITHOUT encryptionThere's never a bad time to improve UX. Making it harder to confuse public and nonpublic posts, for reading and especially for sending, would be great.

@kopper @hongminhee @julian addendum; updated the hierarchical UNESCO World Heritage Collection with their 1247 Entry-Collections having 8000 Places.Apart from `Content-Negotiation` Noticed that you can also get the jsonld in the browser just by adding ".json" e.g.https://www.wikidata.org/wiki/Special:EntityData/Q122842228.json

Thanks @nutomic@lemmy.ml! I was wondering about that, so good to know it's possible.

@box464@mastodon.social Thank you! I've got an account on the indieweb.studio instance for now, but I'll ask you if I need another one later!

@reiver this setting is enabled by default, so you probably changed it at some point to disable quotes of your posts.Or you are looking at an old post that was created before the feature was launched?

@thisismissem ironically, I am debating rolling back the summary generation logic for NodeBB because sending the first 500 chars means fewer people go off-site to read the rest of the post. I was able to get much more engagement by sending the entire darn thing in summary.