![](https://sh.itjust.works/pictrs/image/a61496ac-881d-4e4f-8bd9-b104b7a9b86b.jpeg)
![](https://jlai.lu/pictrs/image/bf05fc72-518c-436c-870f-e2cf0465014e.png)
Après, il y en a combien qui sont pareils, mais qui n’ont pas la casquette?
Après, il y en a combien qui sont pareils, mais qui n’ont pas la casquette?
Haven’t had to use port forwarding for gaming in like 30 or so years, so I just looked up Nintendo’s website…
Within the port range, enter the starting port and the ending port to forward. For the Nintendo Switch console, this is port 1024 through 65535
LMAO, no thanks, that’s not happening.
For your question, you could likely route everything through a tunnel and manage the port forwarding on the other end of the tunnel.
Report posts or comments from that user with an explanation in the reason. Their home instance admins also receive reports.
It’s times like these I can kinda understand why pillories have been a thing.
Faking stuff on 4chan? A lie on the Internets?
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.
You’d think so, but no.
Short story is the ‘nominal’ size is the size before going into a planer to smooth the faces.
Yes, it makes little sense, like many things related to construction stuff.
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?
That’s just how it shows up when a community is banned/removed by a local admin though.
They used the same feature as everyone else:
I’ve used it myself plenty enough.
Fuck Grad, but this part is patently false:
using special code no other instance can access
So I recently had a conversation with some who though Linus Torvalds (kernel) and Linus Sebastian (Linus Tech Tips) was the same person.
That was a pretty funny and confusing conversation.
In cod we trust
Just restored the comment and unbanned the user.