Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
c3r38r1701982236dI hope you put those spaces with the console...
Needs an add-on. :-)
Or just the option to let you view full URL's...
What I really hate is when folk post a shortened URL, and then, a few years later when you are reading the message, it doesn't work !
Similar with hosted picture links, where all you get is a blank picture !
I used to like that search engine that if you came across such a picture, and there was picture info, like size in pixels, and size of picture in bytes, you could search for exact matches and sometimes find it that way. (But I don't think any modern search engine has that option now do they ?)
'Ctrl + V'.split().join(' ') is faster.
Sorry I just couldn't help it.
Early analysis of the situation brings up a couple of interesting points.
First, their storage was only @ 30% capacity, even though it was was reported as a full storage issue, it wasn't !
Things broke when someone (That's me!) commented to sometime else's message so quickly after they posted it, that my message arrived in the system, whilst they was in the process of deleting their message.
The system has two doorways, each with its own database, that is supposed to sync with each other, which is does about once a minute..
It's obviously not designed to handle a lot of traffic at once..
So, one database deleted the message, the other allowed me to comment on the message, thinking it was still there..
I guess things got in a bit of a tizzy and something broke both databases. (Perhaps in different ways, since they are both different architectures..)
When they first introduced this, I did test and try to break things, but I couldn't..
So I thought it was robust..
Of perhaps further interest, one database doesn't have an API for access, whilst the other one does.
Not all the API calls are coded, some are just empty, so they don't work !
And API calls trump the other database, so if someone tries to stop you doing something you aren't allowed to, you can just use the API to override anything you want, since the API doesn't check permissions..
They might fix it one day.. (It's only been like that, 10 or 20 years, and I think they are on version 3.0 of the API now..)