How do New Yorkers live like this? It’s 35C / 95F outside and it’s even hotter inside the subway stations with no air conditioning or air circulation. Literally any other major city or country has this beat. #nyc
I think so / I hope so? They emailed me a QR code ticket and said “Present this QR code at registration to receive your credentials.”, which I can send you.
This feature does exist on Damus and can be enabled in settings. I implemented it last year. However, I encourage folks to consider not using it and I even second guess my decision. Not being able to read content in another language is a solved problem - through automatic translations (another supported feature of Damus and other clients). Hiding content not in your preferred language means you are closing yourself off to those who may have a different perspective or culture than you. You can do whatever you want, but you’re just limiting yourself.
Sort of, it depends. And also, not for long.
1. Damus Purple, NoKYCTranslate.com, and translate.nostr.wine are all paid options with high quality translations.
2. You can create a DeepL free account for high quality translations, but requires KYC and entering a payment method (they don’t charge you).
3. LibreTranslate through self-hosting or using somebody’s server. I don’t recommend this option because translation quality and performance is poor.
With iOS 18 and macOS 15, we’ll be able to add native automatic offline translation support to notes and DMs. This feature will be free.
https://developer.apple.com/documentation/Translationhttps://i.nostr.build/nWXRM.jpg
I noticed only because I haven’t implemented relay pools in my app yet and was using only Primal’s relay. I thought I caused a bug! Normal Nostr apps won’t be affected if they’ve integrated to Nostr as it was intended!
Going full speed with Comingle the past few weeks. Finding motivation and time is hard, but once you have it, the feeling is invigorating. Can’t wait to ship the first version for folks to try and give feedback.
Some fundamental issues of Nostr that make it difficult to scale (but can be fixed):
- NIPs are not versioned. There’s no way to tag which version an event is using, which can lead to divergent interoperability issues.
- List updates are all or nothing (leading to them being nuked in certain scenarios). Updates should be incremental.
- Replaceable events don’t have versions so the created at timestamp is used as a proxy to determine freshness and that could be incorrect.
It’ll happen naturally over time with breaking changes being introduced or multiple devs implementing things in different ways.
Nostur does a really good job of keeping track of follow list changes and prompts the user to pick which copy should be kept. But it feels like a bandaid fix on top of a fundamentally flawed spec.
They do, if you subscribe to the GitHub nips repo as the arbiter of truth. Meaning you trust the group of folks who have merge powers to make decisions you find reasonable and don’t break your client (which have happened). There’s already attempts to decentralize the NIPs repo by using Nostr as the mechanism to decimate spec updates. So you could have dozens of different specifications for the same concept / NIP. You could even introduce a NIP number where the spec has nothing to do with the same NIP number in the GitHub repo. There would need to be a way of specifying in the published event which truth it subscribes to. Or not, and we just plow through this chaotic decentralized environment and hope everything works out. 😅
I don’t have much skin in the game when it comes to GIFs or opinions on it. I don’t use them so I lack awareness. But legitimate question — is it an option to install a GIF keyboard app? That way you can use it on any iOS app, including Nostr iOS apps?
On-device offline translations are becoming more of a thing. Apple just added native support and Android has had this for a while via Google ML Kit.
Nothing yet for Web, though. Translation DVMs, perhaps?
@mplorentz I was able to successfully and easily use SwiftData in iOS 17 as my persistence layer with the data models from Nostr SDK for Apple Platforms. I just put the NostrEvent or any of the subclasses in as a property into a new class tagged with the @Model macro and it worked.
Oddbean new post about login | logout
Notes by tyiu | export