lemann

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 😁

What a compact thing, also charges to full in just 3 hours from a normal outlet 🤯

Wow 😂

Personally I prefer the consumer-friendly RTR ebikes be restricted OOTB. Having people fly past you on the sidewalk riding 45km/h, without a ding of the bell or any warning, is not nice 😭

People who DIY an unrestricted setup usually tend to go fast on the road, probably because they know what power they've got between their legs lol

The design reminds me a lot of a Tern GSD. I'd be scared to leave this in public though because of the price 🤯

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

TIL, that is very neat

Beeper and Beeper Mini are two completely different things

Beeper Mini, the version that does not require any kind of MITM bridge, has been blocked by Apple. Beeper, the version that requires the bridge, still works fine AFAIK

Wholeheartedly agree with the second paragraph though 👍

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

@[email protected] pretty much explained the issue.

Would suggest asking these questions in the dedicated community for selfhosters, who'd be able to point you to specific tools and things you can use to populate your instance with new data from across lemmy [email protected]

Edit: fix community link

Your admin created it

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