They might use standard imagemagick or such on the backend meaning they can ingest pretty much any image format ever invented, and have a limited set of extensions allowed on the frontend side so people don’t upload .txts.

This grant does not include claims that would be infringed only as a consequence of further modification of these implementations.

IANAL but what they’re saying here seems to be “if you download our code and modify it and, with that modification, touch some other patent of ours we can still have your ass”. That is, the license they’re giving out only cover the code that they release. Which shouldn’t be too controversial, I think.

The issue with codecs in general is that there’s plenty of trolls around and coming up with any audio or video codec is probably going to hit one of their patents, so the best that FLOSS codecs can do is “we don’t have any patents on this” or “we do have patents on this but license them freely, also, if someone else goes after you we’re going to detonate a patent minefield under their ass”. Patent portfolios have essentially reached the level of MAD.

Personally, IDGAF: Software patents aren’t a thing over here. You only have to worry about that stuff if you’re developing silicon.

Should all be in place. Even nvidia driver support. It’s one of the rare cases where I actually support nvidia on a technical level, that is, having explicit sync is good. I can also understand that they didn’t feel like implementing proper implicit sync (hence all the tearing etc) when it’s a technically inferior solution.

OTOH, they shouldn’t have bloody waited until now to get this through. Had they not ignored wayland for a literal decade this all could’ve been resolved before it became an issue for end-users.

Oh that’s easy (and probably disappointing): None. Not really a hobby of mine, more of an extension to doing the laundry and being a cheapskate who can’t fathom buying something new when you can fix it in the time it takes to listen to a podcast episode.

The other really valid reason is linen. Kinda unrelated to sewing itself and it’s not about stopping the stuff from crinkling (that’s right-out impossible), but to make sure that crinkles don’t always appear in the same place so the fabric has a chance of wearing down evenly.

Found this out the hard way because my linen duvet covers are oversized – nominal size is correct, but they’re made for down blankets, not flat ones. Blanket slides inside, generally towards the bottom, leaving a fabric flap on the top that really tends to crinkle as you sleep, wash, hang up, the crinkles don’t straighten out, exact same crinkles appear in the exact same spot and get chafed while sleeping, rinse and repeat for two years the first hole starts appearing, a month later there’s more than you can be bothered to patch.

Luckily it was a simple matter of running a stitch down the length of the thing to shorten it a bit, but given that an iron and ironing mat (not a full table, mat is completely sufficient) is significantly cheaper than linen covers or just the material for them, definitely worth the investment and time.

Oh and yes linen covers are definitely worth it because moisture regulation. It’s also nice and soft – not in the silky smooth sense, it has definitive grip to it. So are linen kitchen towels because they actually dry stuff instead of spreading water around. Half-linen is already a massive upgrade over cotton in that area and it’s much cheaper (the main reason why full linen is so expensive is because it’s a bugger to weave, not because the yarn is that much more expensive. Weaving linen wefts into cotton warps OTOH is pretty uncomplicated).

Programs can’t set position or size of windows, period, at most they can ask and then hope they don’t get ignored and it’s good that way. Window management is responsibility of the compositor, not of applications.

At least KDE has support for it that’s about on X11 level, a proper-proper solution is still in the pipeline. And yes you’re seeing right it’s been there for four years.

And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).

That’s precisely the point: All the devs got tired of it and started wayland instead.

X12 might happen at some point when wayland is mature, as in a “let’s create and bless a network-transparent protocol so we might have a chance of getting rid of XWayland in 50 years” kind of move.

Yep that’d be Wayland devs maintaining XWayland, which is part of the x.org codebase. There are no “X11 devs”, they’re the ones who started Wayland to get rid of that bowl of spaghetti!

I argue that X11 would have hyperactive development, if we did not have Wayland

Wayland was started by the X developers because they were sick and tired of hysterical raisins. Noone else volunteered to take over X, either, wayland devs are thus still stuck with maintaining XWayland themselves. I’m sure that at least a portion of the people shouting “but X just needs some work” at least had a look at the codebase, but then noped out of it – and subsequently stopped whining about the switch to Wayland.

