pgeorgi

> that was just mostly regular farmers before the first Nakba but slowly became radicalised

Regular farmers who were asked by their Arab "brothers" to step aside while they eradicate the Jews. Surprised Pikachu face when that plan didn't work out and the result was that the farmers couldn't go back.

The same "brothers" now tell them to not leave the Gaza strip (and enforce it by blocking the one non-Israel-controlled exit), and to rather die as meat shield for Hamas. Priorities, priorities...

Right. I'm not defending their naming choice, just pointing out that "open = you need to be rich" is an ancient trope in computing:

Open Group was formed through the merger of Open Software Foundation (est. 1988) and X/Open (est. 1984), and they were all pay-to-play.

As in The Open Group: discrimination-free, as long as you're able to pay.

See also https://review.coreboot.org/c/coreboot/+/78271 :-)

coreboot has a rather fragile JPEG parser for splash screens but the saving grace is that barely anybody uses it because that's normally the payload's job (the jpeg + display thing was mostly added for a proof of concept "look how fast we can boot" demo in 2005)

With payloads, some are more at risk than others. edk2 might run into issues here, grub2 has tons of features where stuff like this might hide in, other payloads (e.g. ChromeOS' depthcharge) are more limited in their functionality and therefore in their attack surface, too.

But it's a cost they don't bear, it typically ends up in a different section of the balance sheet. And as soon as somebody else pays for it, personal benefit (perceived or real) takes the front seat. See business class pricing in travel, for example.

That's not what the RTO proponents bring forward. A sincere "I prefer you to be here so that I can admire my kingdom and feel good" would be more productive than the currently preferred grasping for straws on why it's better for the bottom line:

Everybody gets a good laugh, and returns to their tasks, or coffee chats, or whatever it is that they were doing, where ever they were doing it.

> Although I was hoping for a real SQL type experience. I don't understand why no one just copies SQL so I can write a query like "SELECT * FROM $json WHERE x>1".

With somewhat tabular data, you can use sqlite to read the data into tables and then work from there.

Example 10 from https://opensource.adobe.com/Spry/samples/data_region/JSONDa... (slightly fixed by removing the ellipsis) results in this interaction:

    sqlite> select json_extract(value, '$.id'), json_extract(value, '$.type') from json_each(readfile('test.json'), '$.items.item[0].batters.batter');
    1001|Regular
    1002|Chocolate
    1003|Blueberry
    1004|Devil's Food

    sqlite> select json_extract(value, '$.id'), json_extract(value, '$.type') from json_each(readfile('test.json'), '$.items.item[0].topping');
    5001|None
    5002|Glazed
    5005|Sugar
    5007|Powdered Sugar
    5006|Chocolate with Sprinkles
    5003|Chocolate
    5004|Maple

Instead of "select" this could also flow into freshly created tables using "insert into" for more complex scenarios.

bzr is a reimagining of baz, also known as GNU bazaar which derives from GNU Arch, which derives from Tom Lord Arch, which started in 2001.

If you squint a little, https://web.archive.org/web/20030629114010/http://www.venge.... is a fair approximation of some of the core ideas behind git (and Linus played with it and wrote a critique of its short-comings before starting git)

> Is it just some kind of accounting benefit to maintain the weird structure / partnership, versus doing everything themselves?

For starters it allows them to pretend that it's "underdog v. Google" and not "two tech giants at at each others' throats"

> it's logically inane to say that someone's criticism of something is invalid because they didn't speak out or criticize some other thing that they most likely don't even know about.

I'm not saying the criticism of Hamas and/or Israel is invalid, I just found it worth pointing out that there are conflicts that teens somehow can make up their mind on (that's TikTok's claim, not mine) and strong enough that they take to the streets for that, while they likely haven't heard of other somewhat comparable conflicts (support by "their government", civilians dying, half the world away, ...) at all.

Maybe it's just the general media circus (Yemen _isn't_ very present in the media, after all), but "algorithm" or not, I'm considering TikTok part of that media circus.

