Logans_Run

Intel was asked whether its attestation infrastructure poses a sovereignty risk under RISAA, the 2024 US law that can compel hardware manufacturers to cooperate with secret intelligence orders. That question went unanswered.

Google did not respond to a request for comment for this article.

Any submission that opens with "In the summer of 1998 I graduated from college and went to work as a programmer at Microsoft in Redmond, Washington. I was put on the group that was building MSN Messenger Service" and then goes in to reverse engineering the OSCAR protocol gets my vote. When it then goes in to the origins of Microsoft's "Embrace, Extend and Extinguish" thinking all I can say is - Thanks for the trip down memory lane.

150%-170% on desktop monitors.

Link for those that want to learn a bit more about the project.

Department for Business, Energy & Industrial Strategy Report - Lessons Learnt from MeyGen Phase 1A (Final Summary) - https://webassets.bv.com/2020-06/MeyGen%20Lessons%20Learnt%2... )

Ok great but let me just make sure that I understand things correctly here... the UK government (and by extension the UK's Tax-Payers) build these nuclear power stations just so the the FANGS* can hook their DC's up to it and charge their users for access? Am I understanding that correctly or am I just being jaded and cynical? Given that apparently building DC's on greenfield land is A-OK [1] because there are no brown field abandoned industrial estates anywhere in the UK (/s) and now on top of that, the UK tax payers are expected to pay for the power stations via increased bills due to "infrastructure improvements" I am beyond the “SMH” stage.

[1] https://www.theregister.com/2025/05/16/uk_overrules_local_co...

*FANG is rapidly becoming an outdated term for the big 5 AI players but in this case the acronym seems a good fit although Wikipedia confidently informs me that these days acronyms like MANAMANA or G-MAFIA BAT are more relevant.

It would be of interest to hear some thoughts from those currently involved in the ad-tech industry about the larger elephant in the room that sometimes is referred to as ‘using ad-tech to influence and alter human behavior and public sentiment’. .

* The above comment is not meant in any way shape or form to diminish, dismiss, distract or detract from the humanitarian outrages and human rights violations that have and are occurring in Gaza however in a (probably futile) wish to prevent a downward slide of "my side is right, your side is wrong" visceral response/tone of comments - perhaps it's time to reflect on the larger discussion around government/political 'nudge units' and the ways that both the public at large and your own opinions might be being steered in ways that border on the almost subliminal level.

Just a snippet from https://files.catbox.moe/i0tkbp.txt

Mike Howell: Are you aware that you won't be able to wear a furry tiger costume when you're getting pounded in the ass in the federal prison I put you in next year?

vio: such unprofessional language from an executive director, would you mind if i shared this? :3

Mike Howell: Please share widely. I hope the word spreads as fast as the STDs do in your degenerate furry community.

vio: meow :3 (image of cat :3)

Mike Howell: Bestiality is a weird sin. It shows you've gone a "few clicks" too far in trying to satiate your deviant appetite.

AND another snippet vio: none of our members will be identified or outted by your organisation built on hatred. the only ones deserving of a destroyed life are those within your organisation. you want me to cooperate? with what, spreading misinformation and hatred? we wont turn against our own people.

Mike Howell: Your own people turned against nature. We will only accelerate the cycle. . https://web.archive.org/web/20240712173219/https://files.cat... . ... WTF! :-(

o.d.g. I lolled sooo hard when I got to the bit that I thought would be coming and yep, ...... sure as bears defecate in the woods... there it was... Stripe Radar ... featuring AI!!!! " it uses machine learning to " etc. Gasp, Shock horror, wow, much AI ffs) ... and the pricing? Laffs even harder.

Pricing:Stripe Radar for Teams is priced at 7 cents per screened transaction . GLWT M8 L0L.

This section of the article is what chilled my blood more than a little ....

"... giving Elon Musk and Jeff Bezos and whoever that they include emergency universal comms on their satellite constellations to get permission to fly, and we're good. Emergency call services are very low bandwidth, which is very cheap, very power frugal, and very reliable to add to high bandwidth satellites and low cost devices on the ground. Because we're talking universal standards here, we can bake in solid location detection that we know will work. You can build the user bits into standalone devices or as part of a mobile phone, as long as it's a simple one-button activation."

... what gave me pause for concern was the thought that an otherwise obvious idea with a cheap and easy solution runs the risk of establishing Elon and Starlink into one of those "Too Big / Too Essential To Fail" types of corporation.

Oh dear lord .... sub heading states - Storm - Assisting in Writing Wikipedia-like Articles From Scratch with Large Language Models

Good luck with this storm, wiki's the world over. Just a thought but ... maybe someone should ask an org like the Internet Archive to snap-shot Wikipedia asap and label it Pre-Storm and After-Storm

