fartsparkles

This is based on Snapdrop. If the current developer hasn’t gone crazy with the fork, you can read the entire source code over a cup of coffee. The server used to just handle discovery/handshake of devices on the same network, with file transfer peer to peer using local addresses.

Edit: Looks like they’ve added transfer over WAN not just local. Privacy discussion here.

I miss the classic Ctrl placement. I still remap Caps Lock to Ctrl to this day.

Exactly. Beating them up for being late has more risk of them dropping plans altogether. Celebrate their plans, they’ll want to execute on them.

CVEs don’t get issued “resolved” statuses… They are either reserved, published, or rejected (technically NVD have a few extra for published). That’s just junk data in that tool you’re using. Use authoritative sources like cve.org or nvd.nist.gov.

You can see the CPEs on NVD and they’re old versions of Plex.

You’re aware those CVEs are only relevant for ancient versions of Plex and were fixed long ago?

You’re going to need to back up your claim otherwise you might as well be lying as there’s no CVE like this I can find nor any public disclosure.

Plex have a bug bounty program and a responsive security team too.

Post your security report.