hkwerf

Back when I was a physics student, I helped engineer exactly this experiment as a off-the-shelf solution for schools as a classroom experiment! We used PMTs mounted on top of coffee cans:

http://kamiokanne.uni-goettingen.de/gb/kamiokanne.htm

The FTL muons produce Cherenkov radiation in the water in the coffee cans, which is picked up by the PMTs.

Using this setup gives a much higher rate, as the surface is much larger compared to geiger tubes. Thus it's possible to quickly capture a sufficient amount of muons.

It strikes me that the former would profit from a strong type system, whereas the latter could profit from (enforced) strict aliasing.

Why exactly would it be too low-level for Rust?

I have to install an app to communicate with my child's state-sponsored daycare. I'll have to install an app to communicate with the teachers at his future school. Is this still fine?

It'd be one thing, if it were just apps. But all of these apps are essentially just containers for some web application.

Do you get access to the web application without the app? No.

So what's the point of the apps? So they can send you notifications and annoy you with irrelevant updates concerning other groups at the same daycare all day long, because they don't care to filter?

Just an FYI: If I select "Features" / "API First" on your page, I end up at a 404.

since the daemon tries to connect to the registry with SSL

If you rewrite DNS, you should of course also have a custom CA trusted by your container engine as well as appropriate certificates and host configurations for your registry.

You'll always need to take these steps if you want to go the rewrite-DNS path for isolation from external services because some proprietary tool forces you to use those services.

I suppose they don't believe certain facts engineers are telling them. With Brexit it was coined "Project Fear". Now they're being told that adding backdoors to an encrypted service almost completely erodes trust in the encryption and, as in the case with Apple here, in the vendor. However, I suppose it is very hard to find objective facts to back this. I'd guess this is why Apple chose to both completely disable encryption and inform users about the cause.

Now we're probably just waiting for a law mandating encryption of cloud data. Let's see whether Apple will actually leave the UK market altogether or introduce a backdoor.

This is only for Docker Desktop. The Docker Engine itself is free (AFAIK). If you're on Linux, you probably don't care about Docker Desktop at all.

I get why this is annoying.

However, if you are using docker's registry without authentication and you don't want to go through the effort of adding the credentials you already have, you are essentially relying on a free service for production already, which may be pulled any time without prior notice. You are already taking the risk of a production outage. Now it's just formalized that your limit is 10 pulls per IP per hour. I don't really get how this can shift your evaluation from using (and paying for) docker's registry to paying for your own registry. It seems orthogonal to the evaluation itself.

You're essentially suggesting a Drake equation [1] equivalent for the number of security vulnerabilities based on NLoC. What other factors would be part of this equation?

[1] https://en.wikipedia.org/wiki/Drake_equation

While it's not implemented, Rust even has a keyword reserved [1] for musttail, "become": https://github.com/phi-go/rfcs/blob/guaranteed-tco/text/0000...

[1] https://doc.rust-lang.org/reference/keywords.html

IANAL. In Germany, something being true makes it non-defamatory [1].

Wer in Beziehung auf einen anderen eine Tatsache behauptet oder verbreitet, welche denselben verächtlich zu machen oder in der öffentlichen Meinung herabzuwürdigen geeignet ist, wird, wenn nicht diese Tatsache erweislich wahr ist, mit Freiheitsstrafe bis zu einem Jahr oder mit Geldstrafe und, wenn die Tat öffentlich, in einer Versammlung oder durch Verbreiten eines Inhalts (§ 11 Absatz 3) begangen ist, mit Freiheitsstrafe bis zu zwei Jahren oder mit Geldstrafe bestraft.

I'll just translate the important condition for being punished for defamation ("Üble Nachrede"):

[...] if not this fact is demonstrably true [...]

I've intentionally kept the somewhat weird word order while translating. It's just as weird to read for a German. It's an old law.

[1] https://www.gesetze-im-internet.de/stgb/__186.html

I'm not sure, most vendor camera apps were pretty much tied to the particular camera on the phone, on the phones I've had. For UVC, I usually needed to use another camera app.

You could try to initiate a video call with the locked device, though.

Well, I opened them in a plain browser profile and in the non-translated page the options seem clear to me? The buttons literally say this:

- Settings / Einstellungen

