January 2024
41 tweets
Apathy is certainly a problem but I don't think it's because people aren't getting paid (even though paying people is of course good). In my experience the two primary drivers of apathy are how hard it is to get started and the fact that developers have no real power.
♥ 3
Barriers to entry come in multiple shapes. Some things are legitimately hard, no one uses email, the process can be counterintuitive, it's intimidating, sometimes toxic, and there's no broad education or outreach about how to do it. Some of this is fixable.
♥ 3
The second is harder: people don't see the point because they're not empowered. I know that browser devs try to be open to input (not everyone tries very hard, but still) but at the end of the day devs just aren't in command and the implementation decisions are opaque.
♥ 3
People don't want to beg for features, they don't want to be (selectively) listened to, they don't want a call centre: they want to be empowered to get shit done.
There are ways to fix that too, but I doubt the level of democratic commitment will be appealing to major browsers.
♥ 3
To give an example, I spent much of 2020 making calls to dozens of publisher or dev teams that I know have real web issues but never show up. I got the same answer *everywhere* (not some, all): Why would I work to participate when $BigCompany will just do what they want anyway?
♥ 5↺ 1
Oh, I forgot this yesterday. There's not really such a thing as a tragedy of the commons: aeon.co/essays/the-tra…
People will show up to organise and tend to their infrastructure, but they need to be empowered and to believe that their contributions are meaningful.
♥ 2↺ 1
Well yeah, it's all in how that institution is structured: the Onceler can appropriate everything but the Lorax can only "speak for the trees." Someone can speak for the devs, but unless they can act nothing is going to get better, it's not!
♥ 1
It's almost like productive and extractive are not the same thing and might not serve society the same way.
♥ 1
It looks like only verified users can DM you. Is the best way to reach you to go find your email on the site?
♥ 1
Thank you! I'll confer with my coconspirator and reach out.
Yeah — this platform is a mess. I have Bluesky invites if you or anyone at Noema is interested. (I promise it's not a bribe :)
♥ 1
I was at RMIT all of last week! Such a shame, I wish I'd been there a month earlier.
♥ 1
I feel attacked.
♥ 2
Context matters 😁 This wasn't originally written as a manifesto at all - I framed that tweet (months after I posted the article) that way because everyone was talking about the a16z manifesto nonsense.
In general, I have deep manifesto fatigue and wouldn't write one.
♥ 2
Yeah, I mean, I would *definitely* write manifestos in 1998!
♥ 2
Unrelated, but folks were *just* talking about the Borg Complex over on Bluesky. Any chance I could entice you over there with an invite? (Resistance is futile 😉)
♥ 3
And @libshipwreck too! Can't seem to find you there either.
♥ 2
*susurating siren voice*
Maybe jussst make an account, ssssssee how you like it...
♥ 1
Will DM!
♥ 1
It's more complicated/subtle than that. If you're talking about irrigation in a village then yeah, you need to exclude or punish freeriders.
For large-scale infrastructure commons, especially digital ones that have near zero marginal cost, that's a lot less important.
If you think about an open access road for instance, it doesn't matter that a lot of people who use it don't pay (maybe they don't meet a threshold for income tax, maybe they're tourists). The spillover benefits, including from nonpaying users, are worth it anyway.
♥ 1
For web infrastructure, we don't suffer from some developers not showing up to write standards. They're freeriding but we all benefit from the spillover benefits of them using the same infra. (It would also be tricky to run a WG with everyone.)
♥ 1
The shortcomings we have aren't from the lack of punishment as much as the lack of voice and ownership. At the end of the day, there is limited value in tending someone else's walled garden.
(Whether you agree with the characterisation doesn't matter if people believe it anyway)
♥ 1
Ah, sorry, I didn't catch the context change! The commons bit of the thread was about devs not participating being a tragedy of the commons and I was still on that.
Sorry, I'm going to braindump at you; first open source, then web infrastructure 😬😉
Open source in general is a bit complicated because most projects would not be viable if they couldn't use their dependencies for free, but they're also not sustainable because they themselves are not getting paid. And then $BIG_CLOUD_COMPANY makes a ton of money from your thing.
There are several ongoing projects to solve that:
• Some folks are working on licenses that give rights to contributors (in money or work) and not others. It's interesting (creates a more robust commons) but I don't understand how you scale that to many dependencies.
Correct. Got you covered! berjon.com/gpc-child-priv…
♥ 2↺ 2
Not having key societal functions operated by undemocratic corporations is indeed a key goal of antitrust policy. Without this it risks being nothing but sterile debates between shades of antiquated neoliberalism.
Quoting a tweet by @BruxConf2024 ↗
♥ 3↺ 1