People look at this and see nothing wrong with using DNS-based image urls or url-based relay hints inside our posts. They are never going to come after our content, right? Riiight?
OpenSecret's avatar OpenSecret
PSA: The functionality of multiple Fedimint federations is significantly degraded due to severe DNS issues. It seems to be the case that some federation guardians have an XYZ domain that the DNS registrar has taken over. Freedom One and Bitcoin Principals appear to have one guardian offline due to this. Unfortunately, despite the server and keys for these guardians being intact, there is no way for the DNS of a guardian to be swapped out after the fact. We became aware of this issue last week and then became aware that multiple federations are experiencing this: https://github.com/fedimint/fedimint/issues/5482/ Given the critical state of these federations, with one guardian out of four being permanently offline, it's essential that if you have funds in these federations, you should withdraw them immediately. Unfortunately, we're unaware of other public federations, so you must withdraw to another lightning or on-chain wallet. From our experiences, intermittent/connectivity issues can occur with guardians, and this may result in errors if not all three remaining guardians are consistently online. No other guardian of these federations has XYZ or other domains like it. So, if you're having issues, please try again later. Unfortunately, not much can be done on the Mutiny side, so we're removing the federation setup flow in the UI as a first step. Sorry for the inconvenience.
View quoted note →

Replies (103)

