justusthane

The main problem with OP's experience is that the AI response has absolutely nothing to do with the search results and is functioning purely as a chatbot.

Well I'll be. It does seem that the ability to get the subnet mask is present in the beta version of Dart, so hopefully this will be resolved.

Are you sure? That would be a bizarre limitation. It seems much more likely there's something else going on where it's not working

From the linked page:

> When a cycle is started, a wax motor is actuated pushing a pin outward and locking the door. This design has cost, reliability and safety advantages. In moist conditions a wax motor costs less for equivalent reliability than an electromagnetic solenoid or motor latch. It has a predictable passive release delay. If power is lost the door remains briefly locked, designed to be longer than the high speed spin cycle coast-down time, then reliably unlocks as the wax cools.

> I really appreciate this attitude towards this because it recognizes that there are a lot of security teams out there that don't take a nuance view of CVEs

This is true, but also: needless CVEs place a burden even on security teams who do take a nuanced view of CVEs - it requires some amount of effort to evaluate every CVE and determine whether it's applicable or not.

Same. I don't get motion sick, and this made me feel uneasy. It would make my wife motion sick instantly. It's an interesting concept though, and I can see the utility of it.

It's an in-depth post about something neat that someone made. Exactly what I want to read on here.

Not to me, but who knows

The author’s take on this in the Mitigations section makes sense to me:

> Remove the timeout, and a legitimately stuck core hangs the platform on the first SMI. Increase the timeout, and you kill performance on many-core platforms that are forced to quiesce all cores every SMM entry. It's not clear what the best path forward is, or if there is even a path forward at all.

I don't think was unkind, and I think that if you make something public, opinions are always warranted.

When someone says "I nearly had a heart attack," it's _highly_ unlikely that they actually nearly had a heart attack. I don't think the chances are good that anyone actually had a heart attack.

I really worry about AI leading to the information death of the internet. If everyone is getting their info from AI, rather than actually reading websites/blogs/forums, is there any incentive for posting things like this on the internet in the first place?

Is this what you're talking about? https://www.star.nesdis.noaa.gov/goes/conus_band.php?sat=G16...

Apologies for my tardy response. I tried it and am disappointed to report that it does not, in fact, "just work", but migration is easy anyway - there's a "File to DB graph" import option. Point it at your existing Logseq folder and it sucks the content into a new graph.

I agree that the migration path should be clearly documented.

This is a minor nit, but why is OP's script a Python script with a .sh extension? I know the extension doesn't "matter", but if I see a .sh extension I'm expecting a Bash script.

I would assume that it “just works”. I’ll try it tomorrow and report back.

I’ve found croc to be more reliable than MW in across different network architectures — croc has worked in places where MW has not. I’m not sure why.

> then suggested I did get hired for my cybersecurity expertise, that I do take my obligations seriously, and he could just ask me to do whatever they were planning to do from the MDM console, and it would get done. He insisted that wouldn't be necessary since in his worldview the MDM was unbreakable and he just needed to reconnect to Wi-Fi or something.

> Very amusing worldview.

It’s ironic that you’re displaying the exact behavior pointed out by the GP:

> This is how you behave when you think you're so much smarter than everyone around you that consequences don't apply to you.

MDM is implemented to protect company assets regardless of the actions of the users. It would not be due diligence on the part of the director to trust you to wipe your own device.

It’s not clear to me what the point of your comment is other than illustrating that you’re smarter than your director.

Isn’t that already what DMARC does though? For DMARC to pass you need DKIM _or_ SPF alignment, not both. It’s designed that way because there are scenarios where SPF _can’t_ pass (email forwarding, mailing lists). So a well-configured mail server should accept your email regardless of SPF if DKIM is properly configured.

Re: specific keys for specific usernames: I can appreciate that you wish DKIM allowed for this, and I could imagine it being handy, but that was never the problem DKIM set out to solve — DKIM and SPF are all about be domain.

I’m also not sure it’s a great idea — the sender identity should be under the control of the sender. If you control the domain @foo.com, you could use that ability to assert that an email came from Bob, even if Bob never sent it. Contrast that with Bob signing the email using his own private key.

What is it about this that makes it particularly hard to OCR?

Also very interested in this. I was playing around with doing the same thing with YaCY. I want the proxy aspect so that I can proxy my phone traffic through it as well.

I've seen this solved in some platforms with localstorage, so that it automatically saves your "draft" as you type and seamlessly restores it if you re-open the page. It was a really nice surprise the first time I experienced it (after closing a tab by mistake).

Really? I’d think more like chaotic good -> lawful neutral (at best).

No, they're very different. Using webkitdirectory="true" on an <input> element just allows you to select a directory to e.g. upload it to the server. It's a one-time operation.

This API returns a handle to the selected directory, giving the webpage ongoing read/write access to the directory.

You couldn't use the former to e.g. create a local-first notes app that stores its files on disk.

The article also contradicts itself halfway through:

> There remains a clear penalty for being an open LLM user.

The conversation here _around_ the article is interesting, but the article itself boils down to “I’m going to try using open models and hope for the best.”

Parent commenter is saying that they do this _after rooting their phone_

You could look into Podman as well - it's rootless by default, and often can be a drop-in replacement for Docker.

That’s a really interesting and pretty neat approach. How do you communicate with it? Just su to that user? Or tmux?

Although I can’t help but think that a VM is still more convenient, more flexible, and more secure.

I have "Agree" and "No thanks" buttons on my cookie banner. Tested on FF and Chrome (Windows) and Safari (iOS). Maybe a UI bug for you?

I was excited to see there's a Canadian one, but it's just a Wordpress blog?