What’s been a bit disappointing is DEs getting on the wayland train so late. A lot of the kinks could have been worked out way earlier if they had given their 2ct of feedback right from the start, instead of waiting 10 years to even start thinking about migrating.

Making screenshots does, too, which is why that functionality gets implemented at the compositor level. And so will screenreaders. In fact looking at my settings panel KDE does have support for Orca. Dunno how well it’s working but it’s not like the issue is being ignored.

That does not seem to be a stray and yes there’s definitely reasons to take potshots at Gnome. They still don’t support server-side decorations. Everyone is absolutely fine with them not wanting to use them in their own apps, have them draw window decorations themselves, and every other DE lets gnome apps do exactly that, but Gnome is steadfastly and pointlessly refusing to draw decorations for apps which don’t want to draw their own decorations. It’d be like a hundred straight-forward lines of code for them.

And that’s just the tip of the iceberg when it comes to breakage you have to expect when running Gnome.

Wayland kinda is an x.org project in the first place. AFAIK it’s officially organised under freedesktop but the core devs are x.org people.

x.org as in the organisation and/or domain might not be needed any more, but the codebase is still maintained by exactly those Wayland devs for the sake of XWayland. Support for X11 clients isn’t going to go away any time soon. XWayland is also capable of running in rootfull mode and use X window managers, if there’s enough interest to continue the X.org distribution I would expect them to completely rip out the driver stack at some point and switch it over to an off the shelf minimum wayland compositor + XWayland. There’s people who are willing to maintain XWayland for compatibility’s sake, but all that old driver cruft, no way.

Azov has gotten completely diluted by a gigantic influx of ordinary people, its hardcore Nazi times were over before they were even rolled into Ukraine’s overall command structure which came along with some more denazification. The Wolfsangel isn’t recognised as a far-right symbol in Ukraine by the general public so they kept it. It’s also not a clear-cut Nazi symbol even in Germany, you see it on plenty of coat of arms, it also has plenty of use in forestry which is its original source: You hang it with bait onto a branch to kill wolves in a rather gruesome manner. That’s outlawed nowadays but you still see it on border forestry border stones, to mark wood, etc. The heraldic use derives from that, it symbolises presence or importance of forestry in the area the coat of arm represents. Not much forest around the Azov sea, though.

Those are not the Nazis you’re looking for. If you want to see, well not exactly nazis but the hot-bed of ultranationalists in the Ukrainian army have a look at the right sector regiment. Dylan Burns did an interview.

Next up: Someone’s going to claim that the Ukrainian army uses the “Iron Cross”. First off, the Bundeswehr still uses it, secondly, no the Ukrainians don’t use it you’re looking at the Cossack Cross, derived independently from the Templar Cross, unlike the Iron Cross not via the Teutonic Order. They’ve been using that thing for centuries.

EDIT: Oh wait I just remembered I’m completely banned from lemmygrad they won’t see this. Well, whatever.

So then, you think Nazi Swastikas without context should be allowed without any repercussions.

That’s incoherent. “Nazi swastika” and “without context” doesn’t mesh because “Nazi” is a context for “swastika”.

That aside, I’m going to take German law as an example: No, non-nazi swastikas are very much not outlawed. You can see them on stray Hindu temples or shrines in the country, for example. “Without” context they’re generally assumed to be Nazi ones over here because historical context, also, only Nazis draw random swastikas over here. You also see ones broken in pieces getting thrown in the trash or in a crossed-out circle, those come from the Antifa side.

Both the Hindu and Antifa uses are legal, the Nazi ones aren’t. That’s because German law doesn’t outlaw the swastika as such, it outlaws “using symbols of unconstitutional or outlawed organisations in a manner suitable to further their aims”. A Nazi painting a Swastika on a Jewish gravestone is considered furthering the aims of the NSDAP, which had the swastika as their logo. A Hindu chiselling a swastika into their gravestone is a completely different matter. (Do Hindus use gravestones? Anyway doesn’t matter it’s a hypothetical example).

