JustEnoughDucks

Personally I would say that is preferable to my house burning down like with Bambus 😉

This hasn’t really been true since the MK3. Even then, I have a MK3 and besides recalibration between filament changes, I have not had to tinker with it almost at all.

I need to do something similar. I have a Esp32S3 music player/ voice assistant connected to my old Yamaha, 90s AV receiver. It can change the volume knob via IR commands (cool integrated motor that physically turns the knob when the remote or HA changes the volume with IR).

I want to do something like put a ring magnet and an encoder on the tiny shaft or something to get position feedback to couple to HomeAssistant/musicassistant.

I read the whole thing. This seems like standard sponsored response of not biting the hand that feeds them now that they are full time…

The entire point 3 of the user complaint is reaching really far. The one user is being toxic through the whole thread so I also get from their side not wanting to heavily engage because nothing besides divebombing immich’s entire livelihood would satisfy them it seems.

FUTO seems like a toxic company, but the thread isn’t damning. It seems like we have to keep an eye on immich. Otherwise a fork I guess…

FUTO sponsors immich I guess, FUTO is on there. FUTO is problematic but as far as anyone can tell, they haven’t pushed anything on immich.

It was a joke, chill.

But let’s be in good faith about this, vibe coders will overwhelmingly use cloud based corporate frontier models…

And self hosting LLMs in general singularly and only solves one part of the resource objection (prompts running on green energy) and that is all and only if the model is run on green energy. It doesn’t solve most of the moral objections, IP objections, economic objections, resource objections, or brain damage objections.

That being said, one’s own, local, never-to-release app or internal tooling is probably one of the better uses for LLMs like documentation discovery, informal document translation and tiny TTS and STT models (the best usecase in my own opinion)

“You’re right to push back, when you create a new plant layout on Fridays, it does drop the entire database and rm -rf / your system, would you like me to fix that for you?”

And yet they allow corporations to relentlessly pillage all water sources going 2-3x their paid water rights while the populations eat the costs and effects…

It is all excuses to increase water insecurity.

Look at the code and commit history and/or talk to the developer.

If the developer only commits in giant blocks of 1-2 days and mostly in a few hours and changes thousands of lines of code in that time, the chances of it not being vibe coded and actually being checked are extremely slim, outside of a complete project refactor. It used to be that LLMs would just do massive single commits, but now they do a thousand tiny commits on the same day using a ton of barely human-readable jargon (for less experienced devs) in the git commits.

If the project was started past 2025 and the initial commit(s) on the first day were massive, that also points (less strongly) towards vibe coding.

If the Dev can’t explain what his code does without having an LLM write the response (this is getting to be harder), that also generally also means that it was vibe coded.

If the dev’s commit history only includes documentation, issues, or very very small things until 2025-2026 and combined with one of the above, it is usually vibe coded.

The vibe coding identifying sites online are complete garbage with mostly false positives. For example, if I run it on my old github repos from before LLM coding existed, it says that it is very likely vibe coded because I comment a ton because my memory isn’t great and I am an electronics guy with very bad coding git management so my git commit history is like one or two commits per day when I am working on something, but I try to bullet list all of my changes in a readable way for people not familiar with the code (like myself in 1 year lol)

I think the comment about AI is not in good faith.

It isn’t users saying every “AI assisted” project is vibe coded slop.

It is just as often or more that developers and “developers” lying about AI assistance when they are just vibe coding or “AI assisting” and barely checking over the code. There are tons if those on Fdroid android apps too.

The projects that are actually only AI assisted don’t get that many complaints on most communities I see. It is the slop that people push as legitimate that gets people riled up.

Also the controlling party in Italy is practically neo-fascist and Austria is also sliding there again with their Nazi party like AfD in Germany and VB in Belgium getting a huge portion of votes.

I don’t see how it is that much better than a US non- profit.

I think the core thing is that you have to know of a bunch of different CA options and switch when necessary or on a compromised CA.

