Embed Notice
HTML Code
Corresponding Notice
- Embed this notice@ayo >the lack of browser-integrated account and session management is a major contributor to the centralization of the web.
I'm not sure what you're on about - the main reason why the proprietary web is so centralized is due to how google pushes a browser-integrated user account in google chrome.
I don't see a way how you could add proprietary global accounts to a browser and not centralize the crap out of everything (after all, each proprietary account results in centralization if it can be used with more than one website).
>Github as an example, here's how most people would comment on a project's issue tracker:
>Open issues page -> write comment.
No, that is not how it works.
It's; >Open issues page -> go to sign-up form -> run the proprietary malware JavaScript -> open password manager -> generate & save password -> back to sign-up form -> Agree to surrender your soul -> open email program -> (wait for email to arrive) -> click link in email -> go back to issues page -> write comment.
If I remember correctly, there's the option to "sign up" with a google account as well and a few more botnet providers and you just need to enter a username, but that's in total more steps than the email method.
People seem to be preconditioned to be glad to sell their soul to one botnet "platform" despite the busywork required to sign up and unreasonable, as it only really needs to be done once (and "everyone uses it"), but then complain when it comes to "signing up" for an account on another forge under reasonable terms.
For any decent project, the ability to post an issue is an simple as;
>With literally any email software (or handcraft an SMTP message with netcat and make up a from: email), send an email to the mailing list detailing the issue - no "sign-up" with any account required (many GNU Mailman based mailing lists request that you subscribe to the list to send emails to it, but that's entirely optional, as the email will just go to the list moderator for approval if you don't subscribe)
Or even better;
>Fix the issue >Send in that patch with git send-email