v8 for the #multicast patchset for the #OpenWrt #Realtek target pushed: https://github.com/openwrt/openwrt/pull/18780#issuecomment-3808673943
Now rebased onto the v6.18 PR for #OpenWrt. And with many style changes, which were suggested in the comments of this PR.

Curiously without needing to cherry-pick the mdio_aux reset-gpio revert to fix https://github.com/openwrt/openwrt/issues/18620. Worked out-of-the-box on v6.18. Will need to dig deeper later what in OpenWrt or between 6.12->6.18 might have fixed that.

v8 for the #multicast patchset for the #OpenWrt #Realtek target pushed: https://github.com/openwrt/openwrt/pull/18780#issuecomment-3808673943
Now rebased onto the v6.18 PR for #OpenWrt. And with many style changes, which were suggested in the comments of this PR.

Curiously without needing to cherry-pick the mdio_aux reset-gpio revert to fix https://github.com/openwrt/openwrt/issues/18620. Worked out-of-the-box on v6.18. Will need to dig deeper later what in OpenWrt or between 6.12->6.18 might have fixed that.

@datacop @cypherhippie following up on the off-topic discussion on Jitsi regarding overlap between @battlemesh and #Fediverse ( #Fedicamp?): I'd be super interested to get a better insight into what resources a Mastodon instance needs + how its data flow looks like. How much data is sent synchronously / simultaneously / redundantly to multiple receivers, how much is sent on-demand? Could smarter routers lead to less resource requirements for an instance/server? Could (long-term) #multicast help?

So I tried to document a potential pitfall with layer 3 #multicast routing, with #PIM in particular, here: https://wiki.dn42.dev/howto/pim-multicast-vs-unicast-issue
The issue of multicast potentially being black holed if the unicast topology is larger than the potential multicast one. I'm wondering how other people tackle or avoid this or if I'm missing an easy solution.
(I'm wondering if maybe @troglobit or @dentangle might have some ideas?)

#pimsd #pim6sd

Anyone know why #UPnP appears to be broken on #NixOS?

So far I only found one forum post attributing it to a "beyond repair" broken Multicast in #NixOS

#Multicast

Anyone know why #UPnP appears to be broken on #NixOS?

So far I only found one forum post attributing it to a "beyond repair" broken Multicast in #NixOS

#Multicast

@olm_e @OlivierAuber Agreed. While we're waiting for the AI/LLM bubble to pop lets keep building the systems we need to help society recover from the mess that will be left behind.

#Multicast can help us build truly decentralized systems that do not rely on the same centralized, profit-driven corporations that are stoking this AI/LLM bubble.

@OlivierAuber hum - AGI is a mirage we should not seek to catch.
human intelligence in a society helped with communication tech is, But indeed it's captured now for decades.
#Multicast is not profiting authoritarianism in any way, so I would really not bet huawei is going to invest in it either. It needs multipolar worlds entities collaborating together, not competing for power. This could come if ppl awake from the current slopness (as a next history wave)

imho it was not a effective stage

Ma discussion "au coin du feu" avec Ben Goertzel au #BGIsummit Istanbul
I reclaim the original DISTRIBUTED architecture of the internet
"CISCO, why not opening #Multicast for #SingularityNet #agi
Et j'ai ajouté en off : "If CISCO don't, Huawei will"
https://www.youtube.com/live/gb5ESFppdD8?si=iHr6wGPYHmwdX4cB&t=11704

I wonder if @librecast has some plans or even a lobby in the EU to advance the adoption of #Multicast in the near future. If there's any time the @EU_Commission would be interested in a major technological shift (due to digital sovereignity efforts) it's probably right now.
To my understanding the underlying capabilities (below layer 5) are already there, it really just needs the political will to enforce it being enabled in routers etc.

Or are there still big fundamental hurdles? 🤔 @dentangle

I wonder if @librecast has some plans or even a lobby in the EU to advance the adoption of #Multicast in the near future. If there's any time the @EU_Commission would be interested in a major technological shift (due to digital sovereignity efforts) it's probably right now.
To my understanding the underlying capabilities (below layer 5) are already there, it really just needs the political will to enforce it being enabled in routers etc.

Or are there still big fundamental hurdles? 🤔 @dentangle

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

Of course I have.

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.

#ngi #librecast

https://spectra.video/w/fyecXM9ULjsKDpUN3bMiid

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.

#ngi #librecast

https://spectra.video/w/fyecXM9ULjsKDpUN3bMiid

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.

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

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.

Je trie mes vieux cartons :
#collector ! Il y a trente ans, Francis Mizio raconte comment il été pris d'une sorte de frayeur cosmique lors de la première expérience planètaire temps réel de la version distribuée #multicast du #poieticgenerator