I would ask it to draw me a picture of <insert whichever $deity you feel like specifying>, light the blue touch-paper and grab some popcorn. That is all.

See also [1] "NIO's 150-KWh Battery Pack Reveals Its Secrets Ahead of Schedule in New Owner's Manuals"

[1] https://www.autoevolution.com/news/nio-s-150-kwh-battery-pac...

Although not the author, a comment made on the issue by someone on another forum [1] expresses it much more eloquently than I can.

" Ignore the SMB/homelabber at your peril...

VMware (20+ years ago) cast their net out as far as possible. They embraced partners, channels, users big and small, experienced and beginner. That formed the foundation of a massive ecosystem of community knowledge around their products that made them attractive (in addition to the stability & ease of use). None of their rivals ever came close to this. That's part of the reason they have such a massive market share (80% of VM workloads not running in the cloud run on VMware).

ESXi free was extremely limited, but it allowed users easy access to the hypervisor to deploy it in a home environment to see what the fuss is about. It gets beginners/novices interested in the product, and eventually the add-on products. From there it's an easy hop to VMUG licensing and additional products to get familiar with the rest of the VMware stack.

Those novice users are usually employed at entry-level jobs at smaller companies, and they tend to stick with what they know or have learned, so ESXi free becomes an easy deployment for those businesses. From there it's an easy hop to adding additional licences as they realise they need a vCenter and more of the advanced features to stay on top of everything (and the beauty of ESXi is that it's just a licence key change to unlock all of the features, no reinstall of a full version over the top of the free one).

Those novice users gain experience, some move on to larger companies in more senior positions, and that knowledge, experience and product inertia continue to snowball into more VMware deployments, more add-on products used (maybe some of the vRealize/Aria stuff, or NSX, or vSAN) and you have a full ecosystem of end-users who are advocates for the solutions used.

That was certainly my journey - I deployed ESXi free about 15 years ago onto a single host in my network lab to see what the fuss was about. It ended up sparking an interest and knowledge in a field that culminated in me eventually being employed by VMware and working with their biggest customers and partners globally.

You can ignore those SMBs and home users and still make money, but don't be surprised if in 5+ years time you have a massively reduced market share further up the tree with large commercial/enterprise customers. With Broadcoms pricing changes I'd suspect it'll be even sooner than that... "

[1] https://forums.theregister.com/forum/all/2024/02/13/broadcom...

* Pricing

Pricing and access depends on your membership or subscriptions with ACM. Purchase this Article Purchase this Article: Protecting Secrets from Computers Terence Kelly

    Purchase Article
    Purchase Article
    Non Member$15.00
    ACM Professional Member$10.00
    ACM Student Member$5.00

    Already an acm Member? Sign In or become a member

deepdyve logo Available at DeepDyve

The Largest Online Rental Service for Scholarly Research

Price: $0.00 *

I.A. or similar link kindly requested please. TYIA

Who here in the HN crowd would be up for porting this to Android as a sort of open-source crowdsource project? Any takers? At a guess (about licensing) I would say that whoever sets up the initial GH repo uses this quote from the author " waiting for an enterprising Android engineer to port it themselves—I’ve placed enough detail in these posts! You’re welcome to do so, just make it free for everybody."

Quote from article It also suggested that street wardens could monitor compliance.

The trouble is that it has always been a case of "Backdoors for me but not for thee" rather than backdoor free.

And as for the price - I was surprised at the cost stated when even a quick search turned up various RTC modules for as low as 0.50p/$0.50 per module which I'm sure could be obtained (in bulk) for a lot less.

Ah well, I guess I just don't understand big business and geo-politics.

At first glance I was about to comment on unsprung mass but before doing so I did a quick dive and can see that it isn't in actual fact an "In-Wheel-Motor" by any stretch of the imagination which makes it a bit of a misnomer.

[1] https://ree.auto/technology/

Not a Tesla owner but I would have thought that Musk & co would be able to state exactly when the Autopilot wasn't engaged and when it was just from the logs and yet they are 'unclear'. Is that another way of saying that the AP bailed and went "here human, fix this" in the final seconds? I mean, how hard can it be to check the logs from moment of impact backwards and state "it wasn't turned on for the journey" or "it was turned off 3 minutes before the crash". Unclear huh?

> The automaker subsequently engineered a system that prevents Autopilot from executing the turn which caused the crash.

So, nothing wrong with the system but they patched it anyway. Riiiight.

I'm not defending the practice by any stretch of the imagination (it's wrong to hotlink, simple as) but I can remember in the heady halcyon days of the early internet (back when Windows 95 had yet to become a thing) hotlinking was done out of pure ignorance about the impact it had on the hosting site and most doing it knew no better nor of the impact it had on the hot-linked servers' resources.

