Another reason to migrate to NIP 17 and stop using NIP-04s DMs, which have a similar issue.
nostr:nevent1qqsy9qtwxjagzdd6tqzsws6j0nud5g6u3fyt3d0cnxjnkj6q8utqnpspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvpsgqqqqqqs6x7g77
I'm very curious to see the outcome of this shareholder vote pushing Microsoft to invest part of its treasury in Bitcoin, which may prove more effective than stock buybacks.
Yep.. that is why it is so interesting. They should be looking into it regardless, but something triggered the shareholder vote because they weren't studying it.
Huge privacy implications when using third-party services for translations. They get to see and potentially track everything you translate.
Also, they cost $ 9/mo/user in USD which is not in the budget for most of all users.
Which part of the interface? Just the translations? I would hate to having to press a button every time a post in another language shows up... Lots of UX friction there. Users are more likely to simply ignore the post.
Hum.. they are def a lot bigger, bolder, softer and occupy more screen space. We always tried to keep them small because: 1. The post is the important part, not the reactions and 2. Lots of screens are really small and bigger buttons tend to get more on the way of content.
Yep, but translations are local. Google knows which language models you are downloading but that's it. It doesn't know the contents of the message being translated.
It only works online. You wouldn't want an online service receiving a copy of each of your DMs to classify language (which is required to figure out if translations is needed) and translate if asked. Most libre translate services out there are just tracking everyone to sell data to sustain the service.
Maybe. I just use Google's in-device ML-Kit. It's fairly old at this point (considering the new Gemini tools) but it still works (good enough translations) and it is indeed fully local.
There is no opensource translation model to run on the phone yet. There are online services, but those are a massive privacy issue because all your posts go over there. They can easily track you.
for starters... the ability to comment on bets and share bets people make
But for real, any Nostr client could code the betting market in thier main UI
Took me a full week to nail down some of the bugs, but Negentropy on native Android/Kotlin is now done and fully compatible with the C and JavaScript implementations.
Next adding it to Amethyst... https://github.com/hoytech/negentropy/pull/15
I do hope it becomes part of nip-01 (mandatory for all implementations).
I don't think Nostr survives the massive amounts of data without very fast SYNC protocols.
that's not a username. Its just a display name for your key so you know which one is it. You can literally write anything you want. Otherwise it's going to be hard to switch accounts and selecting the right one.
Is this to be used just one time? Because otherwise we will need to improve a lot of screens to make sure you can find which account is which in the app. We usually hide most of the key..
Hiding hashtag is a spammer tool. They just add all the hashtags to the event, but not at the content. Which makes the post appear everywhere, in every hash tag search, without poluting the message. To counter act, we add all unlisted hashtags back in the post to make it really annoying for followers of that account.
Oddbean new post about login | logout
Notes by Vitor Pamplona | export