Less than a week and we've got a minor point release for LCRQ.

Version 0.3.1 is now available from @Codeberg It's also already in @debian thanks to @vagrantc

https://lists.sr.ht/~librecast/librecast-announce/%3Ceaeb3286-a02a-4ab4-b328-47d02af9c094@librecast.net%3E

This was funded by #NGICore thanks to @NGIZero for funding these optimizations of our RaptorQ FEC Library!

#Librecast #lcrq

It's a new lcrq release with MOAR SPEED !

Version 0.3.0 is now available from @Codeberg

We have optimized lcrq for some of the AMD64 SIMD instruction sets which has achieved some large performance gains on some CPUs, especially those with
AVX512.

https://lists.sr.ht/~librecast/librecast-announce/%3C89119c3a-561f-422e-a9c0-fde0f63c96d5@librecast.net%3E

This was funded by #NGICore thanks to @NGIZero for funding these optimizations of our RaptorQ FEC Library!

#Librecast #lcrq

A good day.

More optimizations for #Librecast lcrq (#RaptorQ ) including getting AVX512 to do something useful. This has been a lot of fun and I still think I can squeeze a bit more performance out of the encoder.

Alonso came to visit, and fell asleep on my lap while I was coding. 🐶 ⌨️

Had a short walk to do some scrumping, waddling back with pockets full of chestnuts, beech nuts and acorns and scattering them along our hedge area. We're trying to get some trees established around the field 🌳

How many active users does #librecast @librecast have?

AFAIK anoyone on ipv6 could join, listen & snoop any Multicast group. (maybe I'm wrong & misunderstood? please clarify)
So how to authenthicate Multicast group members, for friends only?
AFAIK that's usually done on App Layer (OSI 7th), and considering each recepient receives data encrypted with their unique GPG public key - rendering Multicast unusable in that context (?) (since traffic from sender to all peers is not equal, but unique per peer, basically no bandwidth difference from classic Unicast)

Alonso has come by to review my code and see what else is happening in the #Librecast office today.

Can I just take a moment of your time to point out how awesome the folks are at @liberachat

We take #LiberaChat completely for granted. Like the floor we walk on, or the air that we breathe it's just there. It works. We use it every day with #Librecast and it works so well we mostly forget there are real people that make it all work.

Thanks, while I remember. By tomorrow I'll have forgotten you exist again because you do your job just too damn well.

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.