key

GPL FAQ: https://www.gnu.org/licenses/gpl-faq.html#NonFreeTools

In the old days proprietary compilers was the norm. If “blue” is of value an open source equivalent will be made eventually. But looking at the blue examples and sdesk repo I doubt it.

Going just by the examples, Blue itself seems more an incomplete templating/code generation layer for getting some syntax sugar than anything else. Like you write Blue targeting C, write super high level constructs in Blue, then include C headers and snippets of C code for all the stuff you can’t write in Blue, and finally transpile Blue into C which is then compiled conventionally.

I got one of those desks with a vertical pneumatic lift so I can stack the computers vertically in a rack and just raise/lower it so the right one is at eye height

Oh wow I didn’t realize nearly any of that detail about the current system. That explains why my fluid systems would always be unbalanced crap and sometimes require inexplicable pumps be added.

FTS? fuck that

I wonder if you applied inflation from the time that idiom was first popularized what the modern price would be.

MAAAN would be a much better acronym though

That’s when you update your sig with your address and a link to a local delivery venue

Alternatively all 504 Gateway Timeout

That joke was constant in the early 00s.

Oh wow that looks fucking awesome. Major Legends & Lattes vibes but with a dark undercurrent.

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 guess their advertising campaign wasn’t very effective!

It’s popcorn not salad dressing.

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.

Simple: make friends with someone with high speed internet who’s not very savvy, keep up the charade until they allow you to borrow their computer. Then you install a headless vpn server with logging disabled. Boom, high speed local VPN that doesn’t point to you. Just buy them a $2.50 beer once a month to keep up pretenses in case you need to do maintenance.

I just barely managed to cancel the update and apply hacks to prevent it completing. I

was one of the many people who got hit in the nostalgia from the show and decided to replay. Of course that meant grabbing a mod list which took a couple days to get downloaded and working. Then a couple days later they release an update that breaks all the mods. Would have been much better timing if they released the update ahead of the show so modders had time to fix things before the rush.