Web 2.0 sucks sharp pebbles and canal water through a dirty straw
stormrider.io
stormrider.io
Bad UI is bad UI. Could be web 2.0, could be an app, could be web 3.
Have you seriously not heard about using different browsers for different accounts on the same site ? Many Androids will even let you install the same app twice to use different credentials.
So basically, a lot of software is badly designed, coded, and unsafe. Yep. And apparently people are trying to blame "the web" for that ?
BTW, there's no way to navigate your blog now ? That's good design ?
BTW, there's no way to navigate your blog now ? That's good design ?
<title>‎</title>I used to use TamperMonkey (even wrote a somewhat popular script a long time ago) and more plugins, but tired of the cognitive overhead maintaining the setup eg. every time I format/migrate, or when my browser decided to break backward compatibility, or when sites changed and the mod was no longer being updated, or when my browser got slow and I had to try and isolate which one(s) were at fault.
I'm sure the plugins are great, I just personally find it easier now to remove by hand (and other sledgehammers like disabling JavaScript altogether for the most aggregiously annoying sites).
I think the best one to install and forget is Tracking Token Stripper (https://chrome.google.com/webstore/detail/tracking-token-str...), but obviously it's not going to get all of them. Like, it's not continuously updated AFAIK. If you want to input the parameters it strips, then you have to use Query Stripper (https://chrome.google.com/webstore/detail/query-stripper/cce...).
I wish its dev would create a crowdsourced list, though.
If you need to pay the bills in person for the two different households, do you exit the building and re-enter before paying for the second one?
If you need to do both things in the toilet, do you do the one thing then leave and re-enter to do the other?
Last time I heard the technology should help people, not the other way.
Modern password sync stuff is either E2E encrypted or maintained by Google. Probably won't be hacked. If you don't own crypto you can probably fix it in the unlikely event it does.
Even if it does get hacked, they'd have to hack your phone or network to get past the 2FA on most important sites.
Making a payment online is insanely easy compared to analog methods. Hard to complain too much when you compare it to cash and checks. People used to literally balance checkbooks and some still call it a life skill. Online payments are like having a personal butler level of luxury.
Web1.0 aesthetics were pretty cool though, and the content was great.
They're never going to go Web 1.0 unless it's a special landing page for some marketing effort they're doing, and will be replaced with the bland corporate design as soon as the campaign is over.
Right until you lose your 2FA token, which in Google's case is your phone. And at this point YOU'RE DONE.
I have everything on my phone, I have 2FA on my phone, so if I lose it AND I can't restore my SIM/phone number - even knowing a prroper password for the account I can't do anything to restore the access.
And I really, really don't want to provide my government/country ID to some American company beforehand.
That falls apart neatly in this example where the internal page is deeplinked to and the back button brings me to this comment thread rather than the homepage.
We've had open Web APIs. We've had OpenID. We've had ambitions for semantic web and microformats. We've had API mash-ups. All of this has been closed, abandoned, or morphed into a locked-in monetized hell when VCs demanded their money back.
†) it's symbolic of course, but that's when shutdown of Google Reader deflated enthusiasm about syndication. About that time Google dropped their "don't be evil" motto, and wrote a spec for launching secret DRM APIs from HTML5.
Similar thing happened with XMPP and Google Talk. There was a brief moment in time when you could use any instant messenger with any client of your choice (talk to both Facebook Messenger and Google Talk users via your own server). That also been killed off in favor of proprietary apps.
I'm trying to think of a current-day equivalent of what a shock and disappointment that was, but I'm afraid proprietary protocols and non-interoperable app silos became such a norm that nobody even expects things to work together. I expect GMail to drop IMAP support any day now.
edit: I'll note that if google reader were still around today, its likely the discover algorithm would have been corrupted by bots and trolls and growth seeking managers at google. But back then this hadn't happened yet so it all worked pretty good.
Having said that, "web 3.0" as recently coined is the same type of middlemen-led openwashing. The real revolutionary technologies won't be hyped as some unified trend, because actual elimination of middlemen leaves no outsized investment money to pay for such hype. As always, the revolution will not be televised.
I do agree that Web 2.0 was naive in thinking that merely having open decentralized protocols was enough to ensure services built on top of them will be open and decentralized. The commercialized centralization happened despite the decentralized/open tech — on a layer above. Megacorps figured out that open protocols are merely a fertile ground for building walled gardens on.
And still around :)
It's punishing to have to reading through a post where the text spans the viewport width. It's like he took motherfuckingwebsite.com to heart, instead of the bettermotherfuckingwebsite.com which actually prioritized readability.
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title></title>
</head>
<body>
</body>
</html>so we can have UI "skins"/ themes for all pages exactly same, because it will be client side software responsibility to render it and user chooses theme as user wants / needs i.e disabilities, machine reading so i can actaully use my 4000 dollar gpu with 4gb vram to read text for me. and because of STANDARDIZATION those themes will be universaly working, not i can choose drakoola on reddit but i have to choose monokai on gogole news because those are most similar themes to each other, which i get dictated to use by corporation. corporation dictates how ti should look. i want t oit to look exactly same. it will be easier to consume, less traffic will be needed becasue les page loads, content can be dynamically added i.e. new reddit comment etc
do not use BOLD, use EMPHASIS, do tell me what content of picture is by inserting WORDS INTO DESCRIPTION so i can choose if i need to load it or it is just some placeholder /ad which i dont have to see
and most people forgets that HTML is NOT meant to be read by people but read by MACHINES.
HTML is as bad implementation of latex as RSS is bad implementation of USENET
same primitive s... as with current AI, it can tell you if there is dog in picture but it cannot tell you more about that picture, what exactly is meaning/essence of picture of that dog in there.
im not trolling , im not joking.
web 1 was awesome because i can literaly PUT FREAKING links to content directly, web 2.0. YOU CANT. this should be made mandatory, make dark web 10 % of web !
i was flabbergasted when i think google? announced that you can now create a hyperlink to a specific location in another Web page like WHAT ? you mean i can actually use thing i used in freaking firefox 2.0 or in netscape navigator ? you cant be serious ! XD
but this is state of thing. try to link some FAANG forum page from 2013. you cant because hierarchy of whole "forum" changed and you have to manualy search for answer
and not even start about twitter which dont let you browse without logging in. i dont mind logging in if logging is NOT paired with my number etc.
now imagine having this in your emacs / lynks (webbrowser) window wouldnt be that freaking crazy nice? you can choose which users comment will be highlighted ( friend, replying to you, contains some word...) CLIENT SIDE so there will be less bandwidth and resources wasted fro coprporation.
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
Content.
As to the passwords issue, I use both 1password and apple's keychain password manager. I've never had a problem with either. 1Password I believe lets you specify symbols, numbers, capital letters etc when generating a password. LastPass does too.
None of these issues are really Web 2.0 related, just poor implementations and designs. Plenty of counter examples to how great Web 2.0 is.