Mag lev grip

Yea, I think it was blocked even before our time. Anyway, if it’s no longer a spamfest, then sure it makes sense to unblock them.

There might be more profound reasons for women’s lack of interest in you than money or power.
Exhibit A: this whole comment

It’s in Greece though.

At first my brain processed the images as if the riverbed was a bunch of grey rocks, but it’s actually dead fish floating.
That smell must be something.

Weirdly enough, I can find a PICTRS__MEDIA__PREPROCESS_STEPS variable in pict-rs 0.4.0-beta.8 release notes, but not in pict-rs 0.5.4 readme that lemmy is currently using. I might to check this again after some sleep.

edit: going through the pict-rs source code, that variable is indeed there, just these aren’t in the readme file.
I think TheDude was planning a test instance, this would need some testing first.

Wait, I meant… that version of pict-rs has that feature, which lemmy doesn’t currently use.
I don’t more if it’s something that can be set globally for pict-rs, or if lemmy code needs to be modified to leverage that pict-rs feature.

Yea the error messages all around lemmy could be a lot better.
Sometimes it only times out and you don’t know why.

Lemmy is currently expecting pict-rs 0.5.something which should already have the feature mentioned.
I know there’s a few new tweaks already planned in lemmy, including allowing users to see a list of their own uploaded content, etc. I can’t promise anything just yet but that would indeed be nice.

Unbanned.
Sorry about that, your last post was linking to the same blogspam that’s been linked by a multitude of spammer accounts.

✅

Thanks for taking action and letting us know.

edit: Why the downvotes?

No one can really answer that other than the people who clicked the buttons.
I sincerely have no hard feelings here, but I have to point out the irony of questioning the downvotes you received but not those you cast yourself on kersploosh’s polite request.

PS: FWIW, neither of your 2 downvotes are from kersploosh or myself but rather from random users.

Anyway, thanks for making content and contributing to making this is one of the more interesting communities.

There’s even a few users from June 5th.

• https://sh.itjust.works/u/klaymore
• https://sh.itjust.works/u/this

Ah yea, the “you missed the first 20 minutes window of this post so your comment will be lost into the void”.
Don’t miss it one bit.

A1: probably, although that’s more processing power. The tool I used to fix it would have outputted a second image file if the extra data had been an image, which is then a weird case to handle. (Upload both? Make 2 links?) Certainly, it could output a better error message though.

A2: Should be lemmy-wide, although technically a malicious server could disable that somehow, which I think would only affect their local users. ie: don’t make an account on a server you don’t trust.

A3: It is a server specific setting. It’s easy enough to change the setting. Bigger limits uses more storage which costs money

A4: Possible, I would think. No idea if that’s ever on the devs’ roadmap. I think that would be added to the pict-rs code which is then used by the lemmy server.
Both are open source projects, so an instance implementing this could then share the code so it’s eventually a feature for everyone.

I’ve ran into bugs before on some public image host I don’t remember where it wouldn’t strip metadata if you uploaded an album. It’s probably a good practice to strip metadata before uploading, although much less convenient. I double-check that it still works here from time to time, doubly so after upgrading versions.

Got it.

Your PNG contains extra data after the PNG’s IEND marker which pict-rs probably errors on.
Your images aren’t stored as-is, among other things, their metadata is stripped so people don’t unwittingly share their geolocation, etc.
It rewrites the file in the process, but in this case doesn’t know what to do with the non png compliant data appended at the end.

Here’s a fixed version of your image that uploads fine.

Using pngcheck -vf on the original image will give you the starting hex offset (0x10fc31) of that invalid chunk of data, which can then be browsed with whatever hex editor.
I haven’t investigated that extra data much.
It might be part of a ‘capture the flag’ game, or not.

The fixed image is just the first bytes of the file upto that invalid extra chunk.

Would you mind sending me that file through another means so I can test what’s happening?
Whatever file host, matrix, email, etc.

Thanks

If I recall, the size limit is 5M.

This one is 2.8MB:

This one is 4.38MB:

What’s the extension of the file you’re trying to upload?

I’d like to celebrate early and possibly jinx myself in the process but the line is going down.

Not necessarily.
Thing is, after a few consecutive failures, the next retry is now in a while (later tonight).
This retry spacing at least explains why it hasn’t gone down after the restart

Sadly that line keeps going up.
I don’t have much of an update but it’s really specific to outbound federation and just with lemmy.world.
ie: inbound works fine, outbound with other instances works fine.

We are currently seeing a backlog in outbound federation towards lemmy.world.
Really, this graph says it all… 📈

I’ve restarted the containers, hoping it starts catching up.