How else do you get a name to your link? But before you allow the Nostr FUD to overtake your imagination, know that DNS is actually decentralized. This includes a bunch of dot servers and a bunch of TLDs owned and cared for by multiple entities, jurisdictions and countries. 🐢🐾🫑
DNS is the first thing countries do when they need to take you down. You just need to give them an excuse and you will lose nostr.build forever. Then none of our links inside our notes will work anymore. In many cases, countries don't even need to go through court to get you offline. I have seen many domains being lost (redirected) in my lifetime. It's super easy for them to go through.
Then don’t use a single domain that relies on the same country. Same as a fucking electric grid. Same as anything for that matter. Why do you think big providers have their NS servers in 3-5 different jurisdictions? Did we learn anything from not keeping your eggs in the same basket? 🐢🐾🀯🀯🀯
I’d be more concerned about registrars. There a shit ton of crap ones out there. Still using Gandi myself. But I’d love to hear what others use in a privacy mindset. I know they were acquired and may not be the company they once were. They still beat the hell out of most IMO.
Two of my relays require DNS, and essentially all the shared images and videos I see. Nostr itself can work without DNS (as long as Tor is up, for my Onion relays), but man, think of the memes? The memes must flow. And whoever controls the memes, controls the universe.
Default avatar
nobody 1 year ago
I might expose my relay on a raw IP address to add another option, if there is interest in such a thing.
True: ThePirateBay, LibGen and SciHub show it can be done, with enough lawyers and money, and customers engaged enough to follow you around as the Feds play whack-a-mole. Would be reassuring to have other options, though.
Wouldn't it be possible to use nostr itself as a DNS alternative? Like, create an identity as "static name" and link your public IP to it's profile, done! Or something like that, idk shit about DNS, most of the time I've no idea what I'm doing.
"A little yes", as my old boss used to say. 95% of the world lives outside the reach of the First Amendment, and 95% of internet users use their ISPs' regulated DNS server. Countries like Australia and France DNS-poison as a matter of course. 1.1.1.1 and 8.8.8.8 are win, but outside our circles they are little used...
Good luck teaching my mum how to setup custom DNS resolver on her own. (I've tried. And she has two university degrees, and cares about freedom.) Nostr.build will survive a DNS takedown, like ThePirateBay did. But that's only possible with a tech-savvy and motivated core audience.
The best way out is to merge all media server providers in Nostr in a single pool and users pay by usage, not by storage. With that, we reduce the race to the bottom on image services while also allowing user to choose a trusted provider to serve as proxy for all images and videos. Meaning the receiving user chooses the media server, not the sender.
Yes I think we should have an event kind that allows somebody to cryptographically bind an IP address and port (SocketAddr) to a relay's keypair. But we would need: 1) Relays to have keypairs 2) Nostr to reference relays by keypair instead of by url 3) A means of distributing the binding event (because of the chicken-and-egg problem) maybe just blast them, or maybe a DHT. It's a great idea for nostr2, so nostr2 won't be dependent on DNS and shoudn't need to be dependent on SSL certificates issued by CAs that nobody really trusts anyways.
@Vitor Pamplona If you are using the Brave Browser, centralized DNS is not a problem anymore. To get a STATIC content, just type on the url bar: ipfs://[hash-here] To get a DYNAMIC content, just type on the url bar: ipns://[pubkey-here] The great news about this is that we can use nostr pubkey for this self-signed certificate!!!!
I am not ignoring. The nodes can still implement their policies individually. The two most important parts to me are: - give the receiving user the power to choose. - move your revenue model away from a race to the bottom In that framework, CSAM can be managed by both storage providers and proxy providers separately. Given resources, everything is possible.
That’s the catch, given resources. The problem is, there is a lot of fragmentation in the nostr world, so no one idea gets the resources it needs to get off the ground. It’s like playing wack-a-mole with different half baked standard that are forgotten the moment they are merged. I would love to have more abstraction layers on top of media to make it reliable and resilient, but most of the devs move on onto the next shiny thing, e.g., blossom, IPFS, <next greatest thing after sliced bread> πŸΆπŸΎπŸ€·β€β™‚οΈ
This is an actual problem. We need nostr-addresses, a la tor hidden addresses. No reliance on traditional DNS. Make our own. This is what I meant before about hosting "nostr-based websites". I woild query a relay, and the relay would check a routing table of sorts, and send me the correct way.
Vitor Pamplona's avatar Vitor Pamplona
People look at this and see nothing wrong with using DNS-based image urls or url-based relay hints inside our posts. They are never going to come after our content, right? Riiight? View quoted note β†’
View quoted note →
For example, we put in an OpenSats application over 7 months ago asking for resources to help with CSAM, building out a decentralized/Blossom type NIP, integration with Primal, searchable GIFs and images, etc. Have provided multiple plans with milestones.. They’ve asked us to reduce our scope a couple times and still haven’t given us any confirmation of support, and have been radio silent for months now.. All while the BTC price is exploding, and Jack is donating millions.. And we are providing the majority of hosting for nostr! Imagine a smaller or not so well known project.. Apparently you have to be part of the β€˜in crowd’ to get any significant support from OS, FiatJaf, etc. Fishcake and I don’t have enough Twitter followers.. Isn’t there a meme for that? 🀷🏼
I don't think it's about who you know or your amount of reach. I don't believe that for one second. OpenSats seems to mostly fund developers and not so much development of specific projects. There may be a couple outliers here, but the majority of them seem to be funding existing work, not funding companies or future plans. i.e. I built this cool thing and I'd love to continue to do this. I need money to continue. I haven't seen your plans, but based on what they seem to fund and speaking with some board members in an information gathering way, it sounds like reduction of scope seems par for the course. Maybe reduce to bare minimum and both you and Fishcake both apply individually for your work?
SORRY FOR THE POOR COMMS. WE HAVE AN INSANE AMOUNT OF APPS TO SORT THROUGH AND TRYING OUR BEST TO SCALE OPS AS QUICKLY AS POSSIBLE. WILL LOOK INTO YOURS PERSONALLY.
> Imagine a smaller or not so well known project.. Apparently you have to be part of the β€˜in crowd’ to get any significant support from OS, FiatJaf, etc. Fishcake and I don’t have enough Twitter followers.. I don’t think that this is the problem. There are plenty of grantees that do not have much reach. I get that this is frustrating, but throwing around claims like this doesn’t help either. I hope that they get back in touch to clear things up.
It also helps that if your a registered user it builds a profile of your uploads on my server. So I can scroll my profile for the meme I'm looking for.
> We are providing the majority of hosting for nostr There's your problem. Are you building a web hosting company, or a solution to censorship-resistant content hosting? It seems more like the former, based on your focus on platform-specific features like content moderation and image search. Don't get me wrong, nostr.build is a great service to nostr in these early days, but what if a state actor comes to you and asks you to take something down? You'll do it, as would I. Making nostr.build's source code FOSS doesn't really solve that problem on its own. NIP 96 is a great start to creating an open solution, but much of the spec is concerned with accommodating the needs of image hosts wrt image optimization and transformation. Also, in practice, files are usually referred to by url, not hash. People are excited about blossom because it forces users to refer to files by hash, and doesn't include server-side transforms. It's just a more purist architecture, that makes the benefits of content-addressability clear. NIP 96 isn't necessarily broken, but conventions around its use need to change. Also, serving a transformed file in response to an `ox` prevents users from verifying that the file is authentic, which breaks the guarantees content-addressing gets you. Pushing content replication based on hash does of course conflict with content moderation for CSAM, which is a great service, and important to the health of nostr for users, operators, and nostr's public image. But it's inherently centralizing. I don't know what the solution to that problem is. Here's what I would personally like to see from someone focused on image hosting: - More robust content-addressing, including a referentially transparent mapping between hash and returned file, and better conventions for using these hashes in nostr notes. - A story for replication of content between servers, including self-hosted ones. Also better discovery of where a particular file is hosted. Blossom has this, in theory if not in practice. - Decentralized/redundant CSAM scanning, and propagation of reports across servers (without making the reports public, somehow? I know it's extremely hard to manage hash tables in a way that doesn't allow attackers to circumvent them, see https://securitycryptographywhatever.com/2021/08/27/apple-s-csam-detection-with-matthew-green/) Just my own personal 2 sats.
More than willing to come and work with @OpenSats if there are positions available. And since a lot of what I do is Operating Models and Process Improvement. I can add value in improving efficiencies and scalling. πŸ€™πŸ»
Why should anyone use nostr.build vs any other image host? I think people are just using you a lot because nostr is in your url. Maybe you should try to provide a unique service, and then charge for it.
I think the more likely threat is for content hosting companies like nostr.build to start posting banner ads &/or trackers over everyone's memes. As far as state level attacks It would be far more difficult to censor if we all just hosted on our own domains. Kind of like removing one raccoon in your attic versus an entire termite infestation. A custom domain option from companies like @nostr.build would be something worth paying for once people realize the value in "owning the path" to their content. It would also protect consumers from outrageous rate hikes because they would be able to migrate their content and keep past notes true. Example: image
Kim's avatar
Kim 1 year ago
Last chance, follow me to follow you back . I’m serious
We’ve been building this long before blossom… it’s coming soon, quite literally years in the making now. @Sirius is with us too. You should all take Merkle DAGs more seriously and understand that files need to be chunked in distributed networks. I hope the amazing experience of running a @HORNETS server will open your eyes. Sometimes feeling it is the only answer.
We are ok, please keep to your standard review process. There are other less-known projects that need more help. I just wanted to highlight some of the challenges with timely resources when working across nostr platforms..
Really appreciate the thorough feedback. Most everything has just evolved this way, not necessarily how we planned. Agree we need to innovate further, become more decentralized, but our resources are currently maxed out and that stuff requires a ton more dev/support/legal since their currently isn’t a solution.. We do have a few ideas how to move forward..
Hypnagog's avatar
Hypnagog 1 year ago
Would the issue be more related to possible censorship ? Csam is the excuse given by governments to pass censorship laws.
when you put it that way it seems like a bigger challenge then just shitposting, zapping, and hodling
↑