fdsfdsfdsaasd

Right. The sensible thing to do would have been to develop a migration strategy as soon as you hear words like "grandfathered" or "first-year discount".

My bad, I took the org name to be "Skyfall". Just substitue "Hack Club" for any time I mention it!

Change "Skyfall" to "Hack Club". It's a bit confusing who is who!

No - it's very clear that the people involved know details that we do not, and are withholding them for the sake of a better story. I have an axe to grind against people who use technical platforms to air mismanaged and misrepresented grievances.

"Blame" is a strong word, but I think it was a mistake to not plan a migration strategy as soon as Slack/Salesforce sent a $200k bill. Even if you have some agent telling you not to pay it, it's clear something is about to go very sideways.

In this case, it looks like Hack Club sat on a gargantuan bill for at least weeks and maybe months (see top comment on this post).

I'm not denying that what you describe happens, but in this case - ignoring the warning signs, letting the issue crash into a wall and then complaining online about it doesn't help anyone.

Right - there is so much context missing. Extrapolating just a little, it looks like the story is something more like "We had too many users for our existing free plan, so we switched to a paid plan that had a first-year discount of 97%. We didn't really pay attention to the fine print, and now we've got a nasty letter demanding lots of money."

Not defending Slack / Salesforce. You just can't deal with them with that level of naivety.

Informed of the final cut-off date, sure!

How long have they had the bill mentioned in the top comment on this post? At the very least it's 3 weeks, and the comment suggests it is months.

How long have you had the bill alluded to in the top comment on this post? For how long have you been in communication with Slack? The top level comment suggests it might have been months, but at the very least it's been 3 weeks (since 29th Aug).

I'm not defending Slack here, but allowing this to hit the wall and then raising a stink online does everyone a disservice.

Edit: by "you", I mean "the organisation of Skyfall". It's already pretty clear from the number of people chiming in on behalf of the company that this problem has been handed out piecemeal.

Why did they switch? Given the information provided, it seems that paying anything, if you're on a grandfathered free plan, is a bad deal.

How long have you had the bill alluded to in the top comment?

Skyfall have had awareness of this issue for months. If you're running a teaching service for kids, allowing this to hit the wall months later while telling the kids it's all someone else's fault is disingenuous and a poor example to set.

Reading between the lines in the top comment on this link, they received a bill earlier this year, and have been in communication with Slack since then.

The transition away from Slack's nonprofit pricing is also a key element to this story, but that is glossed over.

>A few years ago, when Slack transitioned us from their free nonprofit plan to a $5,000/year arrangement, we happily paid. It was reasonable, and we valued the service they provided to our community.

>However, two days ago, Slack reached out to us and said that if we don’t agree to pay an extra $50k this week and $200k a year, they’ll deactivate our Slack workspace and delete all of our message history.

>One could argue that Slack is free to stop providing us the nonprofit offer at any time, but in my opinion, a six month grace period is the bare minimum for a massive hike like this, if not more.

This summary from your website misses a lot of relevant detail. I love to rag on big corp as much as the next free thinker, but the dishonesty makes me much less sympathetic to this particular story.

> Integrated SSH and Telnet client and connection manager

Honestly, ssh re-implemented "open source" in javascript goes beyond anti-feature and back around into "useful for security research".

> We scanned 1338 dependencies and found 94 problems.

Just what I want in my terminal app.

I don't like the endless "security audit" noise, but there are 13 critical issues, some dating back 4 years, and including cryptogrpahy-related flaws (and that's just the top-level yarn.lock).

True enough, but I'd want to be a lot further away from a lithium fire than from a propane explosion.

It would make me nervous, although that's only due to my engineering background.

In any case, it all depends on what you want to stand next to. A large explosion, or a multi-day metal fire releasing clouds of hydrogen flouride.

I once did a related calculation on "How much of my garden do I need to dedicate to coppiced willow to heat my house for a week per year?"

I concluded that we're all going to need much bigger gardens.

None of those release hydrogen flouride when they burn (among other things).

Compressed hydrogen is no joke. It can escape most containers, actively degrades many grades of steel, has a very low ignition energy, and will explode over an enormous range of air/fuel ratios. Definitely not something to keep anywhere where you care about the roof :)

That knowledge is not illegal, nor would it necessarily be illegal to write it down.

I can't belive that people have been fooled by the environmental credentials of "paper" straws.

Yes, a situation that Google is steadily fixing.

I imagine most people are using those monitors for text-based applications, which have a much lower rate of pixel change. Still - the pixel switch lifetime is currently a limitiation of eink.

That's about the worst use case for existing eink panels, as they have a limited number of switching cycles before the dots start to degrade.

For dynamic content, a higher refresh rate absolutely will lower an eink panel's lifespan. As the refresh rate increases, more of the underlying content's changes will be captured and more pixels will change state.

Unless you are switching every pixel with every refresh, the panel will last longer than that. However, it's still a huge limitation on its lifetime.

Waveshare specify 1 million switches per eink dot for their panels.

https://files.waveshare.com/upload/4/4e/2.13inch_e-Paper_V4_...

https://files.waveshare.com/upload/6/60/7.5inch_e-Paper_V2_S...

That's a separate effect - eink degrades under UV. Fossil eink watches did not have enough UV filtering.