SimonWoods
SimonWoods

We are now into year eight of Micro.blog. Feels like a good time for certain weak spots to be corrected — the kind of behind-the-scenes upgrade that is not at all flashy and worth lots of attention but instead guarantees such stability that you basically never notice other people having problems.

|
Embed
Progress spinner
In reply to
SimonWoods
SimonWoods

One example is money.

I have no technical capability to offer a solution. Instead, it seems pretty obvious to me that there are few areas as damaging for your reputation when compared to handling money.

Two years ago I rambled on about Micro.blog and communication. I'm still unsure if I'd change much about the basic thoughts I have here — too any issues feel like you get the infamous Apple "magic box" treatment, in that when something happens there is a lack of good feedback. Then, on top of that, you can't easily find a broader explanation to help you understand what's happening as easily as you should. Then on top of that things seem to just continue as they were.

IDK maybe I'm just seeing this from my own bubble here, and most people on the platform are fine. That feels like a bit of a coincidence, though, and either way it is disconcerting to see heavy users of the feature hit discouraging hurdles.

Anyway that's my rambling done for now. Got my fingers crossed for big yet barely visible improvements to stability and performance.

|
Embed
Progress spinner
SimonWoods
SimonWoods

One last thing, since I'm trying to work out my viewpoint here:

You know the Apple/Jobs thing, "Privacy means people know what they’re signing up for — in plain English, and repeatedly."

That. That's where I think some great improvements — and again, I understand this would mostly be hidden and not lend itself to a big marketing splash — could be made, only not especially for privacy but for wherever a user interacts with sensitive and/or complicated parts of the platform. I guess I'm advocating for greater clarity all around...

Ok now I'm final_final_done.

|
Embed
Progress spinner