Notices by shom 🐧📷🤿🏔️🪚✊🏽 (shom@fosstodon.org), page 2

@daviwil is an excellent teacher and an excellent human being.
I'm really glad I took his guile scheme course, I understood programming fundamentals better, stuff I thought I groked. I'm going to see if I can move my travel plans to join the git workshop. Git good y'all!

@cwebber to make _that_ comment that **THAT** thread. I would love to borrow 1% of that guy's confidence, I'll become unstoppable!

@daviwil great topic and cute artwork!

@brianbilston three years ago I lost my closest friend of 20 years. Everyday when I come across cool things that he'd find interesting my first instinct is to send it his way like we used to.
He would have loved your brilliant and creative poem. Today is his birthday and I shared this with all his people in his memory. You have truly brightened our day in fondly celebrating our beloved friend. Thank you!

@clacke it's good to be a regular 😂

@evacide sorry for the necro-reply...

For anyone stumbling upon this exchange later not only can you read the reports linked by evacide but if that's too much work, the EFF is a 501(c) non–profit that has strict reporting requirements and if these unsubstantiated claims are credible, one should absolutely publish the scoop. The EFF has powerful detractors and would love to bury them.

Support the EFF as they work in public interest instead of engaging in manufactured sanctimonious purity tests!

@clacke it's great (?) that the landscape has changed a bit in the last 4 years with Framework¹, System76², and others.

¹https://knowledgebase.frame.work/en_us/what-countries-and-regions-do-you-ship-to-r1899ikiO
²https://system76.com/shipping

@clacke @SocialGaff the sign should say bread potato!
That's quite the "is it cake?" situation.

@gabek @roadriverrail thanks for the great context write up @eb

It was wise of @drewdevault to host redict (redis fork) on @Codeberg to maintain workflow parity with github and avoid any perceived conflicts of interest¹.

I wondered why LGPL and not of AGPL², which is also explained nicely: "but we want to make it as easy as possible for users to comply with the Redict license and we do not see any reason to discourage cloud providers from making use of Redict."

Hope other marquee projects follow suite.

¹https://fosstodon.org/@drewdevault/112167165399257154
² https://redict.io/posts/2024-03-22-redict-is-an-independent-fork/#why-lgpl

@immibis sorry, which part is FOSS class treason, I didn't follow.

@immibis But in this case, with LGPL they can/might switch to redict and could continue contributing. I'm using can/might/could to illustrate that it's a possiblity, not a guarantee, but AGPL would be a guaranteed no.

So in this specific case @drewdevault's choice gives a better shot for contributions from cloud providers to land on @Codeberg than AGPL hosted on sourcehut.

2/2

@immibis ah okay, yeah I agree on principle for sure but not on existing projects that are already in use by the cloud providers. If redict was licensed as AGPL (which is what I would have thought) then none of the existing cloud companies would likely use redict. So none of the contributions they make would never make it out as FOSS.
1/2

Thanks to @cvennevik and @aardrian for pointing out this amazing story.

My opinion: curious coders experimented in good faith, discovered a serious architecture issue with technology and policies, tried to notify and rectify, but got blamed by commercial entities instead of being thanked for their good faith disclosure.

It's very much worth the read:
https://boehs.org/node/npm-everything

https://hachyderm.io/@cvennevik/112100333787925276

@aral aw poor pup, please give extra pets from me!

@hypolite I believe the whole nitter approach is dead now:
https://arstechnica.com/tech-policy/2024/02/twitter-front-end-nitter-dies-as-musk-wins-war-against-third-party-services/

@clacke

@hypolite (Un)fortunately it'll be obvious to everyone now since nothing will work. I hope this leads to sites not linking to Twitter.
@clacke, not a dig against you at all. I enjoy your posts!

@lanodan @hj @halva we need more devs like you!

@aral that's really interesting. Is the idea of composting on the Atem to reduce CPU load on the streaming machine? That is instead of adding the camera and screen into OBS as layers to achieve the same thing.
@tychi @baldur

@aral that would be really cool! As someone with a programming background but not Javascript and little HTML/CSS knowledge a foundational course would be very helpful for getting started.