JeremyBanks

I would call that use case very dumb.

My impression is that most people who talk about overpopulation are basing it on old trends before population growth rates dropped off so much.

> You have to go out of your way to trade options (they're disabled by default), and the only way you can get options enabled in Robinhood as a college freshman is to straight up lie on the application.

Could you please clarify, what does the application ask that he would have had to lie about?

Probably a lot more than that.

Dang, you've got a lot of insurrection apologists in your disgusting community. You complicit sack of shit.

Ubisoft+ subscribers can play their games on Stadia: https://support.google.com/stadia/answer/10248037

They should lean into that kind of thing.

And it was great.

Who could have possibly seen this coming?

If you choose to just call it "speech issues", it sounds worrying, but when you're a little more precise, "shutting them down for failing to remove calls for violence including many instances pointed out to them directly by Amazon's lawyers" sounds pretty reasonable.

Is "PG's Submarine" what we're now calling the fascist subtexts of his writings?

nice find

As it happens, even Beaker dropped IPFS years ago: https://github.com/beakerbrowser/beaker/issues/455

I find HEY's general workflow very good for my medium-volume personal email. It encouraged me to filter a lot more stuff out of my inbox than I did with Gmail, while spending less time configuring filters. The ability to leave internal comments on external email threads (business accounts only) is very useful as a first-class feature, instead of relying on fiddly BCC. The apps are quite nice to use. Overall, there's less clutter and it is a more pleasant experience than other email clients I've used... until I try to search in the Hotwire-powered web view.

This kind-of tangential reply is in bad taste, but DHH is currently being an asshole about this very topic on Twitter, so:

This seems cool, but the progress that HEY has made since launch isn't very impressive if that's the flagship example.

HEY's search UX, which uses these capabilities, has been abysmal since the day it launched. It's a much better experience if you disable JavaScript/Hotwire and fall back to the server-side-rendering instead of the hybrid mess they push down. I'm very disappointed that this hasn't been improved. (I sent feedback about this while they were still in their invite-only phase.)

We were also promised custom domain support by the end of the year, and we don't have a timeline or even pricing yet. (That's obviously backend and unrelated to this announcement.) I don't want to go back to Google, but the lack of improvement isn't giving me a lot of confidence as a HEY customer, so I'm considering alternatives.

Regarding IPFS: I'm very disappointed in the progress that IPFS has made. I was extremely excited when it was first announced, but it's taking so long for them to make useful progress they I've lost faith. So many of the projects under their umbrella are incomplete and untouched in a long time.

Regarding this project: Several of the existing centralized imageboards are already breeding grounds for terrorists. The world does not need this.

Transactions are often slow and expensive.

I used to use DoorDash, and tipped very well since I knew the workers could really use it.

And then I learned that the company has been stealing tips from the workers who need it, so that they can make their finances look better in anticipation of this IPO.

https://www.vox.com/recode/2019/8/20/20825937/doordash-tippi...

I haven't used the service since.

It was infinitely ahead of its time when it was new... and then it was abandoned until it was miles behind the competition.

It's the Google Way.

(But truly, the headcount on Google's internal web tooling compared with the size of the organization is laughable. I watched lots of devs burn out trying to improve internal tooling, then quit, because the organization doesn't value it.)

Admiral's paywall is so glitchy on mobile, when I don't have an ad blocker installed but it frequently thinks I do, that I've learned recoil in disgust from any brand that uses your service.

It's valid if you're not reading a generic zip file but instead a zip derived format like this.

This is a good policy in general, but this is one of the most pivotal moments in American history, so much is at stake, and a line must be drawn. The YC community in particular, is full of people who are complicit or explicitly supportive of these efforts, and they need to be shown that they are not welcome.

Except, that they are welcome. Y Combinator has fostered a community with a lot of anti-democratic sentiments.

It's sick, and history will look upon you all with pity and contempt. You should resign and get out.

That's a fair perspective, but that's not applicable here. The punishment isn't because of how much she violated the policies, it's to send a message.

At Google, someone once disruptively modified the root permissions for the entire company-wide monorepo to show off that the permissions scheme was fallible. They were left off with a verbal warning, even though on paper they massively abused their position, and could have made the point without actually doing it.

The engineer in the OP took a much smaller action, that was closer to the scope of her actual duties, but was punished more severely.

If she had injected a BitCoin miner, for personal profit, that would have been an entirely different situation, wouldn't it?

Yes, this is professional writing, which a lot of people pay for, because they appreciate his frequently very-insightful analysis. The intro paragraph is basically an ad because the free articles drive subscriptions for the paid ones. If you can't get past that, move on.

I wouldn't trust them with the physical copy to verify it, so I don't know that it makes a difference.

Users aren't being fooled here. People learn that progress bars aren't accurate, and things like the author mentioned, "when it gets to 75% it will really be done".

The cartridges printers come with often have ~half the capacity of retail cartridges.

If you've chosen to use a web browser that's forked from an old version of Firefox and isn't aiming for compatibility with modern Web Platform Tests, you're going to encounter a lot of obstacles. The fact that you can't see the server-side code generating the failing client-side code, which you can see, seems like the least of them.