Oh, I don’t know why I quoted that post. Tired from traveling. The initial post made me do an online search and found another one. I meant this one: https://github.com/mlc-ai/mlc-llm
It’s working as expected. The half translations issue is likely due to either the Turkish translations being incomplete, or that we haven’t pulled them into the app build. Using a different language in Damus from your general iOS language preference is already supported out of the box by Apple.
iOS Settings > General > Language & Region. Ensure that English is also a preferred language, but it doesn’t necessarily have to be listed as the first one.
Then,
iOS Settings > Damus > Preferred Language > English.
In theory, that sounds nice, but in practice, it’s difficult to pull off. Most in-app strings are highly contextual. Client needs for user-facing strings can differ greatly. You can’t just piece different words together because languages have different grammatical rules. Depending on the client’s platform or framework, the string format also differs. At best, we could have a glossary of common Nostr terms that translators can refer to, but it’ll still have to be very manual to integrate them into the app and require handholding by translators who know the language.
I’ll be speaking about Nostr at the Unconfiscatable conference in Las Vegas for December 7 and 8. Excited to have the opportunity to onboard new people onto Nostr and drive home the point of why it’s important.
https://x.com/unconfiscatable/status/1728504786637504572
Agreed. The nature of replaceable lists lacking version reconciliation in a decentralized environment makes for a major risk of data loss or clobbering. I’ve been stewing on the idea that old replaceable list events should not be deleted implicitly, and that there should be an additional tag for every new list event that indicates the event id of the old event it intends to “replace”. If a client encounters a series of events for the same list, it should allow the user to determine how to reconcile if there’s branches in version history. I’ll put out a PR to NIP-01 to see what people think but I imagine it could be controversial as it adds a layer of complexity.
This is the way. No shame in charging for nice additional features on top of free basic features. People will find value in them and be willing to pay.
Anecdotally, I occasionally miss notes on Damus but I would say it’s more frequent than rarely. Usually missing the root note when I see a reply. Probably because other clients don’t broadcast the root. Gossip model (or relay rendezvous, as Mike calls it) in all clients would be great.
Time dilation is wild. I remember having my mind blown when studying it in university way back when.
“The faster you travel, the slower time will pass for you. The effect is small – take a transatlantic flight from London to New York and your watch will be a ten-millionth of a second behind one left on the ground – but nonetheless you'll have aged a fraction more slowly than if you'd stayed at home.”
https://www.bbc.com/future/article/20231117-time-dilation-planes-einstein-relativity-black-holes
Plebstr is also closed source. I think the argument is towards monetization and raising getting funding. But I agree, the nature of the protocol demands for open source and transparency. People need to know what their keys are being used for.
Spent many hours on this NIP-52 calendar events PR for Nostr SDK iOS, but I’m really happy to be implementing it. It’s been a wild few months going from authoring the NIP to actually implementing it in code.
https://github.com/nostr-sdk/nostr-sdk-ios/pull/108
There’s a few things that I think are missing:
- participants on the calendar level, not just the calendar event level. e.g. invite participants to the Nostrasia calendar, but not necessarily need to invite everyone to each conference session.
- not sure if having participant lists on the calendar or calendar event itself is the best place for it at scale. I’m worried about excessively large participant lists bogging down the main purpose of the kind - to describe the actual calendar event, not necessarily who is attending. Think about a 1000 person conference like Nostrasia.
- allow multiple locations instead of just one. In the office setting, you can have the meeting in multiple meeting rooms in different offices. At Nostrasia, the sessions were live in Tokyo but streaming in the Hong Kong venue.
- the top-level “content” field should not be optional (but it can be empty). NIP-01 appears to require it.
Admittedly, I have some tunnel vision as I haven’t actually put it into any user-facing client, just the iOS SDK. I did ask @zach the same question for @Flockstr and he said the NIP worked well for him.
@fiatjaf Were there some recent changes to njump.me? I’m getting “error on line 1 at column 2: StartTag: invalid element name” on a few nprofile and npub pages, including my own.
Oddbean new post about login | logout
Notes by tyiu | export