key

Data size and user expectations is the main difference. It’s possible but there’d be a lot of latency and overhead for just scrolling down a page with a bunch of images. Maybe there’s fancy stuff you could do by batching images together and reusing connection pools but it feels sisyphean.

Mastodon and lemmy handle this in slightly different ways. Mastodon (according to the link) replicates media on every instance while lemmy (mostly) only replicates thumbnails. That means a popular post doesn’t cause load for one server on mastodon but does on lemmy. But Mastodon has a higher aggregate cost due to all the replicated data, which is what the linked proposal solves by making it sublinear.

If the torrent is instance to instance I don’t see any real benefit (and instance to client is infeasible). On Mastodon side you still have data duplication driving storage costs and bandwidth usage regardless of whether it’s delivered via direct http or torrent. On the lemmy side it wouldn’t gain much (asymmetric load is based on subscription count and so not very bursty) but would add a lot of non-determinism and complexity to the already fragile federation process.

Conventional solutions like cache/CDN/Object Storage or switching to a shared hosting solution (decoupled from instances like your link proposes) seems like a more feasible way to address things.

No

You could hire a team of security experts to audit it for you

I love the concept. I hate many of the language design choices.

I’ve been using it the last month. It’s autocomplete and does what autocomplete should. It doesn’t guess utterly insane shit like certain other tools.

8 hasn’t been getting the essential security updates since march 2022.

That’s not really true despite what Oracle claims. Even without dropping money for Oracle’s 2030 support, there’s been 9 releases to OpenJDK 8 so far in 2024. Amazon has guaranteed OpenJDK 8 LTS through 2026 as “corretto” for justifying it to corporate compliance teams.

Everyone really should upgrade but it’s going to be several years yet before it’s an actual security risk.

Remove the quotation marks and the first result is https://kottke.org/19/05/grace-hopper-explains-a-nanosecond

More accurate is “electricity has a speed limit”

There were several years when it would be the top result whenever you searched for a tech problem. Back then usenet was already largely dead, was more about mailing lists and IRC if you couldn’t find a blog or forum post that covered the issue.

Enjoy installing fake dependencies squatted by malware

The industry has too long neglected the true threat posed to information security by the platypi.

The manual talks about some of the older alternatives that influenced it. Doesn’t directly compare them though https://difftastic.wilfred.me.uk/tree_diffing.html

They mention that in the first paragraph and repeatedly through the announcement. How does that mean they’re not really sunsetting the original product?

A lot of the classic “pastebin”-type solutions get overrun by phishers and other scammers if they don’t require registration.

So OP is one of the only 25 people who used it?

Harder than implementing RSS. Less hard than writing Linux from scratch. Where it lays in the middle depends a shitload on your requirements. How much you want to federate (a blog post VS conversations for instance), do you try for exact compatibility with existing services VS using a different activity type, is it one way or bidirectional, how does it need to scale, etc. I don’t know of a generic library you can use so you’d need to read and understand the spec.

I usually find web gui good enough to get context of code. Doing all that and then needing to go back and forth from IDE to PR to leave comments sounds like it’d take a bunch more time.

Why squash all the commits if you’re just going to reset? Unless I’m crazy you can reset across multiple commits.

This is a strong example for the distinction between abundant comments and good documentation. Comments should describe why and how, not what. Comments on every single line stating what the line is doing is rarely a good sign. Despite all the comments, it’s not super clear what it actually does from a user perspective and why someone would want to use it. I assume it’s meant to be a templating system for text documents.

Give them a Nomad, even with full batteries it only lasts like 5 minutes.

The “why” is missing an important one: put less load on your primary DB for frequent gets. If you can replace your cache with your primary DB then ya you probably don’t need a cache. Just fix indexing, data normalization, and/or access patterns.