tl;dr

• CNC aluminum Chassis (matte black)
• 74wh battery
• wildly-efficient Panther Lake chips
• Ubuntu available pre-installed
• 20hr. battery life.

Another interesting bit from the presentation: Framework revenue is steadily-growing, in a market where many consumer OEMs may not exist much longer due to AI scams and razor thin profit margins. Maybe they can see the writing on the wall and pivot into this “niche” market as well? Increased revenue is allowing them to invest more in development, including the first custom-made display explicitly for Framework devices.

Overall excellent advancements, and a promising future for the company, despite market conditions.

that still doesnt allow sending emoji reactions.

Either way, it doesn’t matter. The point is, RCS does not matter. It is not necessary.

I’m not sure what you mean. Every receiver has a sender. If you send it to someone with Google Messages without RCS, they will receive it.

It doesn’t, actually. Google Messages implemented this before Apple got RCS. It’s as simple as seeing a message come in that says " liked message" and converting it into a 👍 response for the referenced message. Unfortunately no one has followed their lead on that one.

This is a Mac app and not web-based

I’m yet to find a web-based RSS reader that’s not terrible. NewsFlash for Linux and NetNewsWire for Mac are the best I’ve seen but both are local. They both also support syncing to a FreshRSS server but I’ve never had success.

FreshRSS has a horrendous interface, IMO. Can be fixed but it is way way more complicated than it should be.

Currently I’m running Miniflux but it doesn’t seem to be able to refresh itself or sort articles chronologically.

Edit: MiniFlux seems to have fixed itself somehow. I’m using FluxNews on Android. But it doesn’t support “reader” mode, which I find to be a vital part of any RSS service.

DISAPPOINTED

😮‍💨

Is it possible to transfer RAID drives from a Synology server to an Ubuntu server without losing the data?

They all suck and should be avoided.

You entered a thread explicitly about E2E encryption started by ShortN0te

That person replied to a thread I started, not the other way around. It was never about E2E. It was always about encrypted backups.

It could have a encrypted backup feature but it won’t change it’s fundamental purpose

It’s not supposed to. It shouldn’t.

They’re meant to be workable in other tools like QGIS, Strava or Komoot. Encrypting them would break that entirely.

Then make it optional? Or don’t, I don’t care.

deleted by creator

Halfway through you shifted to encrypted local backups

I never shifted anything. I was talking about encrypted backups on a server. These can be encrypted locally before being synced to a server.

you first called ‘single-party encryption’

Nope, you literally just made that up. I didn’t say that and I don’t even know what that means.

I said it wasn’t realistic in the context of the selfhosted backends we were discussing.

…but it is.

And yes, lots of apps do encrypted backups because they are backup apps. Colota isn’t.

My suggestion was that it could be…

The existing export is for tools like QGIS or selfhosted backends and encrypting that data would break that use case entirely.

You already have local backups that could be encrypted and then synced to a general storage server.

Encrypted import/export for backup is a separate feature that doesn’t exist yet, so there’s nothing here that’s badly implemented.

I said literally nothing about your implementation. You’re imagining things. Please read more attentively.

I don’t know what you want man

I honestly don’t know how to be more clear about this. It’s not complicated. I want client-side encryption, man.

i didn’t realize this was one of those “digging my heels in because I don’t know how to be wrong” threads

LOL I didn’t know that either, but here you are!

You just asked the creator of an exclusively client-side app whether they support encryption.

Client-side encryption is not a novel concept.

something like Keepass where the file itself is encrypted, you have to use some form of auth to decrypt it on use

That’s significantly more complicated and time-consuming.

No one is talking about a phone or a PC, we’re talking about a server.

Also phones and PCs are only encrypted at rest.

“Not so bad” at what? They’re doing this out of their own interests. It doesn’t mean at all that they care about privacy, and in fact they’re one of the worst offenders.

I already explained several times why that’s not realistic

You haven’t. You’ve only explained why you don’t want to do it, which is fair, but you keep presenting as if it’s not possible, which is not accurate. Lots of apps can and do create encrypted backups.

It’s not that I don’t want. I can’t implement it because I don’t offer a server.

You don’t have to. You just have the app encrypt the data before it’s backed up and exported.

you are not understanding mine which is the actual use case of the app

I understand the usecase but you’re acting like you don’t understand the purpose of encryption, for some reason suggesting that it’s supposed to prevent hacking, when that is not at all what it does.

If a server gets hacked where a user sent data from Colota there is nothing the app can do about it or to prevent it

It can’t prevent the hack, it absolutely can protect the data, and make it useless. That’s the entire purpose of encryption.

I don’t think it’s the job of an Android app to protect a server from government hacking attacks.

Again, it’s not supposed to.

Also the app is offline-first. There is no server needed unless the user specifically configures that.

The server is needed for the same reason a server is needed for anything: to back up the data.

If you don’t want to implement it, that’s fine, I respect your decision, but there’s no reason to come here pretending not to understand its purpose.