Well within the budget of a private investigator or burglar or peeping-tom or abusive ex-partner.

No need to scale; plenty of privacy/security incursions don’t require mass-surveillance.

That said, I’d suggest that the attack does scale economically . Think war-driving but with one of these setups – cruising around in a van through a dense neighbourhood collecting short clips of cctv footage looking for something of interest.

Ohh, so “pavement” meaning a sealed road surface?

In my head I’m trying to figure out what the footpath (U.S. “sidewalk”) a.k.a. U.K. pavement fits in with the jibe.

[…] the attack is an extremely expensive nation state level operation that doesn’t scale.

About $250 at most. Quoting the linked page:

Below is a list of equipment we used for the experiments.

• (1) Software Defined Ratio (SDR): Ettus USRP B210 USRP, ~$2100.
• (2) Low Noise Amplifier (LNA): Foresight Intelligence FSTRFAMP06 LNA, ~$200.
• (3) Directional Antenna: A common outdoor Log-periodic directional antenna (LPDA), ~$15.
• (4) A laptop, of course.

Note that the equipment can be replaced with cheaper counterparts. For example, USRP B210 can be replaced with RTL-SDR that costs ~$30.

To reproduce the attack: our GitHub repository provides the codes and instructions for reproducing and understanding the attack. We have prepared a ready-to-use software tool that can produce real-time reconstructions of the eavesdropped videos with EM signal input from the USRP device.

I wonder when (if?) orbital radio receiver arrays (a la starlink) are sensitive and discriminating enough to be used for this type of attack.

No, the “distributor” is the part which runs on your portable device, receives the push notifications, and wakes up the target apps as necessary.

https://unifiedpush.org/developers/spec/definitions/

Conversations can be a unified push distibutor: https://unifiedpush.org/users/distributors/conversations/

…and I’d trust it (battery-wise) with that. I have an old tablet with conversations running without battery restrictions on it, and if I’m not actually picking it up and using it it regularly goes 1-2 weeks on an 80% battery charge before it dies, the whole time giving audible notifications for XMPP messages/calls (which I attend to on other devices).

They’re a little pricey I suppose, but judging by a few minutes comparing gumtree listings for hatchback cars and cargo bikes:

< 20% the cost of a hatchback in analogous condition/age/fanciness.

To be clear though: by E2EE here I mean browser-side encryption with zero-knowledge on the server side.

Etherpad is still encrypted in transit with https; only the server can snoop.

Cryptpad and other web-based E2EE services can still be completely compromised server-side by serving malicious code to the browser, and practically the user would never know.

Cryptpad:

• Full-on google docs / office365 / libreoffice type replacement with collaboration.
• E2EE
• The complexity means it doesn’t work well on mobile, takes a while to load on a slow connection, more frequent bugs. (3.5 MiB page transfer)
• Self-hosting is complicated.

Etherpad:

• A competent collaborative rich-text editor. Doesn’t do spreadsheets or presentations or […].
• Not E2EE (you need to trust that the server a bit more).
• Lightweight, works on slower connections, works alright on mobile. (1.7 MiB page transfer)
• Self-hosting quite simple.

PrivateBin:

• Super-simple plain-text/markdown pastebin. No editing possible once saved.
• E2EE
• Very small. Works fine on slow connections and mobile. (0.2 MiB page transfer)
• Self-hosting very simple.

I suppose it’s likely.

Until then, keep riding. Cycling releases an order of magnitude less rubber dust than driving, and is distributed approximately according to population density on local roads/paths, not concentrated on traffic sewers/freeways.

Sorry everyone, I did try searching the lemmyverse for any previous postings of this article using “signal” in the search feature on my instance, but it turned up nothing at the time.

Lemmy.world seems to have a handle on all the cross posts: https://lemmy.world/post/9121235

DV-55521?

Use a good XMPP client like dino/siskin/conversations and OMEMO just works. XMPP client OMEMO support status.

You can’t argue “not all XMPP clients support e2ee” without arguing the same for matrix – not all matrix clients support e2ee.

Hi! I’m over here on lemmy, and created this post as a link to your post. I don’t think there’s a mutually compatible way to repost/boost a mastodon post into a lemmy community, but this seemed close enough.

As per the quote below, a car loses about 0.08g of tread per km.

Compared to a car, a bike tyre is about the same diameter, 10% of the width (~20mm), 28% usable tread depth (~2mm), has 50% less wheels, and can travel 10% the distance (~10000km).

This suggests a (very approximate) tread loss of 0.08 * 10% * 28% * 50% / 10% = ~ 0.01g per km for bicycles.

For replacing longer car journeys less typically travelled by bicycle, rail transport is the best solution and removes the issue of tyre wear.

Quoting [deleted] in r/theydidthemath:

Using the same assumptions as above (215/60R16 tires, 7mm of tread loss over 100,000 km), I estimate the loss of tread by volume from each tire as follows:

Cylinder with a diameter of 664 mm and a height of 215 mm has a volume of 74,412 cm3. Cylinder with a diameter of 664-(2x7)=650 mm and a height of 215 mm has a volume of 71,307 cm3. The volume difference between a new and worn out tire is 3105 cm3.

Typical land to sea ratio of tires is 60-70% land, depending on the type of tire. If we go with an about average value of close to 65% tread, we get the lost rubber volume of about 2000 cm3 or 2,000,000 mm3 over a single tires lifespan.

Each revolution of a tire loses about 0,04 mm3 of tread, which, according to Wolfram Alpha, is a bit less than the volume of a medium grain of sand.

If we look at the entire car with 4 tires over a kilometer of road, we get 80 mm3 or about 0,08 grams of tread lost per car per kilometer.

I agree. It’s just the title ABC News had on its article.

Of course they would.

Having wider tyres ~2"/50mm or so pretty much eliminates the risk (and gives a comfy ride). If you really like the speed of narrow tyres, it’s really quite safe with the right technique – crossing tracks at an angle to avoid mishaps (I find 30° is sufficient, 90° is never a problem), and when they’re slippery, treating them like ice. It becomes second nature soon enough.

I think there are some rubber/elasromer inserts which have been developed which also eliminate the groove – it presents a flat surface to bikes, yet squishes down for the tram wheel flange under the immense weight.

The nuance is recognising the Google hegemony is supported by choosing Chrome.

The understanding is realising what is happening to the open web as a result.

Sounds like you have too few geese/sheep, that’s all. 😆