nips
Invidious
nips | Invidious | |
---|---|---|
70 | 422 | |
2,096 | 14,973 | |
1.6% | 3.2% | |
9.5 | 9.5 | |
2 days ago | 6 days ago | |
Crystal | ||
- | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nips
-
Why isn't Bluesky a peer-to-peer network?
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
-
Today I'm launching Flare, a video sharing site built on Nostr Like YouTube
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.
-
RSS can be used to distribute all sorts of information
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
-
Ask HN: What is the next great online community?
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.
-
Nostr: A Decentralized Messaging Protocol
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!
- Why even let users set their own passwords?
-
Where does iris upload it's images?
Take a look at NIP-23: Long-form Content https://github.com/nostr-protocol/nips/blob/master/23.md .
- Nostr NIP-05 : Mapping Nostr keys to DNS-based internet identifiers
- Greetings! I'm here to tell you about Nostr, a decentralized and censorship resistant social communication protocol that has recently added protocol level support for Moderated Communities. Developers are actively building this on Nostr and would love your help and support. Let us know what you want
- I happened to learn about Nostr by chance.
Invidious
- Google Broke Invidious Again
-
Mobile Ad Blocker Will No Longer Stop YouTube's Ads
Youtube seems to be doing some A/B testing with the comment system which has made proxies like Invidious and yt-dlp/Newpipe unable to load comments. There is a patch for Invidious [1] which solves this problem but it is not in master yet. I tested it on my own instance and it does solve the problem.
[1] https://github.com/iv-org/invidious/pull/4576
- YouTube: Google has found a way to break Invidious
-
Google fights Invidious (a privacy YouTube Front end)
BTW, I don't understand the workaround: https://github.com/iv-org/invidious/pull/4552/files
Which was taken from here: https://github.com/LuanRT/YouTube.js/pull/624
Could anybody explain it to me?
- Google Ordered to Identify Who Watched Certain YouTube Videos
-
YouTube is loading slower for users with ad blockers yet again
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
-
YouTube begins new wave of slowdowns for users with ad blockers enabled
Going to drop this here for others who haven't heard of it https://invidious.io/
Now, how do we fix this? YouTube's ad model sucks. Their algorithm sucks. Their front page sucks. They've captured a bunch of creators though so often YouTube is the only place you can find someone.
I want those creators to benefit from me viewing their videos. I want the fact that I view a video and like it to help other people find that video in their recommendations. I want an algorithm that shows me things that are interesting and relevant not one that promotes the spammiest and most ad heavy videos that barely have anything to do with my watch history.
Having an alternative front end is nice but I don't want to rob YouTube of the money they spend on hosting the videos.
So, how do we do this?
Peer to peer fails when there is little interest in something or when most people leech and it sucks for archiving old content.
Hosting it all in one place is super expensive and hard for a small group to manage without turning into YouTube.
Maybe we could find a way for the creators to host their own content and get paid when people view it while being part of a large federated network for easy discoverability?
Please list any projects you know of, I'm sure there are a lot of people here who would be willing to contribute or donate.
- Crystal 1.11.0 Is Released
- YouTube is trying to block Invidious
-
Reviving decade-old Macs with antiX and MX Linux (2022)
Sometimes a half-solution will do, like Invidious or Piped.
[0] https://invidious.io/
[1] https://github.com/TeamPiped/Piped
What are some alternatives?
simplex-chat - SimpleX - the first messaging network operating without user identifiers of any kind - 100% private by design! iOS, Android and desktop apps 📱!
Piped - An alternative privacy-friendly YouTube frontend which is efficient by design.
gotosocial - Fast, fun, small ActivityPub server.
NewPipe - A libre lightweight streaming front-end for Android.
nostr-emitter - An end-to-end group encrypted event emitter, built on the Nostr protocol.
FreeTube - An Open Source YouTube app for privacy
nostream - A Nostr Relay written in TypeScript
nitter - Alternative Twitter front-end
awesome-nostr - nostr.net - awesome-nostr is a collection of projects and resources built on nostr to help developers and users find new things
SponsorBlock - Skip YouTube video sponsors (browser extension)
smtp-nostr-gateway - SMTP to Nostr NIP-04 Gateway
libreddit - Private front-end for Reddit