Jiocus
Joined 6 years ago
Joined 6 years ago
I want to thank my father for giving in and purchasing Fable for me when it hit the shelves. Fable II was my favourite, a fantastic game.
You namedrop three(?) artists and insinuate something about two legal frameworks - but provides no arguments or context why they should've been a natural inclusion in the article or how your critique relates to it.
Is that.. yes, a low value comment.
User-agent: *
Disallow: /
And possibly allow-list the ones you accept. This probably won't change the fact that you may allow a vendor at one point in time, only to realise they changed their crawling use case and has been scraping data for AI training for the past 6 months (before they go public about it).It can be argued that if you are a server operator, you always know which User-agents are making requests to your resources.
"You're likely to stay in the social class you were born into" - is basically what the predictor means.
It's where I'm from as well, and as a young kid, me and friends would visit the houses in the village at the date mentioned, and receive candy (or else!). It's very similar to the trick or treat tradition during Halloween.
Spotify will only repeat a song during shuffle if you also activate repeat. It will also repeat a song if you actually added the song twice or more to said playlist. You can try it out by shuffling a playlist+deactivate repeat then check which songs have been queued from start to finish.
Smart Shuffle -despite the name- is more a playlist function than a shuffle function. It's like the Radio playlists but with the songs interspersed temporarily in your own playlist. Note that these songs were not already in your playlist - so they do not repeat unless you activate repeat.
ffmpeg -i $input_file -movflags use_metadata_tags -crf 22 $output_file
Source: https://video.stackexchange.com/a/26076In my opinion, it's consideration as unsafe isn't intended literally. It has more to do with:
- The human error aspect of understanding and tightly implementing CSP,
- Separating style and JS into their own files provides some security as is (and allows ignorance of CSP to continue even though it has it's use case here as well).
Now, if your company takes this pretty seriously, they likely require that CSP should be part of your security process already. If that's the case, any use of unsafe inline in your markup will be blocked by default until concrete steps are taken to have nonce or hash in place.
Edit: I did not intend to sound harsh - just wanted to chip in about the nuances about the possibilites we are provided :)
---
[1]: https://web.dev/articles/csp#inline_code_is_considered_harmf...
[2]: https://www.w3.org/TR/CSP/
[3]: https://content-security-policy.com/nonce/
I named my project panopticon inspired by the original idea.
On the other hand, I don't think it's application on humans is ethical nor effective, but for devices, maybe.