Especially with music, if any of this is plain HTTP (or any other plaintext, non-encrypted protocol) and you live in a lawsuit happy jurisdiction you might end up with piracy letters in the mail.
Especially with music, if any of this is plain HTTP (or any other plaintext, non-encrypted protocol) and you live in a lawsuit happy jurisdiction you might end up with piracy letters in the mail.
Yeah the “whole thread” goes off about iOS 18, so my bad for assuming people were using iOS 18. 😒
Though you’re right, the entire thread is pointless. I’m considering blocking this community because it feels like everyone’s got an attitude problem.
So you prefer they don’t take any feedback at all so everyone can complain about it and they’re never made aware of the issue. Okay 🙄
iOS 18 is in beta, which means you should be using the Feedback app to report stuff like this. Apple has actually been very good at responding to me about stuff like this, so I actually encourage you utilize the app.
I’m thinking of building my own and having it use Paperless’ API for invoices, receipts, etc.
I finally gave this a go a few days ago but wasn’t in love with the UI. I’d contribute but it’s written in .NET.
I’ll probably build something myself. One thing I’d like to do is have it integrate with other APIs (like Paperless).
I’d curl
from a machine on the same WiFi network as the phones just to confirm that HTTP is working. That way you’re not dependent on browsers that can be more finicky for debugging.
I’ve noticed that but I thought I just didn’t know how to persist it correctly and never bothered to find out how. If what you’re saying is accurate (which I don’t doubt) that sucks.
GL.iNet actually has a decent UI too. When I’m on the road I don’t necessarily love hitting the CLI (okay fine I secretly do); they keep the updates going for a long time too.
No, mesh networks’ APs use WiFi to connect to each other so that eventually client traffic reaches one that can finally route to the wired network. Client traffic doesn’t go through one AP to immediately reach the wired network.
I’m talking about a traditional network where everything is wired together using Ethernet (probably to a switch) so that client traffic on the AP immediately reaches the wired network from that AP without that AP then relying on another one to reach the wired network.
This arrangement is still common today on business networks and was so before the term “mesh” became popular in consumer routers.
Finish it off with DNS-based blocking. Tons of websites and apps stalk you via their shady tracking APIs you might never see.
Thanks for this: so sick of seeing “mesh” WiFi everywhere, what a load of trash. Just set up access points with roaming capability, actually use the correct broadcast power (instead of trying to blast it off to space), etc. I’ll never understand why people want their backhaul going over WiFi; yikes.
I didn’t have a great reason other than mind-blowing performance on my LAN, and with large files (which I have a lot of) performance is better too. Probably I’m not smart enough to answer this well, but I did just see this today: https://www.phoronix.com/review/linux-611-filesystems/2
I’m a huge fan of XFS for network mounts. I think everyone else here is right that the best filesystem will depend on the OS, and picking one to make it compatible with everything has serious tradeoffs.
How is VPN on airline wifi? I’ve yet to try it out; I usually just listen to a bunch of music I’ve downloaded ahead of time.
I’ve just discovered this today too! I’m not even sure how to find my key (Proton user too). I’ve admittedly not spent too much time understanding PGP since basically no one uses it.
pfSense is UNIX-based and those commands are generally included with Linux and probably Linux-specific.
I’m running a Raspberry Pi 4 with an array of hard disks. Essentially the entire OS is on a small SSD but because I have so much data I’ve got two traditional HDD drives with XFS and LUKS disk encryption.
I’d say overall it works fantastically, over 802.11ax and Samba I’m pushing about 600-700 Mbps while transferring to the HDD drives.
I usually play around with travel routers and OpenWRT but if I had an old router laying around maybe I’d do something fun with it.
Plain HTTP means anyone between you and the server can see those credentials and gain access.
It it using HTTP Basic Auth by chance? It would be so easy to put nginx (or some other reverse proxy with TLS) in front and just pass the authentication headers.