Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nostr.how – A Complete Guide to Nostr

nostr.how

Post reply on HN
Print view View original

41–50 of 140 posts

Re: Nostr.how – A Complete Guide to Nostr

#41

Post by libraryatnight »

lazzlazzlazz wrote: post #10
lapcat wrote: post #8

My previous Mastodon instance (mstdn.plus) broke this week, the administrator MIA, leaving 4500 active users including myself unable to move their followers to new instances or even archive their data: https://lapcatsoftware.com/articles/mastodon.html

Mastodon is essentially centralized — you just pick who you trust with full centralized authority before they have a change of heart, fail, begin rent collecting, whatever. Nobody seems to understand how difficult it is to make a system that can guarantee its neutrality within the protocol. (Sorry HN: it requires crypto.)

It may need cryptography. I think the majority of HN likes cryptography. When you say crypto, and apologize for it, I assume you mean the stupid coins and all the nonsense that comes with that group of fools, and that is not required.

Re: Nostr.how – A Complete Guide to Nostr

#42

Post by erskingardner »

legutierr wrote: post #2

If anyone is interested in trying out Nostr, I would recommend downloading Damus, the iOS client that’s currently available. https://apps.apple.com/us/app/damus/id1628663131 It’s not perfect, but it feels a lot like the Twitter iOS client, and gives you an idea of what Nostr can become.

Agreed. Damus is great. Iris.to is probably the easiest to use web client.

Re: Nostr.how – A Complete Guide to Nostr

#43

Post by immibis »

lazzlazzlazz wrote: post #10
lapcat wrote: post #8

My previous Mastodon instance (mstdn.plus) broke this week, the administrator MIA, leaving 4500 active users including myself unable to move their followers to new instances or even archive their data: https://lapcatsoftware.com/articles/mastodon.html

Mastodon is essentially centralized — you just pick who you trust with full centralized authority before they have a change of heart, fail, begin rent collecting, whatever. Nobody seems to understand how difficult it is to make a system that can guarantee its neutrality within the protocol. (Sorry HN: it requires crypto.)

This is why I installed my own Pleroma instance (immibis@social.immibis.com). It's not very difficult. I hear Mastodon is much more painful to install.

Re: Nostr.how – A Complete Guide to Nostr

#44

Post by immibis »

gray_charger wrote: post #7
class4behavior wrote: post #4

The whole premise of Nostr is that you consider your access point hostile, yet its provider is still offering one. That contradiction just incentivizes bad and toxic actors to participate and dominate this network. That's why, it seems, the developers actively conflate what one would expect from a private communication platform and a social media platform. But this isn't an alternative to Mastodon or Twitter, it's an…

I think centralized moderation is the problem with social media servers. Users should be the ones to control their own moderation. See a post you don't like? Hide the post. Don't like any posts from a particular user? Block the user. It's not difficult to do and if users are really only following friends and famous accounts (celebrities, bots, news, etc.) they won't experience much spam anyway. I think the real issue…

You would think that at first glance, but it's short-sighted. Experiment: Turn off your email's spam filter for a month.

Re: Nostr.how – A Complete Guide to Nostr

#45

Post by drexlspivey »

cactusplant7374 wrote: post #32

I was surprised when I learned it's not really related to Bitcoin. I didn't think Jack would support something that isn't adjacent.

It’s not really related to Bitcoin but it uses the same crypto primitives, schnorr signatures, secp256k1 elliptic curve etc, if you are building for nostr you can reuse the numerous bitcoin libraries. As a result it’s trivial to implement support for lightning network payments.

Re: Nostr.how – A Complete Guide to Nostr

#46

Post by jasonjmcghee »

erskingardner wrote: post #40

I’m the dev behind Nostr.how. I’d love to hear your feedback on how I can make the site more clear/better at explaining Nostr. That said, while I am not the core dev on the protocol or any client/relay it’s been awesome to see the points of confusion from the comments and questions here. Keep them coming - great fodder for new guides.

Search doesn't seem to work for me. There are always no results.

Re: Nostr.how – A Complete Guide to Nostr

#48

Post by fiatjaf »

Zamicol wrote: post #37
evv wrote: post #36

Earlier quoted context omitted.

> - The plan appears that user names are delegated to the centralized DNS system ( https://github.com/nostr-protocol/nips/blob/master/05.md ) DNS is not centralized, it is distributed. A name server can delegate authority to other servers. Every nation has their own, which I consider sufficient decentralization. (Although it does rely on IANA to list addresses of root name servers, which is perhaps the centralization…

DNS is centrally controlled by ICANN. There are alternatives like ENS. I don't mind Nostr just simply having its own system.

ENS can definitely be used. The DNS thing is just one hacky way to put meaningful names on keys, but other hacky ways are not excluded.

Re: Nostr.how – A Complete Guide to Nostr

#50

Post by Aeolun »

lapcat wrote: post #15
pointlessone wrote: post #13

I read everything there and all NIPs (they look like underage RFCs, but also drunk) and I'm a little confused. - The protocol doesn't define a transport but seem to use WebSockets. How does it handle poor/dropping connections? Does it allow usage of alternate transport protocols? - Messages are defined as JSON but doesn't use much of its structure anyway. Some fields are just arrays of values. And even then some part…

> It's unclear how to preserve/port data. A relay is supposed to keep (or not) messages and the client is supposed to send messages to multiple relays. But what happens when a relay goes down? Can a client send messages to a new relay? Should the client keep all messages just for such a case? https://www.nostr.how/relays "If all the relays that you have used in the past go offline, all your posts will be unretrievabl…

I’m really confused as to why they’re called relays. As it is now they’re not relaying anything. They’re just a default server/client.
Post reply on HN