I’m watching on the ABC YouTube stream, so i don’t know if there is a local broadcast. Normally all public events yes there are interpreters normally for public events in NZ, but I don’t actually remember there being sign language interpreters at NZ political debates.
Indirectly, they’re still commonwealth countries with the King of England as the head of state… it’s the UK which is still our colonial power, even if there’s lots of autonomy. So it’s the UK’s relationship to the US… so by a second degree…sure…
The advantage of relying on a centralized relay caching proxy is that some things are faster but the downside is you’ve got a single point of failure for all users of the decentralized app.
I think we need to do work to reduce the need of these centralized caching servers. Or make them more horizontally scalable as part of the protocol instead of a custom overlay.
Looks like cohost.org is shutting down. They’re actually bringing in a lot of money each month with a high % of users supporting as paid members. But their expenses are really high for the kind of site it is.
Anyway this is what happens to a community that builds itself on closed source centralized platforms. When the maintainers decide to give up the users and community have no say.
https://cohost.org/staff/post/7611443-cohost-to-shut-down
This is great. Now let’s get the iOS apps onboard too. I’ve been talking to the guardian project and their mobile dev on the iOS side about working with us to get Nos and other Nostr apps to have similar seamless tor support.
nostr:note1n82a3q2d7fvk8em6350v027092my90p6zahq8yx52zjmw9aghpfs9p7wwy
Awesome to see this getting updated again and it’s nice to see all the projects you’ve supported. That kind of transparency is all to rare for philanthropists. Lots of good worthy projects too.
Takes forever to load, doesn’t load reliably, loses data, is very slow to run. And all for a bunch of encrypted stuff which makes the software hard to build and optimize and wasn’t needed for my use case. It’s slow buggy software. Browsers aren’t good at the encryption that cryptpad tries to do.
This is really good stuff, we need to take this opportunity to build better resilience in to the Nostr network. I think the paid relays aren’t going to be enough, they make Nostr work for existing users but not new ones. I think WOT are more accessible, but we need something which works for the new users.
Maybe it’s new user follow lists like Bluesky starter packs + WOT relays…
So much of our discussion about trust, safety, and governance of Nostr is related to content and political speech. But there’s so many more issues we’re going to face and we need to think about. If you care about this stuff, read this paper: https://tsjournal.org/index.php/jots/article/view/171
Yeah, just like we need ways to find a bunch of content which interests people. So we answer the question, is this a place where i feel comfortable.
The new user experience is really different than what we all get as existing users on Nostr.
If we want Nostr to truly protect privacy and resist censorship—like when X faced a government ban—we need to stop relying on relays with known IPs or domain names.
We need encrypted traffic between clients and servers by default. That means Tor (and networks like I2P and Nym) should just work right out of the box, ideally without leaving the mixnet where traffic could be exposed at the exit node.
💡 A lot of relay operators are already running Tor onion services, which is awesome—but we need to make them easier to discover and use. If a public relay becomes unavailable, we should be able to switch to the Onion service version seamlessly.
What do we need to do to make this happen? First, it’s about getting Nostr relay software to publish the Onion address when it’s set up. Then, it’s about getting clients to handle alternative transports like Tor or I2P natively, letting users choose between IP (TCP/IP), Tor, or other options.
We could also explore mapping DNS records to onion addresses or including the info in HTTP headers. But maybe the most straightforward approach is extending NIP-11 to include alternate transport details so that everything's baked into the protocol.
What do you all think? How can we push this forward? Let’s brainstorm and figure out the best way to support these privacy-preserving networks and keep Nostr resilient. I think we need Tor support in native clients where users can turn it on with a single click. Or maybe even have it attempt Tor as a fallback when the normal way of connecting fails.
This isn’t a big change current relay info ospec here: NIP-11 https://github.com/nostr-protocol/nips/blob/master/11.md
I mean sure but we’re talking about nostr tor that doesn’t use exit nodes at all and running things at known ip addresses doesn’t exactly help with either privacy or censorship resistance if your adversary is a nation state. But you do you.
I know people keep proposing alternative dns systems for Nostr, but I don’t see much value. If relays can easily be replicated and accessible via Tor, then is it really a big deal that the domain name the relay is using disppears.
It seems to me folks advocating from alternative dns systems are all in to it because they want to collect the domain name taxes instead of it going to ICANN. Feels like rent seeking to me.
ICANN’s not perfect, but it’s an example of internet governance which has done the minimal thing needed to keep nation states away from the internet. Even the way DNS seizures are tied to countries and not across the entire system, lose a .af domain and you can register .co.
And there’s a decent process by which you’re not losing your domain names when the dns keys are lost the way a blockchain dns system would happen.
So if somebody figures it out, gets all of Nostr to adopt it, then sure, if we need to we’ll support it, because why not, but this seems like such a silly thing to focus on.
I’m saying clients should start adding language tags to notes when they get published so clients could just request posts with a specific language from relays without having to do that parsing client side.
I don’t buy the language bubble thing, right now we’re not cultivating users beyond English because we make it hard for people to find non-English language content.
Penso che sia brutto comunicare in più lingue, ma sarebbe anche utile filtrare per lingua in quanto puoi filtrare in molti altri modi per scegliere cosa vuoi vedere e con chi vuoi parlare.
Yeah, I’ve thought about standing up one for that, which is fine, and useful. But when we need cloud bots for Nostr to work, it’s a form of centralization. So while I’m happy to stand up a language labeling bot, hopefully it’s not so controversial as @Tagr-bot, it’s something I’d prefer clients did themselves.
Similarly i’ve got notes for an update for NIP-02 so we can easily add tag differences in the list, making ‘new follows’ something clients can get without having to have a network bot crawling the nostrverse the way Nos and Primal do. I’m hoping to also update it so we have version history of the profile and lists events similar to how you’ve got edit history on other events @Vitor Pamplona.
One way to help Nostr grow would to make it easier to find content in languages you speak. Damus and others have nifty ‘translate this note’ features but there’s something different from the way people speak in their own langauge.
Nostr already has the nips for this: https://github.com/nostr-protocol/nips/blob/master/32.md
We can easily add tags to events which would let clients request only events in a specific language, or set of languages. But do any clients write out the language tag and do any use it in the UI for helping people discover content in their own langauge?
I’m thinking of this because most Brazilians prefer to talk to people in their own language, Brazilian Portuguese (yes it’s different written language than Portuguese du Portugal).
It’d be so cool to have on boarding which saw that a user is in Brazil, or has their device set to pt-br and then show them primarily content in their own language. This is also true of Thai, Japanese, and Chinese which also have big sets of Nostr users. The latter two seem to use custom local Nostr clients to avoid this problem. I’m not sure what Thai users do. I know that although I speak Spanish, and there are lots of hispanohablantes on Nostr, we mostly seem to write in English. That’s because it’s hard to filter out by language community except for who you choose to put in your contact list.
So, what Nostr clients do this well? How do get clients writing these language tags in their posts and make it so clients then display / use them for users.
Sure, my point was more we can use both he language and dialect tags to help people find the content they’re most interested in engaging with.
My Portuguese isn’t really good enough to distinguish except to know that Brazilian Portuguese sounds “normal” to me and Portuguese do Portugal sounds a little bit weird. ;-D
I mean folks are swimming in the ocean and it’s 15c/59f out. It’s not exactly warm. The water is closer to 12c/53f!
But it is a bright sunny day. And kiwis are used to colder temperatures.
London is warmer right now than Wellington.
We need an instance of the nostr blogging software which highlights non-bitcoin content. I keep talking to people about how amazing and powerful Nostr is as an open Medium.com and showing them YakiHonne, highlighter, and habla. They get turned off not by the apps, design, idea of a protocol, or anything like that. They get turned off because all they see are bitcoin posts. They think, this isn’t for me.
It’s like porn on Twitter, there is so much of it, but you only find the porn if you’re looking for it. We need at least one nostr blogging app which can highlight other content with lots of diverse audiences. That way we can get them on board without them thinking, this place is not for me.
Yeah I agree. We’ve got pieces to make it all work but they’re not put together well I a way that works for users and creators.
And for my trolls out there, the bitcoin payments part via zaps, lightning/cashu etc is fine, it’s the overwhelming bitcoin content that drives people away.
Yes but we don’t make it easy to discover, use, and tweak the nostr apps to use these topical relays. There is nothing like Bluesky starter packs. We could do it, we have all the components, but we don’t make it easy and clear.
Yeah we will need ways to filter content and prevent abuse. What we needed is examples of abuse and the desire to set limits that are needed. Reply Guy is great because there is nothing political or useful about the content.
@Rif'at Ahdi R the @Tagr-bot works two ways. First it looks at posts that Nos users might see and checks that with OpenAI’s moderation tool. It also accepts encrypted reports from Nos users which are reviewed by people and reports are issued. It works for the scale we’ve got. I would love to be able to use the Bluesky labeler app Ozone but with many labeling bots and different labelers on nostr.
Looks like Bluesky is getting a huge surge from Brazil blocking Twitter. Reports are 50% of their users joined in the last week.
There is something to be said for being a simple Twitter clone.
Twitter wasn’t banned because it was Twitter it was banned because the company wasn’t following local laws. Were those laws legit? That’s another question. If Bluesky responds to legal and law enforcement requests it’ll be allowed.
I’m not saying it’s good to respond. In a past life I ran a network of websites which constantly was getting police attention, Indymedia.org, and we had the EFF represent us. We moved servers and domain name registration between countries on a regular basis to keep us from having to comply with government attempts at restricting speech.
Until ATproto works as an open network, Bluesky will be more like Twitter in terms of governance than Nostr which is more like BitTorrent.
We setup a filter to stop accepting the events on our relays.
Honestly these attacks are good to have because they’re pretty friendly and let us improve our anti-abuse / anti-spam setup in apps and relays.
@Robert Atkins you’re just now discovering this? It’s been all over the news and social media for a week. :) I envy your ability to be disconnected from the frothy drama.
Oddbean new post about login | logout
Notes by rabble | export