Muddybulldog

Because nobody has written the code to make it “not function like that”.

No

Disabling IPv4 isn’t going to do anything to move IPv6 forward. You’re just shutting those who remain limited to IPv4 through no fault of their own.

Lemmy, itself, does NOT collect or store IP addresses. You won’t find this information in the Lemmy database/application.

However, your IP address will be captured in the webserver logs themselves, which is typical for any connections to any webserver.

Take a bow.

For me it was $24 for a new oven igniter. That was three weeks ago and it hasn’t worn off, yet.

I really hope you’ve considered how much storage you’re going to need to sustain this.

Instead of embracing open standards they made Metal.

Did DirectX become an open standard when I wasn’t paying attention?

It’s no win scenario for developers. While you’re ok with “one up front payment and then maybe in app purchases to pay for new features going forward” there’s a whole other slew of voices who are going to complain about being nickled and dimed.

Given those choices (and other factors), as a consumer I prefer the subscription model. If nothing else, it lets me forecast my expenditure and continually re-assess the cost/value proposition of the application in question.

I’m of the mind that the truth already is noise and has been for a long, long time. AI isn’t introducing anything new, it’s just enabling faster creation of agenda-driven content. Most people already can’t identify the AI generated content that’s been spewing forth in years past. Most people aren’t looking for quality content, they looking for bias-affirming content. The overall quality is irrelevant.

Somewhat of a loaded question but, if we need to scroll through their comment history meticulously to separate real from bot, does it really matter at that point?

SPAM is SPAM and we’re all in agreement that we don’t want bots junking up the communities with low effort content. However if they reach the point that it takes real effort to ferret them out they must be successfully driving some sort of engagement.

I’m not positive that’s a bad thing.

Looks fine here, here and here so it’s likely not a problem on your side but problems with specific instances. Making a new change to your profile should forward the changes to other instances that may have missed the previous changes. That may be enough to jiggle the handle on the ones that don’t have the current information.

Gotcha… Was just looking… while the 0.0.0.0 URL obviously doesn’t work, providing the proper domain, https://lemmy.mindoki.com/pictrs/image/1fdef263-05e5-48e6-a065-a174a8002f85.png?format=webp&thumbnail=96 works as expected. That means the image was inserted just fine but obviously the URL provided in the client/UI was bad. I’m thinking that at some point you had 0.0.0.0 in your lemmy.hjson file as the URL for pictrs.

0.0.0.0 is shorthand for ANY IPv4 address present on this host. Nobody has an ACTUAL 0.0.0.0

https://en.m.wikipedia.org/wiki/0.0.0.0

No u.

Don’t fool yourself. Lemmy has karma, it’s just not presented in the default UI.

Fitz Benwaballs

I legit believe she could pull it off.