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

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



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





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



  • There was a rash of people shoveling kanban “first project”-ware for a year or two a while ago. Everyone and their mother made a kanban app and advertised it on reddit and Lemmy. All also abandoned within a few months and were exceedingly mediocre to begin with.

    Just because you made a project, doesn’t mean you have to advertise it as a maintained app, especially if it is one of 1k of the same projects.

    I think the problem partially is people thinking they have to “get a following” and get “github stars” on everything they make in order for it to be a valuable experience.