Back to the future - Interacting with threadiverse communities through Usenet / NNTP

A few months ago I threw this question out into the void - “what if you could access the fediverse through your Usenet reader??” and got almost no response. Still, the idea had lodged in my brain and wouldn’t go away so this weekend I caved in and built the thing. Hat tip to the author of the excellent nntpserver package that did all the hard stuff.

I look forward to seeing someone’s screenshots of fediverse posts on a Commodore 64, some day.

This will be released as a part of PieFed 1.7, coming soon.

Back to the future - Interacting with threadiverse communities through Usenet / NNTP

https://piefed.social/c/piefed_meta/p/1904499/back-to-the-future-interacting-with-threadiverse-communities-through-usenet-nntp

new tomo dev .plan update

tomo is dead: long live tomo

a month away from tomo gave me time to think about why the project stalled out for such a long time, and where it could go now.

tldr: tomo is getting a reboot as shard-based federated discussion forum. think of each shard like running your own BBS, except that it's linked with every other BBS on the network if you want it to be, with full privacy controls for each forum/topic.

and no more NNTP. it was causing more heartache than it was worth, while adding almost nothing.

read more here (RSS friendly):

https://tomodori.net/#2026-03-04

#fediverse #tomo #bbs #rss #nntp

@matthieu @feudjais :

Je vous rappelle que le collectif #Interhack (enfin, surtout moi) est en train de songer à monter un réseau #NNTP entre les teams recensées dans le wiki informel, et semi-officiel. Les #gif89a seront acceptées dans une limite raisonnable fixée par le #BOFH.

Interhackerspace pleroma

@StrawberryWarr Yes! Replace all group #chats with #NNTP.

Proven technology that comes with lots of advantages: freedom of interface choice, many clients available, offline features, community-driven moderation processes, decentralization, speed, includes people with special needs, ...

#PIM #chat #groupchat #discord #Usenet

fuck it. i'm declaring project bankruptcy with rslight-tomo.

😆 😭

after futzing around with tomo's (rslight-based) code for the afternoon, i realized that it's such an ensnarled mess that it's not worth trying to untangle the old rslight code from the tomo code i wrote over the last couple of years

it reminds me a little of the source code for adventure game studio - a game building IDE that is over 20 years old.

at some point open source projects have changed hands so many times that it's like trying to renovate a 300 year old house. the foundation was built in the 16th century by louise, the bedrooms in the 17th by raoul, and the bathrooms in the 18th by edward. you need to run new electrical wiring throughout the house, but none of it was ever built to accommodate conduits in the stone walls.

you don't know why louise, raoul or edward designed things the way they did, and you can't ask them now. but you assume there was some kind of rationale to their decisions, so you work around their messes. it seems ok at first. the wiring runs on top of the stonework, but you've found a way to hide it in the crown moulding. you've got it running dangerously close to the water pipes, and god forbid you ever have to fix a broken wire, because you couldn't use conduit anywhere.

after years of blood, sweat and tears, you've got howl's moving castle. your friends who visit call it quaint, but no one really wants to live there.

that's what happened with RSLight. it was originally written by Florian Amrhein in 1999 until the mid-2000s. then over a decade later, Retro Guy picked it up and began extending those php scripts with his own particular code.

and then i picked it up in 2023, and began trying to rewrite *both* retro guy's and florian's code.

the truth is: louise and raoul and edward never knew what they were doing in the first place. they were all renovators just like me, using their meagre knowledge to solve problems particular to their time and place. the house was never built to accommodate the 21st century.

it's not pretty. and worse, it's not maintainable. other people love howl's castle precisely because they don't have to live there; howl does.

#tomo #nntp #programming

blog post: death's inheritance and the future of tomo

today, tomo appears to be the only fork of the RSLight nntp server that is still alive. so what now?

i'll be honest: once Thom/Retro Guy died, i was very tempted to trash the project and move on. I have a half dozen other neglected development projects and books and a podcast to devote my research time to.

and then I thought about Thom and the thousands of hours of his life that he put into his final project before he passed away. his dedication was infectious. and in 2026, we need decentralized forum software more than ever.

that being said, I sure as hell don't want to be responsible for taking over someone else's open source project. that's almost as bad as adopting their kid. hard pass.
.....
rest of the post here:
https://tomodori.net

rss here:
https://tomodori.net/rss.xml

screenshot: the tomo interface for the user's private mailbox

#tomo #smallWeb #nntp #usenet #indieWeb

Usenet dà ancora segnali di vita.

Attualmente sto frequentando:

alt.chat-programs.jabber
alt.cypherpunks comp.infosystems.gemini comp.os.linux.misc
it.cultura.libri
it.test

Segnalatemi qui altri gruppi attivi.

Per accedere vi consiglio:

https://www.eternal-september.org/

è un server ad accesso gratuito che richiede la registrazione.

#nntp #usenet #xmpp

www.eternal-september.org

Eternal September Usenet Server

Anybody know of any accessible #nntp clients for #windows? #accessibility #blind #usenet

If you could access your #PieFed
instance using your Usenet client of choice (e.g. Thunderbird), would you?

#nntp #fediverse