• 0 Posts
  • 178 Comments
Joined 5 months ago
Aquileo | cake
Cake day: March 10th, 2026

Aquileo | help-circle

  • 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.








  • 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.


  • I think it is the other evidence that it is vibe coded

    • Brand new account
    • Dev only responds to non-technical or feel-good comments
    • other commenters have pointed to AI teltale vibe coding syntax signs in many of the files
    • Claude extra files in early commits and changing gitignores to do it.

    Advertised Vibe coded projects absolutely are by default bad and here is why:

    • Developers do not understand what they have built, so can’t debug it beyond “Claude, fix this”
    • Vibe coded projects are easy-come, easy-go very often abandoned (73% of the vibe projects on flathub, and those are the people who thought far enough to decide putting it on flathub was worth it)
    • developers can’t answer any questions on security when the app will be handling credentials, be hosted on a server, or attach to some sort of live service -> absolutely gaping security hole that you just have to cross you fingers that Claude didn’t do another “oops, you are completely right to push back,1500 common attack vectors were left open and you are now part of a CSAM botnet, do you want me to fix it?”

    If someone wants to make small scripts, one-off test firmware for a home project, writing test cases, design reviews, boilerplates, etc… Are arguably good usecases.

    Vibe coding an ongoing software service is almost always a hard no-go and statistically will be abandoned and unupdated, leading to even more security and usability issues.



  • 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.