7,467 karma · joined December 20, 2013
I always appreciated the rare times when an application would use something other then "File", such as "Game" or "Room" for chat apps.
While I don't agree with some of the suggestions I appreciate the author took the time to at least propose solutions.
Men seeking same-sex encounters transformed the pissoir into something its planners never intended. Who ultimately determines the meaning of a public space: its designers, authorities, or the people who use it?
The law determines that public space can't be used for any sexual activity.
I'm not sure what constructive classroom discussion you can have when the example is based on the law being broken.
I use the Maildir format so each message is its own file making it atomic.
It's your sign to move on, there are hundreds of other cloud providers who will actually provide meaningful human support because they need your business unlike Google.
If you don't set hard boundaries it's also the fast track to great burn out.
And you will be ordered exactly where to put that text down to the pixel.
However your design system will be built around a twelve column bootstrap layout which your designer won't follow because "an experience can't be constrained by columns"
My experience has been you'll be regularly moved around to mitigate the "bus factor"
If you're seen as highy capable you'll be moved on to firefighting duty.
I say "wherever" because if they were paying attention to the licences of their sources they'd see the artwork was named for a landmark wasn't in Sydney.
Although I guess if the rights holder never knows about it, nobody is going to enforce the rights, probably hard to even prove it by the time its been butchered and cast into metal.
Why is it considered acceptable to test on paying customers without letting them know or giving them a way to opt out?
As much as Claude's style frustrates me I can't say I'm willing to pay for double the tokens to fix it.
Although then you get a possible delay of undefined duration, additional questioning and seizure of your device.
Not sure even rare books will dig these big AI companies out of the hole they're digging for themselves.
Companies are immune to bad PR in this fast news cycle. Everyone has already moved on to the next injustice in less then 24 hours.
Surprisingly you'll even get downvoted for "living in the past" if you attempt to bring it up later.
I'd be worried about how much they'd be charging for access once they had the monopoly on so many rare books.
You don't need a final answer but you can't just answer "I don't know" otherwise you risk being slimed (shout out to anyone who still remembers "You Can't Do That on Television")
Unit tests already mock network calls so create mocks to return errors instead.
Call the function multiple times and ensure it'd passing the expected wait durations in for each time it's called followed by a fatal error after say 30 seconds.
It's Microsoft, if they can't afford to do comprehensive unit testing, what hope do the rest of us have?
The mother would not look away from her phone while she sort of tried to answer her.
Truely heartbreaking to watch.
Symptomic of a wider trend to avoid showing the user any error at all costs, even if that means they sit watching a spinner for 7 hours.
> Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service.
The detailed root analysis tries to pass this off as a "bug". You can't seriously tell me client retry doesn't have a unit test which ensures the retry back off behaviour is functioning exactly as designed. In this case aggressively to try and hide problems if token service responses become flakey.
Pro $49/month
- Includes $49 of usage a month
- ≈ a few hundred active end-user sessions
"You are Vendo Auto, a safety judge for tool calls.",
"Choose run only when the call is appropriate for the user and context.",
"Choose ask when user confirmation is warranted, and block when the call must not proceed.",
"Return a concise rationale grounded in the supplied call, context, directions, and recent activity.",
The version page [1] should show that for 86 minutes there was a version 0.3.10, it was malicious and was deleted with a link to the advisory. I get this takes time so even a generic "deleted" entry until they have time to link in the advisory would also be fine so we know something is happening.
Presumably even "deleted" crate versions still have some metadata left behind in the backend so this should be surfaced.
We shouldn't need to resort to pasting `find` commands [1] into the shell from blog posts to tell if we're compromised.
`cargo audit` should be reporting if these packages have been downloaded. The "What you need to do" section of the blog should be run `cargo audit`
> Not having an advisory INSTANTLY available isn't a sign of a decaying org. Chill.
The GitHub issue was opened 8 hours ago. The cargo.io team also acknowledged it 8 hours ago. [2]
> [3] is no longer true.
Previously published versions shouldn't just disappear from the list. There's still nothing there to indicate a version was yanked.
[1]: https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on...
[2]: https://rust-lang.zulipchat.com/#narrow/channel/318791-t-cra...
Jarred spins it as "pre-release" [1] but it was pre-embargo.
[1]: https://bun.com/blog/bun-in-rust#loops-that-write-review-cod....