- Accept / Akzeptierten

- Reject All / Alle Ablehnen

The English translation is on the buttons in the non-translated page and those translations are fine. There's even a reject all button, which is fine too. The only not so nice thing is that the "Accept" button is coloured green.

Again, I don't want to defend those banners.

That's what I'm wondering too. This is in uvcvideo, processing data from USB-connected cameras.

So, maybe you can exploit it by connecting a camera to the USB port? That would be bad enough. But this code only seems to be called if a video stream is active. So things like unlocking a locked phone seems improbable to be possible.

I concede that cookie banners are not helpful here. I also admit that I rarely see them anymore, as uBlock Origin removes them for me. I probably shouldn't have assumed that the web I see is the web everyone else sees.

At this time of day, I'd wager half of the users here are able to comprehend German texts. The other half knows how to use a translation tool.

The primary metric of interest in this task is cognitive control, measured using ΔRT (the difference in response time between repeat sequences and change sequences).

Can someone elaborate on the naming of that parameter? I would have guessed that a parameter named "cognitive control" yields better cognitive function for larger values. Is there a reason for that name?

It's 2025 and this new tool works on X, but not on wayland. We are lost.

Setting an OS timer would make the thread use 0% CPU. “Regularly querying the system time and comparing to a limit” would not.

As mentioned, this is the first case and can be achieved by calls to sleep/Sleep/etc. You'd only regularly query if there is actual useful work to be done. That's the premise of the second case you quoted from.

Thanks, I've edited the list. :)

This article fails to separate the concerns one has with timers. There's three cases I see:

The simple case is just putting a thread to sleep for a given time. It's somewhat odd that there's no portable API for that, granted. At least POSIX has sleep, nanosleep and clock_nanosleep (list edited, thanks oguz-ismail).

The second case is that a thread wants to continue processing until a timer has passed. This has to happen cooperatively one way or another, so setting a timer is equivalent to regularly querying the system time and comparing to a limit. There is simply no need for a "timer" operating system facility. (Even if you were to plug POSIX timers in here, you'd in all likelihood still need to check some flag set in the signal handler in the processing thread. And then you'd still need to check the system time as signals can originate from anywhere, just as with sleep/etc. above.)

In the third case, a thread waits for I/O. Then, of course, the call to that I/O facility defines how any timer is handled. As these facilities are not portable, timers aren't portable. The author refers to this realization as the need to implement "Userspace timers". These are just an artifact of the I/O facility and calls querying the system time, though.

So, ultimately, not having portable timers is the least of our problems. So long as we don't unify select, poll, kqueue, io_uring and what not, we don't have a need for them. And, as the author realized, libraries like libuv, which do an acceptable job at unifying those facilities, tend to provide a portable timer API.

This is THE AI gold mine. Create agents that both support calling and getting rid of agents if you're called. Sell both.

Is there a recommended hardware and step by step guide for those new to this?

What exactly are you planning to do? OpenWrt is quite flexible. There's this https://openwrt.org/toh/buyerguide.

Can you do mesh networks?

Yes. Note also https://openwisp.org/ if you want to do a whole fleet of OpenWrt routers.

They just fixed it by now. It was different when the story was new.

It's typical Stroustrup style to write code in a variable width font. I'd wager they didn't have an option to use a variable-width font in their code blocks in their CMS and normal paragraphs are trimmed automatically.

I didn't see the author at first. However, immediately after seeing the code I checked for the author, because I was sure it was Stroustrup.

I believe you may have misunderstood my comment, as I agree.

There is more than one type of people who stress over code style. There's the group who wants to discuss about how to style your code and then there's the group who wants to just use a common code formatter and be done with that.

For example, I have objections to rustfmt's default style. I would never start discussions on rust projects about changing that to another formatter or changing its configuration. I definitely would carefully ask that people should really use rustfmt, though, if they don't do so yet.

You can find the actual specs here: https://www.amd.com/en/products/adaptive-socs-and-fpgas/vers...

As usual, you have to accept a trade-off between different features depending on the number of channels you want.

Yes, I have seen versal, in particular in defense and satcom. However, in just that field, I have also never seen an RFSoC.

I've seen lots of integrated RF transceivers that were tightly coupled to the FPGAs, but not shared on the same SoC.