Given that Eternal September remains a thing to this day, I wonder if that remains the case?

As for Google Bot being well behaved - I'm glad to hear that this has changed because at the turn of the century (which is the last time I dipped my toe in to self hosting) it certainly wasn't well behaved in the slightest and it would ruthlessly crawl away, happily ignoring any robots.txt limitations applied.

A less hashtag version: https://www.omafra.gov.on.ca/CropOp/en/indus_misc/chemical/r...

Other Common Names Include: Dandelion, Kazak dandelion, TKS, rubber root. Latin Name: Taraxacum kok-saghyz

Dandelion roots also contain substantial amounts of the starch inulin, which can be fermented to produce fuel ethanol.

USDA Report from 1947 entitled "Russian Dandelion, an Emergency Source of Natural Rubber" https://archive.org/details/russiandandelion618whal/page/n1/...

As a grey/gray beard, I fought long and hard for $reasons against any distros that switched to using systemd. I lost that fight and although I wouldn't say I will ever fully embrace systemd (for the same $reasons), I accept that it is "the way forward" chosen by so many flavors of *nix that I might as well suck it up as the de-facto way of doing things. To be clear - I'm not salty about it because, meh - life's too short to take a teaspoon to the incoming tide. I've upvoted this submision and bookmarked the link for easy reference.

That is all.

Well played ;-)

ps - I spotted the pedant that is technically correct, and I claim my 5 McFun bucks!

Two things -

1) Keep it current, with a way of (actively) marking supercede / outdated / retracted copies (somehow? perhaps an (optional) url on each doc to check for "freshness"?))

2) Document the documentation. Having a master index greatly assists version control, esp for tech docs.

Having read their privacy policy and done a quick search for Dark River Systems (bottom of link's landing page, to the right) that would be a hard "Nooooop!" from me. Then again I guess that's why there are things like guerilla mail etc eh?

An interesting 5 minute rabbit hole tho and https://www.sapperlabs.com/code was a chuckle... for instance ---

"DISCLOSURE OF YOUR PERSONAL DATA Business Transactions

If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy."

Two things to note. Firstly, I can't see why this is any different from modern fuel injection systems that don't achieve the same results and secondly I stumbled across this while doing some research about the Sloot Digital Coding System.

Would it be possible to create a read-only instance that was federated with every single other instance? Possibly there is already one or it's been tried and didn't work but the way I envision it is this -

You sign up to the read-only instance and can see the entire fediverse's contents and posts and when/if you wanted to comment, the app would let you know that you had to sign up to the instance the comment came from to post your own comment and take you that instance's sign-up page.

One of the biggest turn-offs for me was finding which ones to join and/or had content I was or might be interested in.

Regarding point #2) Absolutely yes that can be (and is) a problem for exactly the reason you say in terms of synchronising 2 (or more) PV setups to the local grid and (I would imagine) have the facility for emitting volumous clouds of magic smoke.

Fortunately the solution would appear to be use of a GPS central time clock that is fed to the 2x PV arrays individualy... if you run your own local time server you can 'skew' the clock signals to each array to get them in sync with each other and then in to a dummy load of spare lead-acids or a capacitor bank (if you want to get fancy and don't mind the 'large gray box' emitting smoke and launching itself off the wall from time to time).

Then you sync your 'mini-grid' to their slightly larger mini-grid.

Oh and when synching - never forget the old-school 4-light-bulb trick as a visual confirmation that things are synched correctly before tying in to the grid. Oh and fuses, large ones. With spares.

If you can find a friendly H.V. engineer or Linesman they might be able to tell you what clock source 'their grid' uses (GPS, Network time etc etc) which makes synching to the local-ish grid a whole lot easier if you have the exact same setup. I think the main thing is to make sure you have the dummy-load ready to feed/smooth what can be at times be a large inrush/outrush till the load equalizes.

Obviously, always seek out advice from someone that knows what they are talking about and has knolwedge of local laws, quirks of the grid etc.

1) Among Intel's expressed benefits for a 64-bit mode-only architecture is removing ring 1 and 2, dropping 16-bit addressing support, eliminating ring 3 I/O port accesses and the string port I/O, simplified segmentation model.

- Sounds Reasonable to me given the current erosion of Ring barriers being effective as a security measure.

2) Removing some unused operating system bits.

- Good idea, time to chuck out those burned magic key backdoors aka no longer zero-days.

3) Those wanting to run legacy operating systems or 32-bit x86 software would have to rely on virtualization.

- Again, sounds reasonable given the current speed of processors and the improvements in Virtualization plus the (likely) age of 32-bit software.

Gosh Intel - Wheres the trap?