At first i read "immoral avatars".
At first i read "immoral avatars".
They aren't that dumb
Gone doesn't mean there will be no replacement. It just tells, that the replacement will not be the same file. So you can re-request the URL, but you should not try to resume a download from there.
> 2) People will be more wary to publish anything on the web. Also known as self-censorship.
Actually you NEED to be wary. If you publish something, it is there, it will be copied, screenshotted, archived
You should not censor yourself. But maybe you choose the use your anonymity online. Even a anonymity which isn't anonymous against your hoster is anonymous against archives. You do not need to put your name next to everything (dumb) you say online. An interesting opinion is worth a read independend of the writer.
There are already flags like "noarchive" to get google to index the site, but not provide public "google cache" links (you can assume they still cache it, but that doesn't matter for you).
So archive.org should ignore noindex directives, but not noarchive ones.
Firefox crashes once a day here since version 52 and even with 53. With 51 it was stable. Possibly Quantum is more the problem than the solution?
emacs would at least add a nice video player, to the software.
> Use standard buttons, standard borders, standard colors, standard fonts, standard everything. Don't deviate from the standard, unless you really have to.
The problem is, the projects changed the standards to utter bullshit.
checkbox? Too easy, make it a slider! Write to the left and right, what the directions mean? Too ease, write it below the sliding part. Yeah, who cares, that moving the slider to the side with the text "ON" now turns it off and shows OFF on the inactive side. We color it to show, if it is active (like checkboxes before). But lets not make it obvious, choose the colors so, that the user first needs to see both states, to decide if he thinks the thing is currently active or inactive.
Android, Gnome, i look at you.
> Ever thought that your workflow may need improvement?
And when my workflow needs improvement this means YOU should decide how i need to change it?
Give me more options, but DO NOT change how it works for me now. An upgrade may give me the chance to change the workflow, but MUST NOT change it without my consent.
This is what many softwares get wrong, i.e. MS Windows and Mozilla Firefox.
Hey, making up a "syndrome", even with cool acronym (btw. why didn't you try to fit it into DISMISS?) may be a start, but your post is just a 3/10 on the logarithmic troll scale.
because it shifts the burden from the user who says "i do not care about dDoSing somebody else" to the producer, who says "i cannot afford angry customers".
Why 52? Before there were some removal steps and later there will come some more until firefox changes its principles with 57, when XUL is deprecated and all extensions not built on top of webextensions api (still unfinished and not so powerful) will be discarded.
Shouldn't only patches (which proved to be stable in the nightlys) be PORTED to beta? Moving a whole release just moves all the experimental features as well
> VPN reduces this fine tuned envelope information to "when your LAN is passing data, and how much", leaving out the very relevant "...and to whom" part.
This is wrong. They see only traffic to the vpn gateway and a properly configured vpn doesn't leak dns queries, either.
This is a half truth. You can get the spoken words from an compressed VoIP stream, just by the traffic pattern how good the compression works on different words. There are a lot of pitfalls, some of them are for example why SSLv3 is now fully deprecated, others only affect certain ciphers.
Its very complicated to keep up with which encryption really works. On the other hand most isp probably do not try to crack your vpn connection, yet.
It is masked but always present. I don't know who built to it. It came before the first kernel.