> This is why I moved to the BSDs. Linux started as a grassroots project but turned commercial

Thanks, this may be the key takeaway from this discussion for me

> multiple maintainers and contributors

This is important but seems orthogonal to whether or not the repo is under an org.

First time I've seen this idea, I have a tingling feeling it might become reality sooner rather than later.

The snarky answer is that MQTT doesn't require the author's UDP to AWS Lambda gateway SaaS⁰.

I did find MQTT flavors that support UDP but neither MQTT/UDP nor MQTT-SN seem concerned with WireGuard-level security.

⁰(This article is AI-assisted content marketing good enough that I didn't realize it until ¾ through.)

Fair point that yes I’m eating my own dog food here. And I’ve been called a robot enough times maybe I should keep track.

To the question, UDP is easier on a battery than MQTT.

To be clear I understand you are not a robot, but the article reads more as LLM generated especially toward the end which is why I said "AI-assisted".

Thanks for sharing this project; TIL about AliExpress Dollar Express tiny touch screen ESP32 dev kits for first-time buyers for $9 including shipping.

> The client always sends the last ID it received.

Contrary to the second half of the article the display is not stateless (especially not WireGuard). However, the combination of minimum viable state and giving payment details to cloud services does simplify IoT projects.

> Do you expect an IAP peddler to support free software?

Valve does.

Valve doesn't own RAD though

> Why should I throw away all the timestamps, just because the file were temporarily in an archive?

In case anyone is unaware, you don't have to throw away all the timestamps when using "zip with no compression". The metadata for each zipped file includes one timestamp (originally rounded to even number of seconds in local time).

I am a big last modified timestamp fan and am often discouraged that scp, git, and even many zip utilities are not (at least by default).

git updates timestamps in part by necessity of compatibility with build systems. If it applied the timestamp of when the file was last modified on checkout then most build systems would break if you checked out an older commit.

git blame is more useful than the file timestamp in any case.

As another example, a SQL Server optimization per https://learn.microsoft.com/en-us/sql/t-sql/statements/set-n...:

> For stored procedures that contain several statements that don't return much actual data, or for procedures that contain Transact-SQL loops, setting SET NOCOUNT to ON can provide a significant performance boost, because network traffic is greatly reduced.

evengrounds.com mentioned recently: https://news.ycombinator.com/item?id=46502269#46547839

I am not an expert but as long as the video is playable by the browser (x264 - Chrome apparently supports the most formats) and the same duration (05:12:14) it should work.

This is from 7 years ago but you can see if there's any helpful discussion attempting to use the initial release: https://www.reddit.com/r/Bandersnatch/comments/adnn2h/github...