Sven Slootweg @joepie91@pixie.town

Jesus fucking christ I hate tech discourse.

The fucking problem is that COMPANIES ARE UNDERPAYING DEVELOPERS AND NOT HIRING PEOPLE WITH THE RIGHT SKILLS. It's fucking CAPITALISM, like every other problem you people talk about on here. It's not the goddamn framework or the runtime or whatever the hell else.

It's companies hiring webdevs because they are cheaper, who have zero experience with building anything that stays resident in memory for longer than the lifespan of a tab, and "Electron is like a browser, right????" and so why *wouldn't* you task an underqualified developer with building a whole goddamn desktop application despite having had neither training nor opportunity to learn what the requirements of the job actually are, and THAT is why every Electron app you are running uses 3 fucking gigs of RAM, not because boo-hoo it uses the evil javascripts.

And if you spent literally ANY time learning to understand the problem with the resource usage of Electron apps, and actually ran a profiler for more than two seconds, and actually, y'know, *talked* to the people who work with this stuff, you would KNOW ALL OF THIS ALREADY. But no, again, it was easier to just shit on Electron because that's the cool thing that everyone is doing, right?

Also: if you are picking out Electron *specifically* to complain about, and absolutely nothing else, then I *know* that you haven't actually done your fucking homework on what's going on and where the problem lies and you're just complaining at the first thing that someone mentioned that looks related. Cut that shit out.

Getting very sick of the constant substance-less shitting on Electron and JS by people on here, I think I'm just going to start muting anyone who toots this stuff.

If you people would ever goddamn engage on the conversation of *why* people use Electron instead of just throwing a pile of developers under the bus who have been fucking begging for better tools for decades, then the whole problem you're complaining about wouldn't exist.

But noooo, it's much easier to just whine about the tech, of course, and never actually introspect about how we got here or what role you and others might have played in that. Fuck off with that shit, seriously.

For clarity, most of these comments I'm talking about weren't actually directly *on* fedi, but rather linked from here.

Not a subtoot of anyone directly here, but since it's coming up again, and some of the claims I've seen are getting rather bizarre: yes, the guy is probably a bigot, yes, I wouldn't trust him either, but do please remember that not everyone lives in the US and different places have different cultures.

This doesn't *excuse* bigotry, obviously, but it is vitally important to understand the cultural background of someone to fully understand the context or perspective from which a comment is made, and some of the comments I've seen on the topic seem to be assuming that everyone is somehow magically aware of (and shares) the cultural context and norms of the US.

(And it's worth asking yourself whether making that kind of assumption is not just another aspect of cultural imperialism...)

As a sidenote, this is why I don't engage on discussions about "but people need a way to make a living!" if the speaker isn't willing to acknowledge that that can also very quickly become a problem if you're not super careful about how you implement it.

Like, we've tried just implementing "letting people make a living" directly. That's how we got Bitcoin.

https://blacktwitter.io/@thiswomanswerk/113368795659069245

2009 decentralization discourse: how do we create financial incentives, so that the network survives?

2024 decentralization discourse: how do we *keep out* the financial incentives, so that the network survives?

And once again, the only actually useful article I could find on a math/crypto concept was one that openly rants about every other article being impenetrable garbage with unnecessarily obtuse mathematical notation.

Every fucking time.

I have a difficult protocol design problem that I need some suggestions for to explore. Please read the requirements carefully because they are very specific, and leave the "it's impossible" comments at the door, because I *know* that this is a seemingly impossible problem already.

(The problem description is also intentionally generalized and reduced down to its core mathematical problem, to avoid unintentional assumptions.)

I have a distributed protocol. The different parties involved mutually distrust each other. They can each contribute mutations to a shared state log, based on some unspecified authorization algorithm which allows for revoking access of other parties. The parties eventually converge onto an identical view of the state, though temporary partitions may occur.

The problem is that a genuine partition followed by a delayed delivery of mutations, seems indistinguishable from a malicious attempt at subverting an access revocation through backdating of mutations.

In both cases, one or more mutations are received which are dated to a timestamp that was potentially a long time ago, and that may be working off an old version of the state.

There is (currently) no shared clock, and there is a small but non-zero span of time between the most recent accepted mutation from a revoked party, and the actual revocation of their access.

How do I prevent backdating, without losing resilience to partitions?

I'm not necessarily looking for full-blown solutions (though those would be welcome!), but even just pointers on relevant research would be welcome, as long as it is research that accounts for all the properties here: untrusted parties, no shared clock, exploitable timespan before revocation.