# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 33
# self = https://watcher.sour.is/conv/hab24la
@axodys How do you feel about the fact that Nostr/Damus is really a distributed blockchain-type network though? πŸ€” Does that not bother you? πŸ˜…
@axodys How do you feel about the fact that Nostr/Damus is really a distributed blockchain-type network though? πŸ€” Does that not bother you? πŸ˜…
@axodys How do you feel about the fact that Nostr/Damus is really a distributed blockchain-type network though? πŸ€” Does that not bother you? πŸ˜…
@axodys How do you feel about the fact that Nostr/Damus is really a distributed blockchain-type network though? πŸ€” Does that not bother you? πŸ˜…
@prologic Nostr doesn't have any blockchain features, it just has a community with a lot of crypto bros in it.
@ocdtrekkie β€œit’s not built on the Bitcoin blockchain per se, but most implementations of Nostr support Bitcoin payments over Bitcoin’s Lightning Network.” β€” Non-scholarly source.
@ocdtrekkie β€œI t’s not built on the Bitcoin blockchain per se, but most implementations of Nostr support Bitcoin payments over Bitcoin’s Lightning Network.” β€” Non-scholarly source.
Are you both sure it isn't built on some Web3 distributed networking protocol? πŸ˜…
Are you both sure it isn't built on some Web3 distributed networking protocol? πŸ˜…
Are you both sure it isn't built on some Web3 distributed networking protocol? πŸ˜…
Are you both sure it isn't built on some Web3 distributed networking protocol? πŸ˜…
@prologic Yeah the protocol for it is pretty straightforward. It suggests relays should charge money for their services though, which is likely why Bitcoin payment integration may be common.
@ocdtrekkie And where are your "messages" stored? πŸ˜…
@ocdtrekkie And where are your "messages" stored? πŸ˜…
@ocdtrekkie And where are your "messages" stored? πŸ˜…
@ocdtrekkie And where are your "messages" stored? πŸ˜…
@prologic It's decentralized: You submit a copy of your messages to as many relays as you would like, and people can follow them from as many relays as they like. The relays act as the "server", but your profile isn't tied to any specific one.
Messages are signed with a keypair to verify who they came from. But there's no blockchain strategy in use for them.
@ocdtrekkie Oh okay, so it _really_ is a "dumb relay". A bit like the saltyd broker design? πŸ€”
@ocdtrekkie Oh okay, so it _really_ is a "dumb relay". A bit like the saltyd broker design? πŸ€”
@ocdtrekkie Oh okay, so it _really_ is a "dumb relay". A bit like the saltyd broker design? πŸ€”
@ocdtrekkie Oh okay, so it _really_ is a "dumb relay". A bit like the saltyd broker design? πŸ€”
@prologic It literally calls itself dumb here: https://github.com/nostr-protocol/nostr (It's a very readable readme)
@ocdtrekkie

> Censorship-resistance
>
> Each user can publish their updates to any number of relays.
> A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

This part of the doc, makes absolutely no sense to me πŸ˜…
@ocdtrekkie

> Censorship-resistance
>
> Each user can publish their updates to any number of relays.
> A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

This part of the doc, makes absolutely no sense to me πŸ˜…
@ocdtrekkie

> Censorship-resistance
>
> Each user can publish their updates to any number of relays.
> A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

This part of the doc, makes absolutely no sense to me πŸ˜…
@ocdtrekkie

> Censorship-resistance
>
> Each user can publish their updates to any number of relays.
> A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

This part of the doc, makes absolutely no sense to me πŸ˜…
Just reading through the FAQ here...

> How do I find relays? What happens if I'm not connected to the same relays someone else is?
>
> You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. > There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

I guess we (Yarn.social) do much better here in terms of reachability. In fact we do way better in terms of discoverability too. Once a pod is spun up, you can pretty much -mention any other Yarn.social user and your post will appear in their timeline instantly thanks to WebMentions πŸ‘Œ
Just reading through the FAQ here...

> How do I find relays? What happens if I'm not connected to the same relays someone else is?
>
> You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. > There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

I guess we (Yarn.social) do much better here in terms of reachability. In fact we do way better in terms of discoverability too. Once a pod is spun up, you can pretty much -mention any other Yarn.social user and your post will appear in their timeline instantly thanks to WebMentions πŸ‘Œ
Just reading through the FAQ here...

> How do I find relays? What happens if I'm not connected to the same relays someone else is?
>
> You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. > There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

I guess we (Yarn.social) do much better here in terms of reachability. In fact we do way better in terms of discoverability too. Once a pod is spun up, you can pretty much -mention any other Yarn.social user and your post will appear in their timeline instantly thanks to WebMentions πŸ‘Œ
Just reading through the FAQ here...

> How do I find relays? What happens if I'm not connected to the same relays someone else is?
>
> You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. > There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

I guess we (Yarn.social) do much better here in terms of reachability. In fact we do way better in terms of discoverability too. Once a pod is spun up, you can pretty much -mention any other Yarn.social user and your post will appear in their timeline instantly thanks to WebMentions πŸ‘Œ
@prologic I mean, I wouldn't want a Russian server to ensure my free speech, but some of the free speech absolutists will take it anywhere they can get it.
@prologic "outside of the protocol for now". that's web3/cryptospeak