As such, "the kids are just voicing their opinion" seems a rather shallow excuse to me: They pick up what gets amplified. Having no idea about Yemen but strong opinions on "who's the baddie" in Gaza (since folks like to talk colonialism: it's clearly the UK) doesn't sound like an independently formed opinion at all, and so I'm not willing to let TikTok (et al) off the hook.

To take another brutal war affecting civilians: https://en.wikipedia.org/wiki/United_States_support_for_Saud... sure sounds like it had the endorsement of two US Presidents both from ends of the political spectrum, and it was a money sink for over $50bn in US tax dollars in 6 years (see https://www.gao.gov/products/gao-22-105988).

I'm not sure if those teens even know how to spell Yemen.

It is the dose that makes the poison...

I'd want a separate house, too, if my neighbors are Americans.

> so the nuclear industry has to bear the true insurance cost

How expensive is a resounding "No" by insurers?

To a layman, they're all useless, and in a dangerous way: they transport a sense of understanding a person/character/psyche that they don't support.

A professional can gain _some_ information from all of them. Just that the Big 5 have much more literature behind them than MBTI, so there's more reference data for any given constellation. That's a reinforcement loop. Methodical differences and reliability and all that fluff can be used to argue in more detail in favor of one versus the other, but by now, it comes down to what folks are more familiar with.

In the end, these are just a few out of many, many tools of the field. If you see somebody build their career on "(MBTI|Big 5|...) analysis" and nothing else, they're not a professional but a quack.

> Or in other words, people should be glad that the demand for cashiers still exists, until the job gets fully automated.

... because what happens otherwise?

§23 PatG covers the case where the patent owner wants to use a general public licensing scheme offered by the patent office to avoid having to deal with every single licensee. That one is opt-in by the patent owner.

§24 PatG offers a compulsory licensing scheme, but it requires not only that the would-be licensee made an effort to find an agreement with the licensor, but also that such a compulsory license is in the public interest.

Since the public interest doesn't seem well-defined in PatG, you'd have to check older cases to see how that turns out, but I'm not sure if even "doing so reduces bandwidth use on the internet" is enough: you still have the option of using another codec and compensate the worse compression by going for lower resolution video, for example. 4K video is not a human right ;-)

(and "we hog internet resources" is the last thing Netflix et al want to say out loud anyway: ISPs are eager enough as-is to try to get them to pay up for access to their customers.)

The patent business is one with no downsides for the patent office: They get a fee for granting a patent, they get a fee for renewing a patent every couple years, they get to fell important when they report to their government how "innovative" the country is through the number of patents granted. If a patent is found to be invalid, it's struck from the records, no penalty to the patent office. If a patent is found to overlap entirely with an earlier patent issued at the same office, it's struck from the records, no penalty to the patent office.

So of course they're looking for any loophole they can find to pass more patents. And even if the loopholes turn out to be of the wrong shape, it's not their problem.

> There's an H.265 patent pool that is supposed to cover all the patents essential to H. 265.

Pool operators like to pretend that this is how it works (unless you ask pointed questions), but it already failed with the first popular codec patent pool, Thomson's MP3 pool - where devices were collected on trade fairs by customs because there were some additional patents from Sisvel that spontaneously appeared.

Also note: pool operators don't guarantee that they provide customers with a full set of licenses. From the horse's mouth (https://www.via-la.com/licensing-2/hevc/hevc-faq/): "no assurance is or can be made that the License includes every essential patent"

> why is it not part of the pool from MPEG-LA?

Maybe Broadcom didn't feel like joining the extortionist pool but preferred to extort the format into uselessness all on its own?

There are precious few ways to mandate licensing of a patent of a third party, and MPEG-LA (now Via LA) license pools aren't one of those ways.

Supply and demand is fair, if and only if both sides are entirely free to walk away from the deal. Depending on the labor market situation this isn't necessarily a given when the alternative is starvation.

The problem is that Intel tries to "solve" security by adding new layers on top of the gargantuan mess of layers that already exists instead of reevaluating decisions made 30 years ago and dealing with compatibility issues through emulation.

I guess that's something humanity can consider once the question of energy sources is settled. For now, whatever energy that could be used to gather energy to split CO2 into C and O2 could as well be used to replace fossil-burning generators, at likely better efficiency.

If it turns out that passing a data set through PyTorch creates enough distance between the source material and the resulting data set to invalidate copyright protections, it will be interesting to see what happens when somebody does that to AI companies' assets.

With the "edge computing in AI" push (offline processing on phones and the like), we might see soon enough.

It can be done to drosophila, as alluded to in https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3197105/

The easiest route towards that might be contract work or employment.

The difference is that so far, everybody was allowed to do that. With that change, only they can do that (with new code going forward). And ask developers to jump through hoops for the privilege.

That _might_ be the best option for Synapse etc, but it should be clear what they're offering.