nips VS nitter

I'm interested in this too. While I note the [slightly chaotic] plethora of NIPs[0], and many of them look blockchainy, NIP-01 is looks ultra pragmatic and simple, and is the only one that is required to be implemented, AFAIK.

  [0] https://github.com/nostr-protocol/nips

For you and others following. Common in early nostr apps. The web-extension spec is defined in https://github.com/nostr-protocol/nips/blob/master/07.md. Most apps check for window.nostr, then fail silently when it's missing or blocked. There are also some popular extensions in that list.

https://github.com/nostr-protocol/nips/blob/master/65.md

The TLDR is that when a Nostr client supports NIP-65, it broadcasts to all known relays (which is continually updated/expanded) the list of relays that User A posts their stuff to.

This means that as long as User B is connected to at least one of those "all known relays", their client now knows what relays User A posts their stuff to, and will specifically fetch things from those relays when it needs to load User A's things.

It's essentially the Nostr take on the Gossip protocol: https://en.wikipedia.org/wiki/Gossip_protocol

I think your best bet here is Nostr (Notes and Other Stuff Transmitted by Relays): https://nostr.com https://github.com/nostr-protocol/nostr

Nostr isn't a federated platform like Mastodon or Lemmy, it's more similar to the AT protocol created by Bluesky, whilst being far simpler to understand and write apps using it. The nostr protocol is defined by a series of NIPs (Nostr implementation possibilites https://github.com/nostr-protocol/nips), the most basic of which can be implemented in a client or a relay in 50-100 lines of code in any modern programming language.

Each user runs a client, anyone can write a relay or run any of hundreds of existing implementations, both clients and relays can choose to support a number of NIPs. Users have a public-private keypair, and distribute notes to relays signed with their private key, which are verified by relays. Clients subscribe via websockets to any number of relays (I usually have 20-30), and receive notes from all users on those relays' databases, or filtered by the public keys of the users you're following. Relays for the most part don't communicate with each other. If you're ever blocked or banned from a relay, you'll still be able to have your notes seen as long as you have at least one relay in common with anyone who wants to see them. I run my own as well for extra resiliency.

At the moment there's ~50 standardised NIPs, which add features like likes, zaps (bitcoin tips for notes), user status, post expiration, mentions, search, DMs, and public chats. Nearly all of these are supported by popular clients and relays. While nostr is primarily used for social media at the moment, it's already possible to build upon as a protocol for pretty much any online service.

The total active user count on most public relays I'd estimate is somewhere around 500k to a million, though the nature of the protocol makes it impossible to estimate its true size. The perceived community on most relays before following anyone frankly can get pretty cancerous, mainly due to a lot of clients sorting notes by new by default, so I can only hope to high heaven it'll improve as it grows.

Though like any new non-centralised platform, it's more difficult to get started on for most non-technical users as they have to pick one of hundreds of clients to install, and requires caution to never leak your private key and be very wary of which clients you trust it with.

There is no "zaps balance". Zaps are just receipts of lightning payments.

The basic idea is that a lightning node will detect when the invoice with a nostr note inside is paid, and then send the receipt to nostr as a nostr note, with the original bolt11 invoice inside with the signature from the user who sent the zap.

It's all describe by NIP-57, a spec I put together to support this:

https://github.com/nostr-protocol/nips/blob/master/57.md

I was working on c-lightning at the time and I thought it would be really cool to replace the "like" button with an instant bitcoin micro-payment. I think it worked out quite well! There are many sites utilizing zaps in all aspects of the protocol, such as a decentralized market for AI job requests (data vending machines), zapgoals and zap fundraisers. All built on this note type. protocol synergy!

Take a look at NIP-23: Long-form Content https://github.com/nostr-protocol/nips/blob/master/23.md .

Don't use Youtube without going through a proxy like Invidious [1] or Newpipe

Don't use {site} Search without going through a proxy like SearxNG [2]

Don't use TwiXXer without going through a proxy like Nitter - this has gotten more difficult lately but it still works as long as you feed the daemon some registered accounts. Video does not work at the moment but that seems to be fixable.

Don't use Reddit without going through a proxy like libreddit [4]

Start noticing the pattern? Maybe it is time to start producing promotional posters:

The only thing to come between you and ADS could be a proxy / ADS. I'ts just not worth the risk

ADS / New rules for a sane net / Sane net protects you, your partner and your community

A proxy here and a filter there, ADS nowhere

The more you tighten your grip, ${site}, the more viewers will slip through your fingers

[1] https://github.com/iv-org/invidious

[2] https://github.com/searxng/searxng

[3] https://github.com/zedeus/nitter

[4] https://github.com/libreddit/libreddit

https://nitter.esmailelbob.xyz/liuzhuang1234/status/17601959...

(bit of trial and error from https://github.com/zedeus/nitter/wiki/Instances)

I assume this is why Nitter got slammed and is on the verge of breaking.

https://github.com/zedeus/nitter/issues/1154

The creator of the project left this comment an hour ago:

https://github.com/zedeus/nitter/issues/1155#issuecomment-19...

(HN removed the deep link to the specific comment from the title)

Most of the time you can just replace twitter.com with nitter.net or nitter.it but when these instances are down or blocked you can use other instances listed here: https://github.com/zedeus/nitter/wiki/Instances

But as the other commenter said Libredirect is the way to go: https://libredirect.github.io/

Use a Youtube proxy like Invidious [1], problem solved and you get to subscribe to channels without telling the Beast about your interests. Add Sponsorblock (which supports Invidious) to get rid of any in-stream advertising which remains and you'll be transported back to those hallowed times of yore when men were men, women were women and advertising was something you found in newspapers. Youtube will try to make this harder just like Xitter is trying to make it harder to use proxies like Nitter [2].

[1] https://github.com/iv-org/invidious

[2] https://github.com/zedeus/nitter

njal.la restored nitter.net, and replied with their reasons: https://github.com/zedeus/nitter/issues/1150#issuecomment-18...

tbh I can totally understand why they acted this way.