It’s out there. Social networking sites with a vested interest in monopolizing your attention don’t use it. So I don’t use them.
Free culture and open internet activists lost this battle
Convince the government to forbid the business model in which most of users are not paying customers but a product offered to advertisers. Then, social platforms will not care if you use whatever client you desire.
Big Social shareholders don’t want it, though. Being a double-sided market is addictive, and no one can compete with them if they capture the market by not charging money.
https://en.wikipedia.org/wiki/Yahoo!_Pipes
https://en.wikipedia.org/wiki/Mashup_(web_application_hybrid...
It's too bad the silofication of the 2010s killed it off.
I like broadcast TV and radio (especially radio while driving) and think that most Americans would object to their removal.
Just look at the uproar over a few NFL games being unavailable on broadcast TV for a hint as to how well such a ban might go.
If you suggest to apply the same model to social media (where they don’t get to know about a single thing about the user, strictly one way ads) then I’d be totally for it.
However, I don’t think they’ll find this model profitable enough (advertisers like to target), and because charging users is easier with social media compared to radio broadcasting the barrier to start doing that is lower.
That is, disallowing profiting from PII and only allowing one-way ads in social media, while difficult to enforce will also mean they start charging users anyway. So why not skip that model altogether.
Local broadcast models don’t work on global scale anyway.
The ideal install workflow would be to have a repo of AWS CloudFormation templates to automate the installation of the lambdas for different sites in your account. Anyone can open an AWS account, and using CloudFormation is a few fields, and a button click.
Also, if the scripts are developed properly, they are runnable locally. A sane developer will run them locally during development, and then test deployed before releasing.
But there is no aggregation - each user runs their own instances. For any site the offers an API, the API would need to have breaking changes to disable this, or block access from AWS.
It's easy to make work for a developer like crowd (very little time to write). It would work for most developers just fine, and could, with more considerable development time, be good for anyone.
Distributed guerilla social media deconstruction.
Unfortunately they've shut down at some point, it seems (thus my linking to archive.org instead of their actual domain).
I had been planning to add Twitter before the API changes...alas.
"Message: Missing configuration option: twitterv2apitoken"