BB_C

joined 2 years ago
[–] BB_C@programming.dev 1 points 3 months ago (4 children)

Because there isn’t a solution.

This has been discussed and experimented with to death where such networks existed for a long time. Just because you never heard of them or even knew they exist doesn't mean that they don't.

See Freenet/Hyphanet and the three approaches (local trust, shared user trust lists, web of trust) if you want to learn something. The second one worked out the best from a performance and scalability point of view compared to the third.

[–] BB_C@programming.dev 6 points 3 months ago

Not only is IPFS not built on solid foundations, offered nothing new to the table, and is generally bad at data retention, but the "opt-in seeding" model was always a step backwards and not a good match for apps like plebbit.

The anonymous distributes filesystem model (a la Freenet/Hyphanet) where each file segment is anonymously and randomly "inserted" into the distributed filesystem is the way to go. This fixes the "seeder power" problem, as undesirable but popular content can stay highly available automatically, and unpopular but desirable content can be re-inserted/healed periodically by healers (seeders). Only both unpopular and undesirable content may fizzle out of the network, but that can only happen in the context of messaging apps/platforms if 0 people tried pull and 0 people tried to reinsert the content in question over a long period of time.

[–] BB_C@programming.dev 4 points 3 months ago

Generally yes, unless it's the original source of a story.
e-celeb content and news aggregators are never the original source of a story.

[–] BB_C@programming.dev 1 points 3 months ago (2 children)

That some can and already do that on the video sites they already browse.

People like shorts too, but that doesn't mean Lemmy should be infested with such content.

[–] BB_C@programming.dev 3 points 3 months ago (4 children)

We went from spam "news sites" to spam videos. Maybe an "original source" policy should be applied by moderators!

This applies to both hare and on !rust@programming.dev

[–] BB_C@programming.dev 13 points 4 months ago (1 children)

^Who^ ^memory-holed^ ^2021^ ^an^ ^why❔😉^

[–] BB_C@programming.dev 6 points 4 months ago

They talk too much. But almost none of them actually code or know how to at a good level.

We have someone just like that here.

[–] BB_C@programming.dev -1 points 4 months ago

Now that others got all the technicalities out of the way, maybe ChromeOS/ChromiumOS would be something along the lines of what you're looking for? not that anyone should choose to daily-drive it.

[–] BB_C@programming.dev 7 points 4 months ago (1 children)

most Rust developers

survey participants != all rust developers

In fact, there is no reason for experienced Rust developers to participate in such surveys at all. I don't.

Hell, the way the survey results are covered (not just here) tells me that maybe we should push for it to never be done (officially) ever again.

[–] BB_C@programming.dev 1 points 4 months ago (1 children)

That's exactly the communicated meaning I was concerned an oblivious reader might get. You can use an updated Rust compiler 10 years in the future while your crate is still on 2015/2018/2021 edition. Editions are NOT software versions.

[–] BB_C@programming.dev 1 points 4 months ago (1 children)

I might expect the Rust ecosystem to adopt these new features.

This again points to you maybe not understanding how editions work, or maybe I'm just reading it wrong again. But you "upgrading" has no effect on your dependencies, and vise versa (except indirectly if MSRV is a factor as another user mentioned).

view more: ‹ prev next ›