I use it to play music from Jellyfin to my Sonos speakers. It won't fix a Jellyfin library that has bad data, but it can pull in music from multiple different sources and push to different players.
It works well enough. Some issues where songs get interrupted, but I think that's issue with the Music Assistant/Sonos integration.
I developed my own scraping system using browser automation frameworks. I also developed a secure storage mechanism to keep my data protected.
Yeah there is some security, but ultimately if they expose it to me via a username and password, I can use that same information to scrape it. Its helpful that I know my own credentials and have access to all 2FA mechanisms and am not brute forcing lots of logins so it looks normal.
Some providers protect it their websites with bot detection systems which are hard to bypass, but I've closed accounts with places that made it too difficult to do the analysis I need to do.
I scrape my own bank and financial aggregator to have a self hosted financial tool. I scrape my health insurance to pull in data to track for my HSA. I scrape Strava to build my own health reports.
~~Can't be a passive adapter or else that would mean DisplayPort and HDMI have to protocol compatible. If they were then we wouldn't have this issue.~~ Apparently I was wrong.
Just an update. Firefox 146 just dropped with:
After upgrading to 146 and natively using Wayland, it feels faster. Some fade animations are still choppier, but on average it's at least tolerable.
Thanks for the suggestions everyone.
Interesting. I played around with X11 vs Wayland settings just to see what different configurations give me
MOZ_ENABLE_WAYLAND=1 /snap/bin/firefox - Exhibits low FPS issueMOZ_ENABLE_WAYLAND=0 DISABLE_WAYLAND=1 /snap/bin/firefox - Actually feels fast like it should be. Most animations feel faster, some are still choppy though. It's hard to tell.It seems like running with X11 sort of the problem? Which seems unexpected and concerns me since I know distros are starting to default to Wayland.
Yep, both are plugged into the graphics card. Other programs and games are a lot faster.
If the app is just a WebView wrapper around the application, then the challenge page would load and try to be evaluated.
If it's a native Android/iOS app, then it probably wouldn't work because the app would try to make HTTP API calls and get back something unexpected.
On Tor dark web domains, you use the .onion domain. Tor is configured as a SOCKS proxy, so it doesn't perform a DNS query. Instead, Tor itself sees you're trying to connect to an onion domain name. Then it takes the URL and translates that into a public key that it knows how to find in its own hidden service directory.
Only the actual hidden service has a valid private key corresponding to that public key in the URL so cryptography (and the assumption that quantum computers don't exist) ensures you're talking to the right server.
Tl;dr effectively no DNS for onion hidden services
Putting the charger circuit inside the battery takes away battery capacity, so I still buy the external chargers
Unless you're running VLANs, in which case the inter VLAN is normally handled by the router. I also expose my home lab services over BGP so all my traffic hits the router then comes back to my lab services.
Pretty cool. I played around with Dafny at work for some security-related software and I was pondering if Dafny could be effective for other problems like complex web-app state management or even more standard services.