I just signed the funniest community agreement....
For context, Light-O-Rama, aka LOR, is a company that sells software and hardware for creating holiday musical light sequences. The software licenses and hardware are NOT cheap but, if you've seen a commercial music and light show in the last 30 years, it was likely done with LOR software and equipment because they cater to that audience. xLights, on the other hand, is a free and open source software solution that caters to home users. The software is FAR more advanced and customizable. Depending on what you're doing, most people would argue it's much easier to use as well. The big difference is that xLights has millions of users vs LOR having thousands so the support community is far more robust as well.
All that said, this community rule is probably the most necessary one I've ever seen in my life. Esspecially when considering that anytime somebody posts about LOR hardware on the xLights forums, 200 people will jump on them about how they should just get rid of it and build thier own controller even though xLights fully supports the LOR hardware. (That's actually how xLights started. They got sick of missing features in the LOR software and paying for the annual licenses.)
Andrew Tomazos, banned from the C++ Standards Group for using the word "Question" in a technical document, shares his story.
The company that pre-loads Chrome on Android, and makes ChromeOS, says Microsoft is "Dark" for pre-loading Edge on Windows. To make this case, they've formed "Browser Choice Alliance" with Opera & Vivaldi.
Interestingly: Apple Safari, Mozilla Firefox, & Brave are not involved.
Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.
It's a fascinatingly annoying cycle. And there's only one viable way out of it.
Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm
Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal
Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.
Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣
Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm
Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal
The craziest story, this last week, has got to be the one where the C++ Standards Group banned a contributor for using the word "Question" in the title of a technical paper.
That was just plain insane.
If you watch just one show this week, watch that one. It's too weird to miss.
The Shows
The Articles
The Comics
Previous Few Months
Reminder: Check out Lunduke.com for all the handy URLS. Podcast RSS feeds, contact info, direct links to some of the big shows and articles and a bunch of other goodies. And be sure to subscribe to The Lunduke Journal to help support the work... and make sure you don't miss out on anything.