Doubt it, after reading it myself it is nowhere as calculated and artificial as ChatGPT output

It is a pretty good read though.

Welcome!

Since you're on the lemmy.world instance, there's a bunch of additional interfaces available to you:

• https://old.lemmy.world/ (Something familiar)
• https://a.lemmy.world/
• https://photon.lemmy.world/

If you're on mobile, there's a ton of apps to choose from at https://join-lemmy.org/apps , or if PWAs are more your thing, your instance has the Voyager/Mlmym interface setup at https://m.lemmy.world/

Finding communities used to be difficult, but it should be straightforward now just from the search, seeing as it is the largest instance.

Hope you enjoy your stay 😁

Most likely this IMO, with all the driver and executable signing/integrity checks nowadays I doubt they can get away with patching the system files a la Windows XP style.

May be a better fit in !mildlyinfuriating@lemmy.world or similar

I wish we could do this, but against Nintendo's billions we may struggle a lot.

Yuzu was making 30k/mo and their best option was to quit... we'd need an order of magnitude more supporters to even be able to consider this viable.

The closest thing we could maybe do is donating to the EFF, they're best suited to defend stuff like this. They prevented the RIAA from trying to take down "youtube-dl" for example, an archival tool supporting videos from YouTube and many other sites. The RIAA also used many of the same arguments that Nintendo used against Yuzu

Would be a shame if a little "OVH incident" happened inside the servers hosting Piracy Shield.

Great job blocking your own schools and remote learning systems too, definitely setting a good example of what piracy prevention is all about.

(/s if it wasn't painfully obvious)

🏴‍☠️

A lot of the libcamera work done on Raspberry Pi boards is going towards improving the camera support on linux phones like the PinePhone, which is great!

Aside from that, sadly a lot of people (including myself) are kind of fed up with Raspberry Pi, after they essentially abandoned their mission during Covid to please corporations, and are preparing to go public despite being a "charity". Broadcom, their SoC supplier, also has left a sour taste in my mouth after their purchase and mass layoffs at VMWare.

If they created a phone it would likely end up being scalped to death, and maybe pretty pricey compared to a PinePhone

Wow, now that is literally insane and super awesome at the same time lol

Thank you for the transparency! Much appreciation to the volunteers who have had to unfortunately handle this.

That being said we would like input in what image sites we will be whitelisting

Although I am from another instance I did want to suggest some common hosts, while I use Imgbox personally I often see Imgur and Catbox used quite a bit.

Catbox actually appears to actually be a generic temporary file host though, rather than a dedicated image host

This needs to be a top comment, not a lot of people are aware that the option changes if the site has been developed specifically as a PWA

Wow, this sounds a lot more serious than session hijacking. Are they straight up using Chrome's special token to generate brand new Google Account session tokens?

If so, i'm not sure how Google is going to fix that without wrecking the Chrome user experience for non tech savvy individuals

That's halfway correct - I'll try and break it down a bit further into the various parts.

Your subdomains are managed in using DNS - if you want to create or change a subdomain, that happens here. For each of your services, you'll create a type of DNS entry called an "A record", containing your service's full domain name, and the IP address of your reverse proxy (in this example, it is 10.0.0.1)

The DNS records would look like the following:

• plex.example.com, 10.0.0.1
• octoprint.example.com, 10.0.0.1
• transmission.example.com, 10.0.0.1

With these records created, typing any of these domains in a browser on your network will connect to your reverse proxy on port 80 (assuming we are not using HTTPS here). Your reverse proxy now needs to be set up to know how to respond to these requests coming in to the same port.

In the reverse proxy config, we tell it where the services are running and what port they're running on:

• plex.example.com is at server.example.com:32400
• octoprint.example.com is at server.example.com:8000
• transmission.example.com is at server.example.com:8888

Now when you type the domain names in the browser, your browser looks in DNS for the "A record" we created, and using the IP in that record it will then connect to the reverse proxy 10.0.0.1 at port 80. The reverse proxy looks at the domain name, and then connects you on to that service.

What we've done here is taken all 3 of those web-based services, and put them onto a the same port, 80, using the reverse proxy. As long as the reverse proxy sees a domain name it recognises from its config, it will know what service you want.

One thing to note though, reverse proxies only work with web-based services