How hard should we push people towards proper security measures? Do nothing? Keep it subtle and rely on them to "get it"? Or be super intense and in their faces about it and induce anxiety?

And of course it's difficult because value is relative to one's personal financial situation, etc. Just feels like we're a bit too tame about this right now and could get just a tad more bold.

Reminds me of fidelity bonds in JoinMarket. https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/fidelity-bonds.md

Next-gen Dribbble, Ffffound and Cargo Collective?

Seeing lots of tiny fonts and tight spacing when exchanges, wallets, etc ask me to verify addresses. Making this bigger is an easy fix that can lead to fewer mistakes and eye strain, but might lower sales of magnifying glasses.

Cool, thanks for sharing. Good tips there.

Also, nice idea with the image comparison. Another test could be simply to see which account posted things earlier - there's a good chance that might be the original (unless dates can be faked).

Most bots I've seen, including this impersonator, also only do reposts and never post anything original. Also seems like an easy test to perform.

It's just going to be a cat-and-mouse game as it always is with these things... but better to start somewhere with the simple things than have nothing at all. I wish Primal had the "possible impostor" label.

Are you aware of any micro-apps that only focus on reporting?

Thinking a bit further. If I report someone, the client could then check if someone I follow, follows the reported account, and offer me to send DMs with a heads-up (warning) message.

Do not follow nostr:npub1q3954hly5yfw7lmlgwrphd9d77575cxdurw6ahczyptnkxw3k98qxdqjss, it's an impersonator of nostr:npub1uescmd5krhrmj9rcura833xpke5eqzvcz5nxjw74ufeewf2sscxq4g7chm. I mention it because at least one person I know follows them instead of the real Paulo.

Do enough clients support reporting? And are we already highlighting reports when we look at profiles? When someone is considering pressing the follow button might be a good moment to check for reports, maybe even retroactively to reduce load. Something I need to look into for nostr:npub1z29uqk4xl4pp6qxrcvufx20nnn782zcrtkmvmtfwkruc80l4v20sr9heag (only shows reports a person has made, not reports made about them).

Neatly organized UI. What screen is this?

Spoiler:

https://www.bitcoinuikit.com/screens/flow/home/home-backup-reminder

Makes a lot of sense. Thanks for the background info.

Just posted another weekly update with open-source bitcoin design stuff that kept me busy the past 5 days. https://gbks.substack.com/p/75-visions-of-peaches

It takes a village to build a (pixel perfect and functional) app.

Client designs has really improved quickly. Still lots to go, but love the progress.

Has one of you already built one of these?

Just going to hang out this weekend and watch blocks tick away.

Do you manage multiple wallets in the same application? Across layers? What are the use cases? And to what extent does this make sense, and are we better served with separate, focused tools more often than not?

Do devs agree?

First draft of some new additions coming to the Bitcoin Icons (all per request via the GitHub repo).

https://bitcoinicons.com/

Nice work. How do you handle music statuses that use the Spotify URI scheme? I don't have Spotify and those links are basically dead ends for me. Convert to actual URLs somehow?

Is she OK?

My weekly update is live. The great designer that I am, I modified the colors of many pixels this week (some people call designers pixel pushers but that's wrong as pixels don't actually move around). https://gbks.substack.com/p/73-imagine