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)
Vibe coded warning for people that don’t like AI.
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)
Oh good to know!
At least on my regional product page they don’t say Thread anywhere in the whole page.
This uses Matter, not thread.
This is just a WiFi device using matter protocol
(It has very mixed reviews also)
Just looked at my local 2nd hand app in Belgium. Withing 20km of me, there are 8 macbook air 13 inch from 2015 to 2017 for <=150€.
Not bad, slap MX Linux on it or something light and it would be a great programming, browsing, etc… Small laptop
Eh, emojis in the readme were in nearly every single readme template for years since before LLMs were available. I use them for my own projects just because the readme template I like has them and they make headers much more identifiable when referencing the readme, that is just human characteristics and also why electronics style guides (as an example) have standard symbols patterning for commonly used circuits. Our brains can instantly parse a familiar pattern as opposed to just text (net labels and block components opposed to shaped symbols in the example).
As a bonus for Brave, you can maybe be part of affiliate link scamming networks, their own personal ad spying network instead of google, Microsoft, or apple. You can even have built-in crypto-bro gambling!
Not only that, but all of the drawbacks of chromium!
Also the ad revenue that they make off you can go to funding conservative mass-surveillance candidates and lobbying against same-sex marriage.
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
Advertised Vibe coded projects absolutely are by default bad and here is why:
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.
It is good to note that sleep tracking is one of those things that is kind of a hand-wavy thing right now And it has actually shown to increase anxiety when using sleep trackers when people get less than great sleep, and can make things worse when the algorithm incorrectly estates quality (which all if those proprietary apps do instead of just tracking sleep state).
There is also the issue of comparing with eeg which the head unit that the qualified scientist is also not completely accurate, it is just the best that is readily available.
Sorry that I can’t be helpful, but I dived into it a while ago and what came out of my search was pretty much that it is not reliable and people pay way too much attention to it when they should pay attention to how they feel.
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.
Google (the company) As A Service. Make new things and discard them, unsupported.
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.
Someone doesn’t remember Sony’s original DRM rootkits malware scandal lol
Source that it actually reduces it and the companies aren’t lying out of their asses?
That is a bit of an open source philosophy difference.
Is it better that everyone has open source everything so that anyone who finds the one-off useful can benefit from it?
Or is the software actually not provided “as-is” like the license states and on releasing open source software the community deserves regular updates?
I think that second option is a very entitled path. We are not entitled to the continued used free labor of a random person on the internet.
True, actual steam flatpak is a mess. Opensuse Kappa/Aeon actually use it and it took an afternoon of debugging and 3, barely - documented fixes to get proton games to launch at all.