100% this is the best choice for op IMO.

A big pro is that they literally don’t need any Google services whatsoever by the sounds of things

Wait hold on - persistent notifications (where when you swipe, a settings cog icon appears) have been ripped out of A14? Everything disappears when you swipe?

Why 😭

Neat, thanks for the additional insight!

fair point that I didn’t consider! my assumption would be traffic, seeing as the toll is branded as “congestion pricing” - which wouldn’t really make sense for motorcycles because they make up so little of the actual cause of traffic in NYC (large motor vehicles).

If we’re talking about noise though, and how clean the engine burns fuel, motorcycles are 100% guilty as charged IMO.

Deaths and injuries is a little muddier because there are several factors at play, fault could lie on any individual involved in the accident, or maybe even the road design itself. I don’t think these would be robust enough to use as the sole basis for a toll fee

Sounds good overall, should reduce traffic levels significantly and make people consider whether they really need to drive their car in such a compact city.

Not sure if I agree with tolling motorcycles though, they don’t take up anywhere near the same footprint as the average car

Mic drop

@PostWatchBot@lemy.lol

Adobe is the one company i’d never, ever, ever want to support, especially with a subscription. 🏴‍☠️ all day every day

Time flies man. I remember the hype for this game back in 2014 like it was yesterday

Free real estate 😂

I think so, assuming these malicious packages are all primitive enough to just look for the single file in a user’s home folder lol. The only downside here is needing to provide the keyfile location to ssh every time you want to connect… Although a system search would pretty much defeat that instantly as you mention

SSH keyfiles can be encrypted, which requires a password entry each time you connect to a SSH server. Most linux distros that I’ve used automatically decrypt the SSH keyfile for you when you log in to a remote machine (using the user keyring db), or ask you for the keyfile password once and remember it for the next hour or so (using the ssh-agent program in the background).

On Windows you can do something similar with Cygwin and ssh-agent, however it is a little bit of a hassle to set up. If you use WSL i’d expect the auto keyfile decryption to work comparably to Linux, without needing to configure anything

I think they would start obfuscating the relevant code to get around it

Many ad networks and AABs do something similar (especially Admiral) in an attempt to evade ad blocking extensions

I like this, but would really prefer if Google works with the GSMA to get these implemented into the actual RCS specs, rather than using specially crafted proprietary RCS messages to add features to RCS (like they have done for E2EE)

For me it’s the ability to set up a shared instance with the base request URL, and set headers for things like the user’s token, allowing all requests made with that shared Axios instance to be sent to the right path with the token without needing to define them for each individual request.

To be honest though something similar can be done with spread syntax in the Fetch API’s options parameter

It’s not natively supported by the base RCS standard, in the section at the end of the paper in the section titled “Third Party RCS Clients” Google explains that they’ve built the e2ee their Messages app themselves, (on top of standard RCS).

A developer has to use Google’s implementation specifically in order to send and recieve e2ee messages to Google’s Messages app (and Samsung Messages who also implemented this recently)

Although the e2ee implementation is using the Signal protocol under the hood, it’s for message content only - this is what is transmitted in cleartext (taken from the paper)

• Phone numbers of senders and recipients
• Timestamps of the messages
• IP addresses or other connection information
• Sender and recipient’s mobile carriers
• SIP, MSRP, or CPIM headers, such as User-Agent strings which may contain device manufacturers and models
• Whether the message has an attachment
• The URL on content server where the attachment is stored
• Approximated size of messages, or exact size of attachments

Without using this implementation of the Signal protocol on top of RCS, the message will deliver to the contact’s phone, but shows up as unencrypted garbled text

That is a very useful resource though, never knew there was a paper available on the implementation. Saving 😁

it’s got telemetry on by default.

Very, very hard pass. Might even blow out my suspension doing so

Of course its Admiral AAB 😭

Does safari have a reader mode you can use to bypass it? I use a FF extension that allows me to disable all scripts on a page when I come across junk like this.

Alternatively just chuck the link into Wayback or archive.is

A lot of jQuery’s features are now available in native JS - would also suggest just using native JS anyway because jQuery won’t throw any errors into the console if a selector matches no elements etc.

The only additional library I’ve needed recently for (personal work) is Axios for requests - easier than working with the Fetch API in some cases

Your admin created it

https://lemmy.dbzer0.com/post/8874717

What’s your problem with tagginator? Just block it if you don’t want to see it?