Danyl Strype

https://socialhub.activitypub.rocks/u/strypey

Public Key

npub14r4ymc8fuwn9kpdsaf5j7knf86cgclh4j45c7dp4x2uf8vaaskxsnx0n7f

NIP-05 Address

strypey_at_socialhub.activitypub.rocks@momostr.pink

Profile Code

nprofile1qqs236jdur578fjmqkcw56f0tf5navyv0m6e26v0xs6n9wynkw7ctrgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dswnxzzx

Publishing to

atlas.nostr.land

nos.lol

relay.damus.io

Author Public Key

npub14r4ymc8fuwn9kpdsaf5j7knf86cgclh4j45c7dp4x2uf8vaaskxsnx0n7f

Show more details

Last Notes

2025-07-02 06:04:24 UTC

On a recent episode of the Dot Social podcast, John O'Nolan of Ghost said;
"For the size of the group [working on federating long form articles], which as you say is not large, man, we are spread across Mastodon DMs sometimes, an email thread other times, a Discord backchannel on the other hand, it's all over the place. We could get more organised here I think, but it's a start."
@npub1d2v…0l89, 2025
https://flipboard.video/w/g8BgnihyFkMsZ4fwGe3MZn
The fragmentation of dev discussions is something I hear about a lot lately. Forum federation could be a solution!
Imagine every federated software project has its own forum space. Smaller projects might be content with a dedicated category on a community-hosted dev forum. More well-resourced projects might host their own instance of Discourse or NodeBB or whatever suits them.
Cross-project forums like SocialHub can then have a dedicated category for each software they know about, and use forum federation to sync that with the home forum space preferred by that project.
Eg the Discourse category on SocialHub is synced with the ActivityPub tag on [meta.discourse.org](http://meta.discourse.org ). Any post in that SH category appears on Meta with that tag, and vice-versa.
With enough careful plumbing, that solves the fragmentation of public dev discussion across forums. But a lot of potentially insightful chats start in micro-posting threads. Adding a limited ability to start a new forum topic, by mentioning the relevent category or tag actor (eg @discourse@socialhub.ActivityPub.rocks), could bring those in too.
However, most of the examples John gives are private chats (fedi DMs, email, Discord, etc). I encourage devs to gird their loins and apply the 'release early, release often' principle to dev chat. Make public the default for dev chatter, unless it really is sensitive.
That said, with some careful work, support could be added for federating private conversations between forums too. Ideally in a way where AP actors could be included, that automatically open the chat to trusted groups.