[-] cypherpunks@lemmy.ml 1 points 51 minutes ago* (last edited 49 minutes ago)

yep, the concept of a "personal carbon footprint" was literally invented by an advertising agency working for British Petroleum https://www.theguardian.com/commentisfree/2021/aug/23/big-oil-coined-carbon-footprints-to-blame-us-for-their-greed-keep-them-on-the-hook

153
submitted 14 hours ago by cypherpunks@lemmy.ml to c/worldnews@lemmy.ml
[-] cypherpunks@lemmy.ml 4 points 15 hours ago

You can use this design, but if you want it to accommodate 3½-inch disks you'll need to scale it down to two thirds of its specified size before printing it.

[-] cypherpunks@lemmy.ml 8 points 17 hours ago

I wrote a comment here about why sealed sender does not achieve what it purports to.

[-] cypherpunks@lemmy.ml 11 points 18 hours ago

most appropriate use of that emoji

[-] cypherpunks@lemmy.ml 36 points 19 hours ago* (last edited 15 hours ago)

Does your computer have a floppy drive? You might be able to find a copy of this at a secondhand store:

Picture of a floppy disk with an official-looking Microsoft product label with the text: The Internet / On a Disc / * Surf quickly and easily with no need for ISPs / * Millions and millions of websites on one 3½'' disc / * Take The Internet with you wherever you go - it fits in your pocket!

[-] cypherpunks@lemmy.ml 45 points 1 day ago
69
47
[-] cypherpunks@lemmy.ml -4 points 5 days ago

I wish we’d stop calling them “exploding batteries”. The battery isn’t the explosive, it’s the explosives that were hidden in the device.

Do you want to stop calling them exploding pagers too? How about other exploding things? And what should https://en.wikipedia.org/wiki/2024_Lebanon_pager_explosions be renamed to? Maybe 2024 Lebanon explosions of explosives inside of pagers? 🙄

[-] cypherpunks@lemmy.ml -1 points 5 days ago

Right, so why are you editorializing the title to say something that the article in fact does not say?

The title is a copy+paste of the first sentence of the third paragraph, and it is not misleading unless you infer "exploding batteries" to mean "exploding unmodified batteries". But, the way the English language works, when you put explosives inside an XYZ, or do something else which causes an XYZ to explode, it becomes an "exploding XYZ". For example:

The fact that bombs are explosive is not revolutionary or all that interesting.

That fact also is not what the article is about.

[-] cypherpunks@lemmy.ml 0 points 6 days ago

sometimes a cigar is just a cigar

[-] cypherpunks@lemmy.ml -3 points 6 days ago

(@Ilovethebomb@lemm.ee:) Just to be clear, the pager thing wasn’t exploding batteries, they had apparently been modified at the production level to have explosives in them, which could be triggered by the pager system itself.

(me:) Did you read the article? It sounds like you didn’t.

(you:) The article literally talks about inserting an explosive layer inside the battery at production. Just like the comment said.

I am really curious: can you tell me, do you actually think the first commenter in fact read the article and was agreeing with its suggestion that the batteries could have been manufactured with explosives inside of them?

(you): It isn’t “any batteries can explode”.

Nobody claimed that, but in retrospect I guess I can see how, read alone, the pull quote I selected from the article to be the title of this post could be interpreted that way.

176
submitted 6 days ago* (last edited 6 days ago) by cypherpunks@lemmy.ml to c/technology@lemmy.world

edit: after 20 comments, i'm adding a post description here, since most of the commenters so far appear not to be reading the article:

This is about how surprisingly cheap it is (eg $15,000) to buy a complete production line to be able to manufacture batteries with a layer of nearly-undetectable explosives inside of them, which can be triggered by off-the-shelf devices with only their firmware modified.

screenshot of paragraph from the article saying "The process to build such batteries is well understood and documented. Here is an excerpt from one vendor’s site promising to sell the equipment to build batteries in limited quantities (tens-to-hundreds per batch) for as little as $15,000:" followed by a screenshot of "Flow-chart of Pouch Cell Lab-scale Fabrication" showing a 20 step process

110
[-] cypherpunks@lemmy.ml 6 points 6 days ago

To save others the copy+paste:

Nothing beats an Eluviated Eutric Brunisol developed on moderately coarse glaciofluvial

254
27
submitted 1 week ago* (last edited 1 week ago) by cypherpunks@lemmy.ml to c/linux@lemmy.ml

cross-posted from: https://lemmy.ml/post/20502769

here is the talk description, from its page on the schedule for KubeCon + CloudNativeCon + Open Source Summit China 2024 (which Linux Foundation somehow neglected to put in their youtube upload's description):

In Febuary the Linux kernel community took charge of issuing CVEs for any found vulnerability in their codebase. By doing this, they took away the ability for any random company to assign CVEs in order to make their engineering processes run smoother, and instead have set up a structure for everyone to participate equally.

This talk will go into how the Linux CVE team works, how CVEs are assigned, and how you can properly handle the huge number of new CVEs happening in a simple and secure way.

今年二月,Linux内核社区开始负责为其代码库中发现的任何漏洞发布CVE编号。通过这样做,他们剥夺了任何随机公司分配 CVE 的能力,以便使他们的工程流程更顺畅,取而代之的是建立了一个人人平等参与的结构。

本次演讲将介绍 Linux CVE 团队的工作方式,CVE 的分配过程,以及如何以简单且安全的方式妥善处理大量新出现的 CVE。

Here is a PDF of the slides from Greg's git repo for this talk.

1
submitted 1 week ago* (last edited 1 week ago) by cypherpunks@lemmy.ml to c/security@lemmy.ml

here is the talk description, from its page on the schedule for KubeCon + CloudNativeCon + Open Source Summit China 2024 (which Linux Foundation somehow neglected to put in their youtube upload's description):

In Febuary the Linux kernel community took charge of issuing CVEs for any found vulnerability in their codebase. By doing this, they took away the ability for any random company to assign CVEs in order to make their engineering processes run smoother, and instead have set up a structure for everyone to participate equally.

This talk will go into how the Linux CVE team works, how CVEs are assigned, and how you can properly handle the huge number of new CVEs happening in a simple and secure way.

今年二月,Linux内核社区开始负责为其代码库中发现的任何漏洞发布CVE编号。通过这样做,他们剥夺了任何随机公司分配 CVE 的能力,以便使他们的工程流程更顺畅,取而代之的是建立了一个人人平等参与的结构。

本次演讲将介绍 Linux CVE 团队的工作方式,CVE 的分配过程,以及如何以简单且安全的方式妥善处理大量新出现的 CVE。

Here is a PDF of the slides from Greg's git repo for this talk.

48
submitted 1 week ago by cypherpunks@lemmy.ml to c/worldnews@lemmy.ml
366
140
submitted 1 week ago by cypherpunks@lemmy.ml to c/worldnews@lemmy.ml
158
submitted 1 week ago by cypherpunks@lemmy.ml to c/worldnews@lemmy.ml
view more: next ›

cypherpunks

joined 2 years ago
MODERATOR OF