In another country, where the historical context is different, those “without” context swastikas won’t be interpreted the same as in Germany. So even under German law those would arguably be legal, there.

Assembly is a direct mapping to instructions. It just converts the text into machine code directly,

Kinda… yes and no? At least with x86 there’s still things like encoding selection going on, there’s not a 1:1 mapping between assembly syntax and opcodes.

Also assemblers, at least those meant for human consumption (mostly nasm nowadays) tend to have powerful macro systems. That’s not assembly as such, of course.

But I think your “a compiler changes the structure of the code” thing is spot-on, an assembler will not reorder instructions, it won’t do dead code elimination, but I think it’s not really out of scope of an assembler to be able to do those things – compilers weren’t doing them for the longest time, either.

I think a clearer division would be that compilers deal with two sets of semantics: That of the source language, and that of the CPU. The CPU semantics don’t say things like “result after overflow is undefined”, that’s C speaking, and compilers can use those differences to do all kind of shennanigans. With assemblers there’s no such translation between different language semantics, it’s always the CPU semantics.

Ok. We’re on the prairie. There’s literally nothing here to eat but bison, though somehow you’ve got it into your head that you can eat grass. Fine, we’ll let you try for a bit until you come to your senses. Two weeks later your digestion is fucked, you’re lethargic, and we have to carry you.

You, MindTraveller, have just become a burden to the whole group, lowering all of our chances of survival, all over some so-called “principle”. I know of gods, I know of spirits, if your principles are anything like that then certainly they must be evil. Maybe shaming won’t help to drive them out, we can try other rites, but if nothing helps then we will have to leave you behind.

“wait why did I support this and then stop the second they said ‘dog’?

It’s a bad idea in general to eat predators because the higher up the food chain you go the higher the chance you’ll contract an illness. Humans are not alone at all among predators to practically only go after grazers, and not other predators. We leave the rest to carrion eaters who specialise to deal with all kinds of nasty stuff.

People thinking that this is some kind of grand ethical-philosophical argument or conundrum just shows how alienated they are from the ways of nature.

They’re overpaying for them. Which then makes companies calculate “we could sell a lot of product at small profit margins to the general vegetarian and flexi public” vs. “we could not invest in production capacity and charge affluent urban vegans and arm and a leg” and guess what they’re going for.

The reason why there’s tons of almond etc. milks costing 3-4 times as much per litre as actual milk is not because of subsidies. It’s because vegans are stupid enough to buy 20 cents of ingredients for that price.

32 is ASCII space, the highest number you need is 114 for r (or 122 for z if you want to be generic), that’s a range of 82 or 90 values.

The target string has 13 characters, a long long has 8 bytes or 16 nibbles – 13 fits into 16 so nibbles (the (x >>= 4) & 15) it is. Also the initial x happens to have 13 nibbles in it so that makes sense. But a nibble only has 16 values, not 82, so you need some kind of compression and that’s the rest of the math, no idea how it was derived.

If I were to write that thing I’d throw PAQ at it it can probably spit out an arithmetic coding that works, and look even more arcane as you wouldn’t have the obvious nibble steps. Or, wait, throw NEAT at it: Train it to, given a specific initial seed, produce a second seed and a character, score by edit distance. The problem space is small enough for the approach to be feasible even though it’s actually a terrible use of the technique, but using evolution will produce something that’s utterly, utterly inscrutable.

Muss ja nichts falsch dran sein. Traditionell sind in Italien Eiernudeln frisch aber auch da gibt’s die getrocknet im Supermarkt.

Wer einen Netto (ohne Hund) in der Nähe hat der kann mal deren Tagliatelle ausprobieren, die die durch Bronzeformen gedrückt wurden. Ist so ein schönes Zwischending: Weder Teflonglatt noch sauteuer weil irgendein Fanatiker jedes Weizenkorn mit der Hand ausliest.