Making progress on lowering my digital footprint.
Google
Amazon
Facebook
Apple
Microsoft
I gave notice on my LinkedIn (but still need to close it) and still have a GitHub account, which I no longer use. I've kept it because there are redirects to our #Librecast repositories on there, but I should close it soon. If I want to contribute to a FOSS project I'll have to find another way.
I still have a Google account I use with YouTube, but should probably delete that too.
New Linux Stable and LTS kernels are out:
6.15.7
6.12.39
6.6.99
6.1.146
5.15.189
5.10.240
This is the first set of stable kernels since @librecast started testing release candidates. Our tests give the network (mainly IPv6 and multicast, obviously) code paths a bit of exercise to check for regressions like the one we found last month.
At the moment we're running our libmld and #librecast test suites on amd64 only, but as we build out our CI system we'll include more tests.
5.10.240-rc1 was just tagged with the patch applied, so when that gets released all affected kernels will be fixed.
6.12.38
6.6.98
6.1.145
5.15.188
5.10.240 (RC1)
This network bug was found by the #Librecast test suite. It occurs to me that we should be running our tests over the stable release candidates to catch this sort of thing earlier *before* they end up in your distros.
The team of people testing #Linux stable kernels is small, but it just increased by one
And yes, I have written a #multicast git transport for #librecast
Of course I have.
Good news from @onepict video.thepolarbear.co.uk/w/fyecXM9ULjsKDpUN3bMiid about the #LibreCast project.
There is even a nice polar bear picture on the website!
librecast.net/
We've got some good news thanks to @nlnet and @NGIZero
Librecast has been funded to do more awesome things with #multicast
Watch this space.
Thank you to NGI Zero Commons
@mray @cwebber would love to know as well.
For people not in the know, @librecast is a R&D initiative that's innovating the internet stack with support of @NGIZero and @nlnet
First, to enable #multicast on the unicast internet an overlay network is planned, based on #WebRTC. See:
https://librecast.net/librecast-strategy-2025.html
#Librecast LIVE will bring all the technology together, to demonstrate and be a reference implementation. With #ActivityPub support being planned. See:
@cwebber I'd love to know what you think about #librecast (if you heard of it) in terms of what we "miss, now that there is #ActivityPub ".
Stumbled on a regression in the Linux Longterm 6.12.y #kernel when I upgraded some machines yesterday.
#IPv6 UDP packets were no longer being fragmented as though IPV6_DONTFRAG was set when it wasn't which broke a #Librecast test.
The regression wasn't in the mainline kernel so I spent a happy morning bisecting kernels until I found that a patch had been backported in 6.12.31 without backporting two previous related patches.
Reported to the stable maintainers with a test program. Now I wait.
Dodge the dodgy #AI infested corporate #streaming services and zoom out, as on the #fediverse we own the stream. Here are platforms that offer #streaming of #video or #audio in real time or near real time, with live chat and other #social capabilities.
On the fediverse our #lifestreams meet people and humanity and we engage our favorite fedi crowds. Fedi is where outreach matters.
#Librecast LIVE. @librecast is a research project aiming to bring #Multicast to the masses.
Had an interesting conversation with someone from the IETF about #multicast today.
Some folks have been trying to solve the problem of getting multicast streams from unicast only sources (Off-net Sourcing) such as browsers.
This happens to be something #Librecast built a demo for back in 2022 as part of #NGI0Discovery and which we're working on again now as part of #NGI0Core thanks to @nlnet so I think we might be able to help.
Thinking about how to explain #librecast can mess with your head:
"Don't list all great things. It sounds too good and people will turn way in disbelief and never understand."
… or maybe I got it all wrong myself!?
Congratulations on the release, #Librecast team!
It is a very exciting #multicast use case you are driving lcagent with, and I am looking forward to learn more about your experiences with this #CI setup.
Thank you, for all the hard work!
lcagent can be used to send and receive data over #multicast and to pipe data between programs on one computer and as many receivers as the multicast network can support simultaneously. We're currently using it now to run our own CI builds by multicasting the patch to multiple build servers simultaneously.
This could also be useful for monitoring and configuration management.
#librecast
We've got a new tool! lcagent version 0.1.0, the #Librecast #multicast agent.
In server mode, lcagent can be configured to listen on Librecast Channels (multicast groups) and execute programs in response to packet data received on those Channels.
Packets must be accompanied by an authorized token and signed by the matching key or they will be silently dropped.
Data is encoded with #RaptorQ using Librecast’s liblcrq library to provide forward error correction in the event of packet loss.
@dlakelan @mray You're technically correct (the best kind!)
Yes, SSM is PULL rather than PUSH, so it has one of the properties of multicast, but it is lacking the other characteristics that make multicast special.
SSM relies on knowing in advance the *unicast* IP address of the source.
SSM is unidirectional.
SSM lets one sender shout at everyone else.
SSM is not group communication.
SSM has its uses, and it's easier than true #multicast but it doesn't meet #Librecast 's requirements.
It's a new release of Librecast!
This release adds restricted channel support with token based authentication. This allows keyrings to be created and filters to be applied to channels such that any data arriving which is not signed and accompanied by a token issued by an authorised key will be dropped.