Alright, I wrote a blogpost about my adventures:

This doesn't have much new compared to my posts from this weekend, but here they are ordered and coherent.

I also posted some audio samples:

Keep in mind that both samples will sound pretty much horrific, but also that each sample is around 100kb for more than a minute of audio.

I prefer the Opus file to the mp3 file, as it's a little less muddy during speech (but ruins music.)


Would be really nice if #floppycast ing would become a thing, preferably with codec2 and wavenet decoding and fediverse integration.

@jsilence I'm looking in to codec2 this week. From what I've gathered, there's no software that would play it back on my target machines (486 and Pentium era computers running DOS), but beyond that it seems like the perfect fit for this project (and for encouraging more broad adaption of the concepts.)


Contemplating on starting a blogcast about climate change. German media is really neglecting the topic and I'd like to translate, contextualize and comment on english spoken media coverage. Doing this in a #floppycast format would really fit well with the topic of low ressource usage. #formfollowsfunction


Distribution of the #floppycast via dat:// or ipfs would make sense as well.

@jsilence I like the way you think!

I'm still not 100% sold on dat because the only implementation is node.js, but distributing the thing peer-to-peere seems like a good call.

Maybe even over SSB?

Focusing on very small file size has a huge impact on penetration when you're distributing peer-to-peer.

(I really wish there was a podcast client or an RSS reader with torrent based distribution built in. I'd already have a (fairly low bitrate) video podcast in distribution.)


Too little practical experience with dat, ipfs or SSB. Read a piece on HN lately on how ipfs is not yet up to snuff and not well managed. A commenter mentioned that dat is way ahead with that respect.
Propably a #floppycast could be distributed via all those fancy new p2p channels.

@jsilence Dat is the furthest along, and I use it pretty regularly, I just don't like the bloat of a JS application being used in this respect.

I also have some issues with SSB, on several fronts, but it seems like a great avenue for distributing tiny files.

To me, though, it seems like this is a perfect usecase for torrents + atom/RSS feeds.


Ok, will look into SSB. So far I only have read the name in context with p2p a couple of times. Need to investigate. Will be back when I watched all SSB videos on YT. ALL OF THEM!


I see, the #floppycast file would end up in the blobs folders of SSB users, so squeezing file size would be really nice to them.

Sign in to participate in the conversation
R E T R O  S O C I A L

A social network for the 19A0s.