hsdropout

The Death Ship B. Traven https://app.thestorygraph.com/books/a4ebe2f2-14d3-4da3-a865-...

One Man's Wilderness, 50th Anniversary Edition: An Alaskan Odyssey https://app.thestorygraph.com/books/44f995ae-fa5a-4641-a696-...

The Experience of Insight: A Simple & Direct Guide to Buddhist Meditation Ram Dass, Robert Hall, Joseph Goldstein https://app.thestorygraph.com/books/7588c259-a0c0-4481-81ed-...

A Briefer History of Time Stephen Hawking, Leonard Mlodinow https://app.thestorygraph.com/books/c10780bc-8dcb-4620-9193-...

Code: The Hidden Language of Computer Hardware and Software Charles Petzold https://app.thestorygraph.com/books/92559554-10f1-4cdf-8a9b-...

The Code Book: The Science of Secrecy from Ancient Egypt to Quantum Cryptography Simon Singh https://app.thestorygraph.com/books/6dd5c507-7098-4aef-b0de-...

It seems we generally have trouble removing emdashes and phrases like "load bearing", even when we're looking for them. Identifying and removing subtle contractions, or less visible nuances will be tough, especially if they change to avoid detection.

That's not 2FA, that's two of the same factor.

The factors are:

- Something you know

- Something you have

- Something you are (biometrics)

Aha good point, my bad.

This has been in their guidance since at least 2017.

"Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator"

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.S...

Also worth pointing out that NIST doesn't set policy, so unfortunately this doesn't directly "forbid" anything, though many other policies reference 800-63.

Do non tech people run Linux? I've not seen this.

Discussion here as well:

https://news.ycombinator.com/item?id=41370877

Agreed. This is also a feature of Microsoft's Purview product:

https://learn.microsoft.com/en-us/purview/insider-risk-manag...

I'm glad to see https://isevenapi.xyz/ made the list.

This was recently decided by the US Supreme Court.

https://apnews.com/article/supreme-court-social-media-biden-...

1. Don’t smoke

2. Try to maintain a healthy weight

3. Reduce your meat intake

4. Avoid ultra-processed foods

5. Drink less alcohol

6. If you notice anything you are worried about, see a doctor

7. Keep up to date with screenings

8. Get physical

9. Wear sunscreen

10. Manage stress

11. Look into genetic risk

12. When faced with a diagnosis, knowledge is power

13. Don’t fear treatment

14. Talk about it

15. Live life to the full

I sometimes use these in Windows when I expand characters with FormD[0] as part of username validation.

If the expanded count doesn't match, a diacritic might be present.

[0] https://learn.microsoft.com/en-us/dotnet/api/system.text.nor...

And the other 50% is concentrated power of will.

Are you referring to the first amendment? If so, this allows you to speak against the government. It doesn't prevent you from entering optional contracts.

I'm not making any statement about the morality, just that this is not a 1a issue.

Apparently I phrased my response poorly. I was responding to the narrow context of the idea that devs aren't using Azure VMs instead of Macs. I was not disputing the popularity of Azure.

Previous submission from 4 days ago:

https://news.ycombinator.com/item?id=40226114

>Windows on Azure

Lol, citation needed if you actually believe this.

>or Microsoft oriented stacks.

is a very complicated way to say Windows desktop.

Of the organizations that have Exchange Server on premises, I'd bet the lions share are hybrid, with regular user mailboxes in the cloud, using the server(s) for application relays, etc.

Not sure if I'm missing your intentional irony, but NIST was one of the best places to send folks who think user password rotations are a good idea.

I said "was" because pretty much everyone has now caught up, but NIST updated guidance shortly after big breaches were able to be studied.

> Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.S...

>I’ve never ever received spam from GitHub.

I wonder how long they will keep investing in both GitHub and Azure DevOps. I'm worried they are just busy ruining other experiences at the moment, but enshittifying GitHub is on the list of things to do.

Or tint people yellow to make a point: https://www.theblaze.com/news/joe-rogan-accuses-cnn-video-di...

Thanks,I have read this concern before but was not aware it was part of the design specification.

What gives people, especially in the west, the confidence to use it at all, given all of the fusion centers and likelihood of parallel construction? Perhaps this is a rhetorical question...

This implies the browser is pretty sold, but what about the network itself? How do we know all of the traffic isn't deanonymized due to a big company or government having control of a large number of nodes?

Apologies for not bothering to research this question in advance.

Blammo's best seller!

Can be done with a combination of client groups, like this:

https://discourse.pi-hole.net/t/client-group-management-how-...

In this PDF there is an example of a controversial output in response to an image for job applicants. The "solution" was to decline to answer that category of question. This doesn't feel like a reasonable approach, as it will become a game of whack-a-mole.

This also seems to acknowledge that the model has deep bias-related flaws and instead of treating the causes, they are going after symptoms.

I like this one

https://tls12.xargs.org/

&

https://tls13.xargs.org/

Unfortunate a settlement was required for what was obviously domain squatting.

The Water Knife. ISBN 978-0-385-35287-1

Dystopian-future novel with a backdrop of water scarcity in the western United States. A "water knife" is a name for a security contractor who enforces water rights...