@vibechen eigentlich schon. Früher hatten wir uns immer viel bei den @ffhl treffen dazu ausgetauscht, aber da kommt leider schon lange niemand mehr, auch nicht durch's ändern auf quartalsweise. Den Austausch vermisse ich etwas.
War auch am überlegen, vll. mal einen #dn42 Vortrag mit anschließendem Workshop beim #Nobreakspace zu machen. Weil man mit dn42 ja auch eine Menge praxisnah lernen+experimentieren kann. Hatte da letztens dn42 wieder eingerichtet und wollte da mit #multicast weiter machen.

@Natanox @librecast @EU_Commission @dentangle this is an interesting question, I initially wanted to reply that I never saw technical changes decided by politics. And that I think the biggest problem is the chicken & egg situation: Barely any #multicast enabled applications <-> barely any multicast users.
Switches become a solved problem, see the advances with #DSA in the Linux kernel/bridge. You can even play/contribute via affordable #OpenWrt + #Realtek switches. Or #Freifunk. 1/x

@evey @Natanox

If you're interested in some of what's happening right now with #multicast in EUMetSat/EUMetCast, this talk from June this year might be interesting to you:

https://tnc25.geant.org/recordings/?session=s792

One of the options for final delivery is TreeDN, which was only standardized early this year.

And yes, I have written a #multicast git transport for #librecast

Of course I have.

@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:

https://librecast.net/live.html

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.

#Owncast. @owncast

@librecast @NGIZero

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

https://codeberg.org/librecast/lcagent

This work is made possible by @NGIZero #NGICore

@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.

@mray IP multicast is a complicated mess, largely because IP is fundamentally unicast in design. There are several different forms of ASM (Any Source Multicast) and most of the complexity is around building source trees when you don't know where the source(s) will be yet.

SSM is a clever hack that says, what if we just skip past all that to the end when we KNOW who is sending, and build that, as it covers a lot of use cases (eg. ballgames).

But, it loses most of what makes #multicast special

@mray Depends on your point of view. Streaming a ballgame to millions of viewers is a problem television solved over 70 years ago. We call that broadcast.

If we use SSM (Single Source Multicast) to unidirectionally stream a game to millions of viewers, I call that broadcast, regardless of how many protocols we use that happen to have #multicast in their name.

Most IP multicast is actually broadcast.

Multicast is group communication. If only one member of the group can speak, that's broadcast.