hey all, i'm looking to replace my isp's router (i know that i can, it's basically just DHCP on a specific VLAN) with my own one and i'm looking for recommendations.

here's what i would need out of it:

• best price-to-performance ratio. the larger the NAT table it can keep in RAM the better (i run some things akin to ipv4 scanning)
• OpenWRT support
• at least one sfp port for internet access, supporting 5Gb/s.
• at least one 1 Gb/s ethernet port
• ideally 2-3 100Mb/s ethernet ports
• wifi support: yes (don't need anything fancy, even 5GHz is optionnal but preffered)
• LTE modem: dont care but nice to have

i had a look around the OpenWRT supported devices table but since it doesn't really list ports and i need sfp, it takes a long time to go through and read german router pages.

can anyone recommend a router that meets these at least partially?

If you're a Lemmy dev and reading this, the problem is in pict-rs. I have sent an email to asonix with the needed changes, please tell them to check their inbox (since I can't register on their git server, I can't submit a formal PR).

Send me a PM if the email gets lost and I'll give you the line you need.

If you're not a Lemmy dev: Have you encountered an image that is suspiciously rotated here on Lemmy? Perhaps you even tried posting an image that looks right yourself and found it rotated itself! Why?!

The reason is that Lemmy strips all metadata from images you upload to it. This is because image metadata can contain, among other things, GPS coordinates or where it was taken. The problem is that when you take a picture with your phone in landscape, instead of rotating the image in memory, your phone saves the image sideways (because that's how it came off the sensor) and then adds a metadata tag that tells everyone to rotate the image as they are displaying it. You guessed it, that tag also gets deleted. In most cases, this is fine because either the picture wasn't rotated to begin with, or Lemmy image hosts actually save the properly rotated image before stripping the tag, but in some image formats, this isn't the case due to a programming oversight. I have found the fix and sent it to the person responsible for the image hosting code.