This makes sense and there's really no way around it without a change from Apple. If iOS is going to show the user a Signal notification with the decrypted message in the notification body, then iOS must be given the decrypted message. iOS could (and probably should) delete that data off the device as soon as the user dismisses/engages with the notification. But it sounds like they do not.

The bureaucracy was painful enough that we just removed from the French App Store and when someone complains we tell them to write their representatives to stop with these misguided laws.

Excuse me, monsieur, do you have a license for that math?

The most active 80 year old I’ve seen. Lots of travel, speaking at conferencing, networking in his professional circles.

Believe it or not, he’s a fairly conservative person. He’d never done yoga, breath work, sauna, cold plunge, saline IVs. I had the honor of pushing him out of his comfort zone a bit with the hippy health stuff.

He’s speed run learning how to use a smartphone and loves using it to connect all the people he meets together.

I think that was the most intriguing part of Leonard- his ability to pick up a new concept in minutes and apply it expertly. We were discussing modern cryptography and he was able to grok it in < 5 minutes.

Yes, he and Ross are still friends today. If I understand correctly they recently met up for the first time outside of prison.

Also, Google support refused to tell me what set of documents they would accept. I had to figure it out myself.

Primal recently launched “build your own algorithm” along with a feed marketplace.

P2P doesn’t work for social, see SecureScuttleButt. Rabble has moved pretty firmly into the Nostr camp. He’s one of the top minds thinking about decentralized social media. Study nostr and don’t dismiss the relay model lightly.

I (well, GPT-4) built freeqrgenerator.app specifically for my wife because she kept using the malicious sites that inject a redirect that inevitably die and stop working.

Thinking I can retire mine and use yours instead on the domain.

In our little niche the median age of a typical employee is ~21. The tasks are things like “mop the floor”.

Yes, maybe someone half-asses mopping the floor to get the points.

I’ve met many a 20-something daily user of the software who comment positively on the Daily Checklist feature. I’m sure there are those who disliked it too and just didn’t say anything.

I built something similar as a feature embedded in a niche product aimed at helping manage a specific type of business many years ago.

The most popular part of the feature was the gamification built on top of reporting. Managers enjoyed the checklists being completed (and reported) more accurately. Staff enjoyed getting a (small) raise for being on the leaderboard.

Basically we just tracked who specifically marked an item off the checklist as complete. Then provided reports (and printable awards) to management.

The business would then implement a program like “whoever completes the most tasks per quarter gets a $0.50/hr raise”.

These checklists were things like “Front of house AM” “Back of house Lunch” etc. with a step by step list of things that needed to be done.

Just throwing that out there as an idea for a future iteration for you.

We had a search function with typeahead abilities. I had intentionally removed the rate limit from that endpoint to support fast typers.

One day around 6AM, someone in Tennessee came into work and put their purse down on their keyboard. The purse depressed a single key and started hitting the API with each keystroke.

Of course after 15 minutes of this the db became very unhappy. Then a web server crashed because the db was lagging too much. Cascading failures until that whole prod cluster crashed.

Needless to say the rate limit was readded that day ;).