l'empathie mécanique @dpwiz@qoto.org

@omgubuntu F

NAnd
The way it's meant to be played

@abcdw I'm not actually sure... I just know Haskell's distributed-process cribbed a lot from Erlang and one of the features that got a lot of attention, up to improving the compiler, is the ability of sending closure over wire. But unlike Erlang that can just send its bytecode, Haskell had to send a function identifier (CAS for code part) and its closure data.

@abcdw erlang?..

Open the pod bay door, HAL

@AkaSci @sundogplanets Extrapolating beyond 2050 lol

@thefranke @aras @phire paper KPI maximizer detected

Counting days to my new Linux battlestation to arrive.

M1 is fine for a laptop I guess, but I miss having a GPU what isn't a joke.

And I miss the lived-in comfort of an Ubuntu (gnome actually, but whatever) desktop. MacOS feels incredibly inept and patronizing at the same time.

@marcel @smallcircles @libertyoftheforest With a few more levels of "we host your backups and you host ours", slicing, mixing, and anonymous scattering it is possible to achieve the level of resiliency above and beyond those of centralized silos.

However, this gets into political territory if we really into privacy as those would require extreme levels of anonymous mixing and you'd almost guaranteed to host some **nasty** stuff without a way to kick it out or even detect.

So, p2p is in the bind here: either you're vulnerable to metadata dragnets and association tracking or inadvertently trade resources with someone you wouldn't like (if you had the option to know).

@marcel @smallcircles @libertyoftheforest I'd like to mark data longevity explicitly, even if it can be folded into maintenance.

Yes, you can run quite a few services on a tiny devices now. But one glitch and it's all gone forever.

Centralization does not solve it by itself, but through pooling of resources. It is cheaper to have redundancy at scale - when the effort went into your backup solution and ops is amortized per user.

In a way we have to replicate this aspect but in a distributed fashion. Not only your tiny device should serve your community, but your neighbors too: "I host your backups and you host mine".

#GNUnet has a good story here for privacy and distribution, but they got bogged down on the protocol level.

@marcel @smallcircles @libertyoftheforest Here's this point in detail: https://secushare.org/centralization

@dbattistella This doesn't make sense... But the dude's got a book to sell, can't blame him.

@wilfredh The "Just Enough Typing" section is unclear... I'm struggling to guess what it is intended to convey and how the code is supposed to help.

@cab404

@reidrac Got frustrated with the experience or it just... didn't deliver?

@dpiponi good job at picturing an angel.. just needs a few more wings, some^W lots of eyes and setting it ablaze. Okay, maybe weave in a silver/golden ring in there too.

@me The feedback loop is important as it the thing that makes the multi-pass iterative improvement possible. An LLM-like model is a closed system and sure, I'll grant that it will bounce around the middle of its prob landscape.
But giving it at least a scratchpad *allows* it to leverage the more powerful and abstract higher-level patterns it learned. And *this* has no limits on novelty, like being turing-complete elevates the system from a level of a thermostat to all the complexity you can eat.

Of course "allows" does not guarantee it would be used effectively. But at least it liberates the system from the tyranny of the "mere interpolation".

@me Polluting the feeds is what we're here for
That, and the thinking ofc.