She's beautiful, is there more of her online?
mystik
Don’t UWU! That’s a $350 fine!!!
“Goodbye, Earl!”
It’s not the Muslims, it’s the evil Christians. Same problem, but different names.
It's uncommon for 'public use' ethernet ports to exist, unless they are clearly labeled. The ethernet ports might grant access to the internal network, which, is easy to accidentally do. A non-profit library with a limited budget might overlook all the extra protections on open ports (enable/disable ports as needed, use 802.11x port-based authentication, internal SSL, etc), that would be necessary to secure it. Or, even better; that RJ45 port might be wired up to an old PBX, and you may have fried their telephone system, or your own hardware.
The Germans have Russians. :-/
Passkeys are great, and generally a plus for security; but (a) all the most popular implementations have not implemented key export and transfer to alternate implementations (b) It includes an implementation ID + hardware attestation feature which can be used to disable 'unapproved' implementations by key consumers. Considering the most common device with a 'secure' environment, and can implement this are your cell phones, and they are made by Apple + Google, this effectively locks your identity to either of these platforms. (c) All the public signals smell and look like the providers (apple, google, Microsoft) are doing everything they can to implement the features to make lock in all but inevitable, including mandating that implementations user-hostile features, or risk being rejected by sites.
It's a great idea, and it could be awesome, but things are not being addressed. Or being handwaved as "we can address them later". This recent discussion from last month (both the discussion in the linked github issue, and in the HN thread both including some key players in the PassKey system) is pretty telling: https://news.ycombinator.com/item?id=39698502
In fact, it can be better: having root means you can arrange additional 'firewalls' between apps and your data , or omit/falsify sensor data the the banking app should not need, that the Google is unwilling to implement.
https://pairdrop.net is FOSS, cross platform, realtime, peer-to-peer, and only needs a browser. You can host your own version if you prefer. In contrast, Firefox Send (also FOSS) was 'asynchronous' (you could upload, and then email a link), but it was shut down due to abuse. https://github.com/timvisee/send is a fork of the archived github project that you can self host with many improvements, notably authentication, so only yourself and trusted users can upload. (edit: wrong link for ff send)
Here's the REAL reason: Apps grant Developers/Content owners more control/metrics/data about the user to feed their advertisers, which translates to more revenue. It's way easier to hoover up data about the user outside of the browser sandbox, and in apps.
I wish I knew, but the ad industry LOVES this tech: https://duckduckgo.com/?q=smart+tv+ACR&t=ffab&ia=web Every other result is "How ACR is going to be awesome for advertisers/marketers". the ones in between are "How to shut off ACR" :-/
TacticalRMM is very comprehensive, self hosted, but more geared towards organizations managing a fleet of machines.