@Docker could someone update the official `whalesay` image? It hasn't been updated in 9 years and is throwing errors: https://t.co/RWgdePoM4G, https://t.co/XBSSsE6NNd. It's used in "hello world" examples across the internet that are now breaking ๐
@Starbucks Refreshers have caffeine in them without mentioning it??
Thought Panera Charged Lemonades were bad but at least it says "charged"...
As a migraineur, people bought me this thinking "he can't have caffeine so I'll get him a Refresher" and now I can't get out of bed ๐
Congrats to our newly promoted maintainers!
Anton Gilgur (@agilgur5 ) to Approver in Argo Workflows
Christian Hernandez (@christianh814) to Reviewer(docs) in Argo CD
Ashutosh Singh (ashutosh16) to Approver(docs) in Argo CD
Isitha Subasinghe (isubasinghe) to Approver in Argo Workflows
@github Problem has been resolved. GitHub should perhaps not delete all repos in a scenario like this as it can break ecosystem usage very quickly (especially in Go, which relies heavily on git for packages)
Retweeting for reach. Anton maintains several popular OSS projects that are hosted on GitHub that now all 404. Could someone @github help escalate this?
@LinuxSuRen@antonmedv@github You can match the commit SHA of a previous version.
@antonmedv wouldn't have access to add retroactive tags unfortunately (not sure if anyone else has access to that repo).
Hopefully everything is back to normal shortly though!
@TerryTangYuan@antonmedv Also for other readers, I did manually verify that the most recent commit SHA on the fork matches an existing previous SHA: https://t.co/nCObyL4Cn5 is the same as https://t.co/PLxoiIptvW.
@fitbit @FitbitSupport The new models don't have this defect since the band doesn't attach via super glue, but I wasn't offered a newer replacement. The warranty expired after a year of replacements, but the Charge HR was a lemon to begin with.
@fitbit @FitbitSupport I used to own a Charge HR that broke 3 times (below) due to its super glue construction until warranty expired.
I have a heart condition now and need a tracker, but while I love yours, I'm hesitant to buy one after such an experience. Anything you can do?
I've only got a ~decade under my belt, but hard agree
Without even getting into complex human interactions, even simple problems can get significantly more complex when you add a human component to it, e.g. "building the right abstraction" in a library: https://t.co/AhlMhceyai
The first half of my career I thought technology had hard problems to solve.
The second half of my career, I realized that people were the source of more problems that were much harder to solve.
As someone who has been both promoted several times as well as fired for "Doing The Right Thing", this really resonates.
No one really talks about the "embarrassment", the shame, and the *trauma* that ensue for the coming years. Thank you for sharing @jsnover โค๏ธ
When I was doing the prototype for what became PowerShell, a friend cautioned me saying that was the sort of thing that got people fired.
I didnโt get fired.
I got demoted.
@SouthPawNZ Getting toxicity and abuse for volunteering 1000+ hours also made me pretty suicidal, as one can imagine.
I'm in intensive therapy now and hoping to start contributing to OSS again soon (gradually). I remembered this tweet so just wanted to finally say thanks for the support โค๏ธ
@SouthPawNZ Thanks Alex โค๏ธ Any kind words help!
My status has been up for over a year and you're the only one to acknowledge it so far. The experience was so traumatic for me that I went from multiple daily contributions for over a year to almost 0 in the past year.
@Makste2 @slicknet A fee for implementation wouldn't cover it -- you'd also need a recurring maintenance / upkeep fee (tbh, maybe a cognitive overhead fee too).
That's without getting into that most OSS is side-projects: you have a finite amount of time and not everything is worth your time.