This happened when my sshd dameon did not start or died. You could use systemctl status to check it.

It has also happened when my white listed static IP for my machine that I access the server with changed. Do you have a default DROP policy?

Timing out indicates that either the sshd service doesn’t exist or is unreachable (but not blocked).

Check the dmesg for all sshd notifications and maybe you find why it is crashing (if the service is dead)

Also, looking towards the future or for people that can find one at a decent price:

Not a raspberry pi but an Orange Pi Plus or Pro. They have a rockchip that has AV1 decoding (along with standard others) which is probably going to be the future (it is for corpo streaming already).

Put plasma big screen on it and get a Bluetooth wechip remote or something

There is no way this isn’t just an AI bot

I guess there is no rule about having the AI writing the AI disclosure because I guess 4 sentences has to be extended into 8 paragraphs.

But what if the AI disclosure lies? 😂 for example, PRs are reviewed by Claude code and merged. That doesn’t sound like “every commit is reviewed by the maintainer”

This seems like the perfect scam for Lemmy for setting up a fresh IP for launching a cyber attack/scam with a real residential IP. Helping a community member while circumventing shitty corporations. (Not saying OP is, just that it would be a decent scam)

This requires either an insane amount of trust in a random person or gullibility. Plugging a random mailed device into your network, even behind a VLAN.

I definitely would never do this if I didn’t have absolute full and complete access to every part of the pi’s software, or preferably set it up myself (optionally in collaboration with the requester) and the requester only had read-only access to it.

Eh, I am not pro AI, but these sorts of non- critical projects are maybe not a horrible use for them. Keep AI out of my kernel, core programs, basis functionality, camera, and personal/health information etc… But for a sorting/catagorization tool maybe not so bad. (Ignoring the environmental and ethical concerns of course)

Good question!

Sodium ion already had a reduced capacity (30% less at least than Lithium ion). And 2.5% of voltage is not 2.5% of capacity, something more like 3-4% (still small)

You could then just choose to use a configurable lithium ion IC, but almost all of those have an undervoltage lock out (safety shutoff) that is 2-2.5V that you would have to stay above. Sodium ion drops out at 1.5V, so I would again be losing a chunk of capacity. If I lost 30%-35% of capacity on an already reduced capacity cell compared to lithium ion, then battery life would be quite disappointing.

Do that rules out using a standard Lithium-ion charger.

If I am building a custom charger anyway (most non- embedded systems have custom chargers), then might as well put in all the features now and get 100% of the capacity. Cells usually also have a higher lifespan (double or more) by dropping that high CV charge voltage 0.1V or so and settling for lower capacity, but Sodium Ion lifespan is already 3000-5000 cycles compares to lithium’s 500-1000 (lithium ion and li-po, lithium iron phosphate is in the higher range) so might as well then use the full capacity.

That is amazing! I have just started making sodium ion battery chargers in my free time.

The bad thing abouslt sodium ion is that traditional CC/CV charging is harsh on the cells. Optimally each cell had to be CV charged at around 97.5% of its voltage end and then slowly brought up to 100%. Apparently that is how you get the most life cycles per cell

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.

Anything with a motor will run differently, usually safely but not always.

Motor speed is 120*frequency/poles.

For example, a 4 pole hair dryer motor will run at 60Hz, the fan will run at around 1700-1750rpm instead of 1400-1450rpm.

For fans specifically, this can be a problem because fan load (torque) increases to the third power with respect to speed. This means that changing the frequency to 60Hz for a fan designed for 50Hz will run it at a significantly higher load which can make it run at a worse point of the torque curve where it is less efficient and ultimately overheat.

Some electronics have filters based on their designed operating frequency, so signals may get distorted by switching frequencies (notch filters on sensitive signal chain things like ECGs devices) though many are designed for both nowadays.

Things like electric blankets are just resistive loads so there would be little effect, but if they have very cheap electronics it is possible that the timer functions would be analog AC coupled so the timers might run fast or slow.

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?

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)

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.