zexodus
Is there really no way we can make it technologically impossible for them to exfiltrate user data?
Have the same issue, but can't subscribe to mousepads. I believe that's dust getting in the crevices of the wood.
Possible approaches include transforming the text to MD or minimizing the HTML (e.g., removing script tags, comments, etc.).
If these readers do not use already rendered HTML to parse the information on the screen, then...
https://github.com/poem-web/poem (see poem_openapi)
All you need to do is derive a trait on your response structs and in return you get an almost perfectly generated spec. Unions, objects, enums are first class citizens.
Also, if you're from coming from PHP, the controllers feel very much like symfony controllers.
P.s. Please do recommend an ORM that would feel closer to doctrine. I miss doctrine.
Businesses use data from the user. The Business does additional crunching on that data to derive new interesting data for the user. Who owns the data? The user or the app?
At the very least the user partially owns the data and as such, I'd argue that the user should have the right to share the data between different applications however they see fit. However, businesses tend to think that they somehow have the legal (moral even?) right to keep that data in their walled gardens. For as long as this (imo unfair) stance is common, I think that data extraction by use of these anti-bot-bypassing technologies is fair game.
Web Scraping in a Nutshell: The How, When, and Why Answered
Almost a year ago I've had pretty much an identical idea. Ultimately I got discouraged by the thought that historical data does not correlate with actual stock performance.
Nonetheless, I'm very proud of you for managing to release this product, regardless of the critique you get in this thread.
Best of luck in the future.
#!/bin/bash
xrandr --output DVI-I-1 --brightness $1
xrandr --output HDMI-0 --brightness $1
xrandr --output DVI-D-0 --brightness $1
~