

Cringe
My username is a wordplay on the Linux command filesystem check: fsck.
Cringe
I thought that might be what they were saying, but then it would be “with regard to to” so I was unsure.
Initialisms like this bug me because they cause confusion for the most minimal amount of benefit.
I’m curious about the reasoning for even using Roku in the first place.
You can disable JavaScript with uBlock Origin
There are other issues with using AI other than laziness or lack of funds for an artist. Especially if you’re using a corporate run AI, instead of a self-hosted model.
I would prefer if they just included a small bit that explains “this art was generated using X model run on Y servers” or something like that.
The lines have inconsistent colors and have weird missing spots, which makes no sense if it was drawn, and they have a weird texture in only some spots that does not result from image compression artifacts. It also has blurring in the darker green details of the skin, like the AI didn’t finish those parts.
Are the images AI generated?
/–edit–/
I’m fairly certain they are.
Better quality version
I’d argue that they can have equally good motivations, it’s just harder to do. A lot harder.
I recently saw a self-hosted imgix/cloudinary alternative. I thought I starred it on gh, but apparently not and I can’t remember the name.
Edit
I think this was it:
https://github.com/imgproxy/imgproxy
But also, on a second read of your post, I now realize what you are looking for is right here:
https://squoosh.app/
It’s open source and it’s entirely client-side. It allows you to customize the settings to compress your image to the file size and format you need and maintain as much as the quality as possible. I can’t think of a simpler solution that works across all your devices.
“I get you don’t think it’s important, but there’s plenty of sysadmins that do, with experience backing that up.” Is a passive aggressive remark designed to belittle me based on a notion that you have experience and qualifications over me that makes your point more valid, and also that other people with experience and qualifications would hypothetically agree. It very clearly implicitly claims that I am not a sysadmin and that lacking sysadmin experience is why I am wrong. This does not add to the point at all and provides, so it could not be seen as any other way than an expression of that. However, I still gave you the benefit of doubt and I felt I expressed pretty rationally that that remark does not add to the comment and is disrespectful and that it may have been unintentional to be disrespectful.
But now “I think this guy just likes to argue.” and “it sure escalated with the other commenter” is clear evidence that you were just trying to be rude. I certainly don’t like to “argue” but much more than that I don’t like to be disrespected. So I will stand up for myself and call out such poor behavior.
Jabba could’ve been NalHutta
To add to that, to effectively use docker and basically anything important for self-hosting is to learn the basics of Linux.
A good resource for that is https://learnlinux.tv
At first I read the title as
How much pareidolia is too much?
And I was bracing for a fun thread, but then my brain caught up and now I’m disappointed.
Yeah, I’m not buying into your trolling. Go somewhere else.
Interesting how you feel the need to disingenuously misrepresent my point.
What registrar was that? Were they as big as Cloudflare? How exactly did they “go tits up”? Isn’t the situation you describe a completely different scope from an individual’s usecase? It’s also an anecdotal point of data without including the full context of how common that situation is. “It happened to me once, and I have heard stories” does not necessarily mean it’s common enough for everyone to prepare for every time. I’ll remain skeptical of the
Mainly, though, I’m not saying it’s a bad idea in total. I just think that for someone who is inexperienced with DNS management and self-hosting, those types of concerns are already unlikely and just keeping the environment simple and cost less has far more value than being prepared for unlikely scenarios. It could even prevent self-inflicted issues by keeping it simple, which would be far more likely than Cloudflare’s infrastructure creating a problem that they have to remediate themselves.
If anything, the true argument for risk mitigation would be to have multiple DNS servers for redundancy.
I just don’t believe that, in this type of usecase, it’s worth pressing for and that there’s more of an argument to keep it simple.
Additionally, you can leave out trying to use your credentials and a hypothetical group of people to make your argument for you. It makes it seem like you’re trying to talk down.
I get that you’re likely exaggerating by saying “it’s no extra work”, but managing another account is markedly extra work. It will also cost extra because Cloudflare does not add any markup for registration, which is why they are the cheapest registrar.
I think the convenience and reduction of cost greatly outweighs the highly unlikely situation where “something goes fucky”. If it does, then what? You can’t make DNS updates for a little while?
The most likely reason to get locked out is billing issues, or maybe you lost your login information or something like that, which is going to be the same risk regardless of who your registrar is. Otherwise you’d have to be involved in some sort of legal issue associated with your domain and that is a much deeper issue than can be solved by simply changing nameservers.
Counterpoint: public votes make it possible to spot users who try to manipulate the platform by voting with multiple accounts.
That just happened recently with a new user account that has been posting a ton. No one noticed they were doing this until they started harassing users and their harassment comments were showing a pattern of upvotes. Who would upvote a user harassing others like that? Well, themselves.