221–230 of 382 posts
Does anyone here use Write.as for blogging? This is the first time I've seen them and the simplicity look appealing to me. For the record I was really excited when Medium came out and loved the simple, open, no-clutter style it had. But fast-forward to today and it's now very different.
This website owner went all nuclear and indignant because they couldn't wait back for a response from Medium, indicating the interruption was because of a bug.
Then they try to backpedal: "We don't get why a particular bug manifested this specific way so we're waiting for more details, but our heels are still dug into the ground".
Secretly hated Medium for a long time. Didn't know everyone shared the sentiment. I'm reading this and smiling.
I don't have a Medium account so I'm not sure if this is still true, but there was once a button in the settings to export your content as a zipball. If you'd like to migrate to a self-hosted blog, I wrote a tool which will convert this zipball into a Jekyll blog: https://git.sr.ht/~sircmpwn/unmediumify If you want, shoot me an email for free hosting, and I'll rig up builds.sr.ht to automate deployment for you, too:…
ooops
Earlier quoted context omitted.
While some interesting and insightful articles still exist on the site, the majority feels like someone trying to explain me what they read on Wikipedia this morning.
Or to sell themselves. Or worse, writing a subpar programming tutorial to have "online presence".
I'm fortunate to have enough experience to tell the wheat from the chaff usually, but holy hell there's a lot of sifting to do. I'm currently studying Python for the first time and the amount of garbage writing on the language I find is frustrating.
Secretly hated Medium for a long time. Didn't know everyone shared the sentiment. I'm reading this and smiling.
The response from Medium was that the service interruption was caused by a bug. This website owner went all nuclear and indignant because they couldn't wait back for a response from Medium, indicating the interruption was because of a bug . Then they try to backpedal: "We don't get why a particular bug manifested this specific way so we're waiting for more details, but our heels are still dug into the ground".
We recently experienced an interruption with API, and the ability to generate new oAuth-based applications has been restricted. I have reenabled that feature.
It was a service outage, they didn’t remove the API.
The response from Medium was that the service interruption was caused by a bug. This website owner went all nuclear and indignant because they couldn't wait back for a response from Medium, indicating the interruption was because of a bug . Then they try to backpedal: "We don't get why a particular bug manifested this specific way so we're waiting for more details, but our heels are still dug into the ground".
They didn't explain why the "interruption" has existed at least a week, or why they didn't notify anyone in that time. Our application doesn't seem to exist in their system anymore, even after their most recent email response. Before this, it was working steadily for two years. That's what we're waiting for an explanation on.
Earlier quoted context omitted.
Around 1997 or so, I got called into a meeting with my boss, director, and head of IT security. I worked night shift in a wafer fab, and someone was accessing the computers in the office, and visiting inappropriate sites at night (that their new sophisticated monitor found). I was young, and into computers, I guess they assumed it was me. I pointed out that I didn't have a keycard that gave me access to the office ar…
How dare someone be excited! I used to have an excite.com email.