Hit on a message's permalink (which is the "X hours ago" link), and in there you'll find the action to Favorite it.

1. Clear that "might", it either is or isn't. An AI can get you 90% there, maybe the definitive confirmation would be good from a lawyer.

2. None of this matters if you share it from a foreign code forge and an anonymous pseudonym.

Is that possible, does that exist?

All those would be important, but don't let the perfect be the enemy of the good. We could start from the Vulnerability Of The Year: supply chain attacks.

But I do very much care about losing useful behaviors. The top-right pixel MUST still be able to register a click on the "Close" [X] button of the title bar, always.

Hide your lack of taste behind rounded corners all you want, but DO NOT change the underlying shape of the invisible event handling surfaces.

What is it that makes it "better" versus simply asking for an animated video? Is it the ability to later do some adjustments programmatically?

This kind of posts are a valuable trigger for all others who are reading it. To the author: good luck, I hope you sort your situation soon! I'm now headed to check my accounts for what recovery options I left in there.

This tends to happen more when one is young. Growing older usually means that a good old dusty 15 years great quality coat is seen as it being perfectly ok. I guess that's also what provides that feeling that some people when they approach middle age they "always look the same"... It's not cheap to have a large and varied wardrobe and at the same time filled with high quality garments.

If end consumers were able to see an exact and measurable bump in prices the next day a new stronger regulation made production more expensive, voters would be more informed and the whole cost of doing things "better" would be clearer.

I'd argue against relative dates because that's an opinionated design that requires cognitive overhead on the user. A young person might be able to mentally translate, but older ones tend to have it more difficult. Usually, opting for relative dates tells us about the designer's lack of experience with different groups of users than the normative one.

There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time.

2 taps for some other extra info such as call length, or further contact details, would be OK I guess, but for first-level info as these, it's 100% bad design.

I mean come on, design-wise this was already a "Done" thing in the golden Nokia days! https://the-gadgeteer.com/2009/03/02/a-week-with-the-nokia-n...

[*] Ctrl+F to find the image below "miss a call".