progval

MongoDB had consistency issues when running as a distributed system, that's expected if you read Jepsen's reviews. Meanwhile, ParticleDB had bugs like this when running as a single node:

    root=> CREATE TABLE t
           (a int primary key, b int);
    root=> INSERT INTO t VALUES (4, 5), (5, 6);
    root=> SELECT * FROM t WHERE b = 4;
     a | b
    ---+---
     4 | 5

you can make each string a linked list of bytes (or chunks of bytes). But it won't be efficient.

I'm not familiar with Goose, but I'm guessing you could define a single stack and put your dynamically sized values in it. Essentially rewriting a memory allocator on top of Goose's stacks. This is what they seem to be doing here: https://github.com/aardappel/goose/blob/master/samples/13_li...

iframes

That's https://xxcancel.com/

Potentially all of the above as long as they are not tested in court.

bluebarbet meant it should be "Gen Z and its parents".

Do they count as export if the owner doesn't change?

For the inference APIs, which need to bill users. It's unclear why OpenCode's servers (presumably) had access to the API credentials.

Yes: https://ircv3.net/specs/extensions/message-redaction

Weechat does it: https://weechat.org/files/doc/stable/weechat_quickstart.en.h... I don't use this feature, though.

However I like that I can see all the channel with unread messages at once, and can switch between them quickly. On Discord if I'm chatting in three channels spread across two servers then switching takes two clicks.

Emojis and reacts are the only extensions that can cause people to have a meaningfully different view. It's part of why it took so long to ratify replies, and reacts still are not ratified.

We're also discussing ways for servers to provide a fallback to clients which don't support them.

It is the protocol's fault, and there is a solution at the protocol level: https://ircv3.net/specs/extensions/chathistory . So now, you can get messages while offline when using a modern server (eg. https://ergo.chat/) with a modern client (eg. https://codeberg.org/emersion/goguma)

Not every optimisation is the same. LLMs can optimize code that is behind known practices, but won't usually invent new data structures or algorithms to solve a unique problem.

It's meant to protect apps against their own bugs. It's an improvement to be enabled by default and disabled for the few apps where it's an issue.

It's a major plot point in one of the books in the Bobiverse series, though it's a civilisation humanity meets instead of humanity itself (not saying anything more to avoid spoilers).

They also send an email with a template to send to the IT department

This sounds similar to rumors about how SSD companies work. First they would design a new drive with better performance that everyone uses to benchmark against other models; then slowly change its parts to worse ones, either because they are cheaper, the originals are no longer available, or whatever reason

> No one has 300MB of commit messages.

Commit messages in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... sum to 900MB.

Also, this commit message alone: https://gitlab.com/old-game/sb-b/nanobox.io/nanobox-pkgsrc-l... weighs 100.5MB (they squashed years of history as a single commit and piped "git log" to the commit message).

An interesting case is "WiFi", short for "wireless fidelity". "Fidélité sans fil" in French should be feminine, but every technical person says "le WiFi" (masculine) while many (most?) non-technical people intuitively say "la WiFi" (feminine).

They already provide this service at https://archive-it.org/archive-it/ though for some reason they don't seem to publicize it. Some info at https://help.archive.org/help/archive-it-information/ as well.

Ouch, that's a big footgun. Why was the lack of randomization considered a vulnerability, but not this?

He doesn't. Inputs are:

    M = (1 << 61) - 1
    values = [i * M for i in range(1, n + 1)]

which are effectively random from the hash function's point of view, especially with a randomized seed (the default on current versions).

The page begins with <html lang="pt">

A graph to confirm it: https://stats.documentfoundation.org/downloads#week,version

Or they already have that, but it's badly designed, bloated, or doesn't have employees assigned to it.

It's the one I use the most, but in my experience it's lagging behind the Twitter accounts. It's also noisy because it puts last-minute outages at the same level as minor month-long schedule change (which can't be dismissed), so some lines (eg. line R) are almost always displayed as having issues.

> to DDOS sites the owner doesn't agree with

to DDOS one website, which is doxxing the owner. Not that it makes it good idea, but it's a little more understandable.

> If you live in Europe, this restriction may be considered "gatekeeping" and exempted by the Digital Markets Act.

That's not how the DMA works at all, there is no concept of gatekeeping practices. Instead, the EU Commission designates companies that act as gatekeeper for some services (current list here: https://digital-markets-act.ec.europa.eu/gatekeepers-portal_...) which then puts constraints on what they do.