JustEnoughDucks

I am already trying to understand all of it first myself. In the middle of a full-strip renovation; I don’t think I will have time to spend on it 😂

Please dear god let STM or Nordic someone hire some technical writers for Zephyr, not just Nordic documentation.

The data structures, macro basics, and core concepts are OK, but for example ADCs have literally 0 documentation at all, documentation about DMAs is barebones at absolute best, non-led PWMs is not good, etc…

Pretty much every single peripheral needs 5x-100x the documentation it currently has lol.

Some people are fine with down time/inconvenience in exchange for security.

I have my boot drive on a secured USB and LUKS keyfile with the rest of the partitions on an encrypted SSD and data on encrypted HDDs.

In a smash and grab (or fascist government gestapo smash and grab), the server is pretty impossible to steal information from (inject illegal content to in order to fabricate evidence) without the USB and they can’t simply inject boot malware either. A network device is almost always findable either by cables or WiFi broadcast analyzing.

Ah so it isn’t the kopia server receiving the backup, it is the client making a server backup to a dedicated drive? Not connecting to a different computer’s kopia instance

How did you get kopia running on your server? Even on the kopia github they pretty much just say “use one of the other options like a S3/B2 bucket or one of the file transfer options”.

Only local, without certificates for example doesn’t even work to test and there is nearly no documentation on hosting it yourself (decent documentation with the rest)

See: Susan G Coleman

Every corporation proving like always that it hates its workers and only exists for executive profit.

And ironically, the danger of teslas is underreported and downplayed. Don’t you still burn a lithium-firey death if the electricity goes out during a car fire? There have been many people that have died from that insane intentional design already…

The thing that really kills me with actual budget instead of firefly philosophy differences is that a “budget per month” app needs to have some flexibility with dates and categorization which I don’t find in actual budget. At the very least, setting a different “beginning of the month”.

I get paid on the 27th-30th of the month, that is my budget for the following month but according to actual budget, that is my budget for the month of money I have already spent. Likewise with bills, I transfer money to an account where all the bills automatically come out of after I get my paycheck, but those are bills coming out of the budget for the following month.

You can’t budget with money you don’t have yet… Especially for people with variable salaries (Belgium pays money for the days you bike to work, getting expenses paid back, etc…)

If I transfer my bills money on the 1st of the month (last possible day) and then before the 1st of the month the next month, then all metrics and budgeting for 2 months are fucked up and inaccurate with no way to fix it.

And many, if not most, of the people vibe coding projects on git repos are that stupid. People who have never coded and never used anything other than git clone. That is just a fact of many of the people who do it. They are the people who think they are tech geniuses because they once made an LED blink on arduino or made the millionth timer app.

It is just a fact of who is flooding the most slop projects. There are plenty of people who use AI in subtler or more useful ways, but that is not what is the target of anti-vibecoding rules. It is the 1000 slop projects generated bloated repositories fully in 1 day that are killing bandwidth and storage limits for everyone else.