The room might stink, but nobody intentionally shat on the floor.
I like this figure of speech a lot, stealing it 😁
Pressure shortens that timeline significantly IMO, similar to what happened with USB-C
I assume it's a feature to prevent Android's memory management from forcefully killing Firefox... for me the tabs don't unload, but they behave as if the JS running inside them has been frozen/paused.
Maybe installing those tabs as apps via Firefox's menu will bypass this
That's really nice! Feels great to have a positive impact on others
From GoG specifically, as they patch the older games on their store to "just run" on modern Windows
That typo 🤝 Your username
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 😁
What a compact thing, also charges to full in just 3 hours from a normal outlet 🤯
About three years ago I upgraded from a cheap MTB bike to an upright dutch-inspired urban bike.
For the equivalent of about $300 USD on sale, I got an aluminium frame, front and rear mudguards, internal 7-speed hub, extended handlebars, and all-weather rollerbrakes. They're nowhere near as powerful as diskbrakes, but they do the job.
The pie chart data is from a bike expenses spreadsheet I keep, was surprised actually to find out how little I've spent on maintenance, in comparison to completely optional accessories for the bike...
About my previous and current commuter
My cheap MTB had served me well for 4 years prior, despite being a bit neglected in the maintenance department. Don't get me wrong - there was chain cleaning and re-lubing after wet weather, replacing diskbrake pads and all that stuff, but it wasn't perfect and sometimes it was just plain tedious to do.
The upgrade made a lot of sense at the time, and after 3 years of owning the Dutch-inspired bike I've not needed to do much maintenance at all. However, it's a little difficult to get parts for the bike outside of the Netherlands, worsened slightly by the original retailer no longer selling consumables such as the rollerbrake grease and internal gear grease. Despite that the bike has been rock solid, still shifts and stops like new. I'll need to give the internal hub an oil bath at some point though - not looking forward to that...
I last topped up my front and rear brakes with Shimano's rollerbrake grease after hearing a loud unsightly noise while braking.
The brake performance has been OK so far since the re-greasing, but I'm concerned at how much grease has been coming out consistently.
There are a lot of hills in my area (sadly not an environment the rollerbrakes are recommended for) so my usual braking style is similar to 'cadence braking', where I pump intermittently to prevent overheating and cooking the grease.
Is this leaking something to be worried about or is this normal for my use case?
I don't understand this attitude at all... Some people are better off staying on Reddit IMO
The last time I checked, piped had a button right on the playlist page to export playlists as JSON. You can then switch instances and re-import that data back in
I'm not sure about subscriptions though, only really use piped for watching videos quickly or listening to music playlists