mqus

well, no? Systemd actually also delivered all of the implementations of those protocols and barely no one cared to fit their previous solution to their standards? Rather, it was the opposite, systemd could also run your usual service shell scripts for a while.

Sure, there are similarities in the sense that you started out with 0 service files at the beginning and no GUI toolkit implemented the Wayland protocol from the start, but the thing itself is pretty different. Systemd wasn't designed by committee (and many people still have gripes about this). Wayland kinda is.

The point is: The libraries are not from the same people that build the standards, meaning: there is no "primary implementation" that everyone agreed on. ("agreed on" already is one of the problems, X11 was mostly just developed and everyone got "the thing" and had to use it, for better or worse. In Wayland, KDE, Gnome, wlroots, etcpp first have to agree on a common protocol to implement... and we see how that is going)

At least in the past, this was an nvidia issue (not respecting the kernel). But I do understand the user issue here: X works, Wayland does not.

If it helps: the EU ones are still just proposals (likely to ve struck down by courts), the north korean surveillance is already active(?)

The author builds a ticket system and says it's not trivially solveable. What's your trivial solution then?

regarding OpenDNS (from the article):

> When OpenDNS was first ordered to block pirate sites in France, the company made a simple but drastic decision to leave the country entirely, effectively affecting all French users. Last week, it repeated this response in Belgium following a similar court order.

even just text > base64 would also be great

Isn't SEPA instant kinda mandatory by the end of this year? (it mustn't cost more than regular transfers)

Same happened in germany but sadly, dwd (the national weather service) lost. They _have_ to take money if you want their weather app.

You mean ABI issues like not being able to run a java 11 jar on a java 8 runtime?

"an avatar" would also cover vtubers so png-tuber is actually more accurate here

include:component is usually what you want now, you can version your components (Semver), add a nice readme and it is somewhat integrated in the gitlab UI. Not sure about the other include: ones, but you can also define inputs for component and use them at arbitrary places like template variables.

Since the integration is done statically, it means gitlab can provide you a view of the pipeline script _after_ all components were included, but without actually running it.

We are using this and it is so nice to set up. I have a lot of gripes with other gitlab features (e.g. environments, esp. protected ones and their package registry) but this is one they nailed so far.

Great, they are now websites. What happens if they decide to no longer host them in two years?

oh I know. And considering the CLOUD act that's how it should be. Maybe I shouldn't have written "easy to follow" since stuff like backups can get tricky and DSARs can be a pain on the receiving side, but it is certainly easy to understand. I do hope that GDPR does add a wedge for getting less dependent on US companies that obviously do not care about privacy at all.

But please also share the more nuanced take on the GDPR of your lawyer. You can't go around making claims like that without substantiating them ;).

I think you're posting a strawman here. ePD is known to be bad (though for different reasons depending on who you ask), GDPR on the other hand _is_ easy to understand and follow.

it would be, if chrome would pay for this ad (and other browsers can compete for the spot). But it doesn't (can't?) and that is exactly what is wrong here.

This is a feature in zsh (I don't think it works in bash and the autocomplete in bash is also a bit inferior to the zsh one)

> when money lies in stocks and bonds, it is invested in the real world.

Is it though? How much did Nvidia invest more, after their stock hikes? How about Tesla, Microsoft, Apple? No. They cut their staff or maybe stayed at their current investment levels.

yeah, kinda, but VODs (the automatic recordings) are not covered by this change. This is about edits & uploads, so stuff you would usually put on youtube. If you're a full time streamer and stream every day, Twitch will still provide your past streams for 2 (or 3? not sure) months (or less if you're not popular) and this will not change anything for you.

My main gripe with handling music on jellyfin is that it expects your music to be stored in a certain folder structure[1] meaning it uses a kinda weird mix of metadata and folder structure to scan. This seems to be foundational so this probably won't get fixed in the near future (not because they like it this way, but because it's a lot of effort).

Not sure if you need some effort to "convert" your library to this structure.

[1] https://jellyfin.org/docs/general/server/media/music/#discs

Is the article really right though? I imagine that much more stuff runs some linux on any machine than there are running intel processors. Even if it was true in the past, it likely has shifted in linux favor even more

As others have mentioned, this kinda misses a "category" filter that is not just a search. I would suggest using the osm database for this (e.g. via overpass). If the data is good (depends on the location), this is better than just a keyword search.

I also have another issue: If I put the same thing in two different criteria (with different settings), it says the heatmap parameters are invalid.

My use case is this: I want to have a big station reachable within 30 minutes by public transit and any light rail station within 10 walking minutes. But this big station could fall into both of them, which, to me should then be handled according to the set criteria (maybe just treat it as two different entities entirely, just with the same coordinates?)

> Signal's default setup is more usability focused while supporting E2E

If images/attachments were e2ee, this problem probably wouldn't exist, right? or are the images on cloudflare encrypted?

Edit: I should clarify. I didn't mean the encryption itself fixes the problem, but rather that: If this were handled like the text messages we send (not via cloudflare CDNs) then this wouldn't exist. I get that attachments are quite some bytes bigger than text but shouldn't the security guarantees be the same?

> If other pages point to your page with descriptive text, Google could still index the URL without visiting the page. If you want to block your page from search results, use another method such as password protection or noindex.

> If your web page is blocked with a robots.txt file, its URL can still appear in search results, but the search result will not have a description.

https://developers.google.com/search/docs/crawling-indexing/...

So, a robots.txt will not keep your site off of google, it just prevents it from getting crawled. (But, to be fair, this tool probably does not do this as well)

Or... he didn't even login and the widget already was logging the IP when he opened the page? Either way I agree though.

As a german, we do "collection" well. Recycling(of plastics)... not that much.

I don't think I agree. I've now seen the 'language' approach in jenkins and the static yaml file approach in gitlab and drone. A lot of value is to be gained if the whole script can be analysed statically, before execution. E.g. UI Elements can be there and the whole pipeline is visible, before even starting it.

It also serves as a natural sandbox for the "setup" part so we can always know that in a finite (and short) timeline, the script is interpreted and no weird stuff can ever happen.

Of course, there are ways to combine it (e.g. gitlab can generate and then trigger downstream pipelines from within the running CI, but the default is the script. It also has the side effect that pipeline setup can't ever do stuff that cannot be debugged (because it's running _before_ the pipeline) But I concede that this is not that clear-cut. Both have advantages.

mini-nitpick for everyone that might be confused: it's "schwarz" (without t), Schwartz is a name of a lot of people.

> Another reason patents are nice is that it's that you get something for your actual contribution. This means that it offers particularly skilled people who aren't rich a chance to actually build a company and have something real.

... assuming you have the money to defend your patents (or even just find violations). Also, Bigco will just patent adjacent things like production processes and then force your company to trade. How many "small guy" patents were there in the recent years? It just does not fit to our world anymore.

Having a simple syntax might be fine for computers but syntax is mainly designed to be read and written by humans. Having a simple one like lisp then just makes syntactic discussions a semantic problem, just shifting the layers.

And I think an complex syntax is far easier to read and write than a simple syntax with complex semantics. You also get a faster feedback loop in case the syntax of your code is wrong vs the semantics (which might be undiscovered until runtime).