The upcoming "Feature Policy" is now called "Permissions Policy":

w3c.github.io/webappsec-featur

We already updated the relevant part of our Web server security series: infosec-handbook.eu/blog/wss3-

Keep in mind that the Permissions Policy isn't supported by most web browsers, so you don't need to set it at the moment. Clients ignore it.

#FeaturePolicy #PermissionsPolicy #webserver #security #infosec #cybersecurity

dustri.org/b/i-wont-buy-ebooks

Ebooks with DRM suck. We should always try to buy them from stores/places that don't use this kind of crap.

"Catalina is checking notarization of unsigned executables"

or in another words:

Apple is tracking all the executables you run on "your" computer

lapcatsoftware.com/articles/ca

wow, I have no words for this...

"Google bans Podcast Addict app after 9 years for letting users play podcasts that reference COVID-19" -> reclaimthenet.org/google-play-

"Google bans my events app for referencing Covid-19, or related terms"-> news.ycombinator.com/item?id=2

"Ask HN: How long has Google been censoring YouTube comments critical of China?"-> news.ycombinator.com/item?id=2

"Google deletes “communist bandits” 共匪 comments on Youtube globally."->news.ycombinator.com/item?id=2

🤔 Is there a new trend here? or just an old one?

A list of security related tools. Perhaps we can find something interesting there:

tools.tldr.run/

Disambiguation time

Multitasking when a computer works on several problems at once.

Prallelism is when several problems are being worked on in a single time slice. Concurrency is when one problem is worked on per time slice, but the problem being worked on changes from slice to slice.

True parallelism requires one hardware thread (or CPU core) per task. The kernel offers preemptive mulitasking as an alternative for when CPU time is over-committed (which is literally always, and badly); it "pre-empts" tasks and switches between them in each time slice, which is effectively a kind of transparent concurrency.

Cooperative multitasking is the opposite of preemptive multitasking, and in this case each task decides for itself when to relinquish control to another task. A common way of achieving this is coroutines.

A process is a task with its own isolated memory space. A thread is a task within a process, which shares its memory space. Multithreading is using multiple threads, multiprocessing is using multiple processes.

Did I miss anything?

Show more
Social feed

This is a personal and private instance.