BakedCatboy

Does fakespot have a chatbot? I thought it predated LLMs and is basically just some human-made algorithms to filter out suspicious reviews.

The :8b and :latest tags actually point to :8b-instruct-q4_0 so I think we're already good. You can check the tags page on ollama library and see the hashes for each tag to see which ones match.

Bro the article headline even says balcony railings. We're talking single solar panel + plug in micro inverter type setups. That's like $200 if you shop around.

And not sure if you're aware, but after the "usable age" the system produces at like 80% capacity, so unless you disconnected from the grid and really really need that last 20%, you don't need to change a thing and can keep using it way past the warranty period. Or you can add a couple extra panels. Why replace the whole thing lol.

Hmm that's very surprising. Secure boot setup mode is entirely just to enable or disable enrollment of keys, so being able to enroll keys with setup mode off and the bios locked is bizarre. I can say that my dell (xps 9560) does not behave that way - I have to enter bios and explicitly enable setup mode to enroll keys, and setup mode automatically switches back off once you enroll.

If the bios is locked you can't modify the enrolled keys - that's the point. The guide you linked assumes the bios is already set to enroll mode, which requires unlocking it.

The result is that without the bios password (or a bios in default state) you can't change the settings.

I have my laptop set to only allow booting internal drives and to verify with my own enrolled keys. The only way to bypass it is to use something like ventoy is to unlock the bios and use the one-time boot menu or to enroll their key or sign ventoy with your own key.

Sounds like this is completely about the preloaded PKs, so if you set up your own secure boot with your own keys then you're probably fine because you would have cleared out the OEM keys right?

Could even mix the yeast into a bottle of sugar syrup beforehand to give the juice a boost of yeast food. And less suspicious when dumping it.

I thought tepid was like neither warm or cool, so more of a lukemedium.

That seems like a pretty big hole in their lifecycle analysis. The ol' tow it out of the environment strategy.

CohortAttack?

It's better because PPA isn't about targeting ads at all. It doesn't share any browsing history, topics, or any information for ad targeting to advertisers at all. What it does do is provide a way for a website to tell your browser which ads are relevant to an action you take - for example on a checkout confirmation screen the site may tell your browser "here's a list of ad IDs for the shop you just bought from". Your browser then checks if it's seen any of those ads, checking completely using local data that doesn't leave the browser, then to an aggregator it reports which ads possibly led to your purchase. The aggregator increments a counter for each ad in its database and relays the totals to the advertiser. There are no unique identifiers or any information about your habits or interests involved.

When I initially heard about PPA I also thought it was related to FLoC / topics, but it has nothing to do with ad targeting or sharing information about habits / interests, it's just a way to tell advertisers "Ad XYZ was effective and led to a sign up/purchase" without revealing who saw the ad or any personal information about them, just the total number of people.

Not when the conversation tracking is done 100% locally. The only thing sent from the browser is telling a server to increment a counter - a single bit of data. It's hardly any different than a visitor counter that "tracks" how many visitors a site got, which I think would really be a stretch if you claimed that visitor counters were tracking individual users.

I'm not sure if you actually read the details, but this system enables sites to tell your browser which ad IDs are related to an action you're doing (for example on a check out page the site will give your browser a list of ad IDs for the shop) so that conversion tracking can be done locally in your browser. Then, without needing to share any personal information, your browser can tell an aggregator which (if any) of the ads you have previously seen, and that counter gets incremented.

It's literally just a view counter for ads that only increments when the ad is successful, and because the correlation between the ad view and the checkout is done locally, the advertiser doesn't need to link your ad view with your checkout action - your browser did that correlation privately and locally.

Sure no user needs this, but advertisers do everything in their power to track ad conversions and this gives them a mechanism to do that without giving them any information besides "this ad achieved it's goal 30 times", which is so much better than adtech tracking every page we visit so that they can have the information to deduce that for themselves.