#[2] For decentralized live video streaming over websockets see https://vdo.ninja and read https://docs.vdo.ninja

Media files are centrally hosted and easily censorable and have nothing to do with Nostr per se.

Impossible. Nostr is decentralized storage of text blobs, not media.

That there are some text links to centrally hosted media files in those blobs do not make centrally hosted media files part of Nostr.

This protocol will look? Renting a dedicated folder on a central server to deliver files over has nothing do with Nostr protocol.

Cool, but not part of protocol any more than central streaming audio servers.

the grand unified ledger, the centralization posing as decentralization, the monopolist community that poo-poos any suggestion of more than 1 solution to all fiscal concerns and use cases, the thought-stopping catch phrases like "you just don't understand the technology" and "hfsp" in response to legitimate concerns, the fixed pie gambling pool, the 7 transactions per second globally...

Impossible, that's not what Nostr is for. Nostr is for sharing text only in a decentralized way. All media files are centrally hosted and censorable.

Look into clients like https://webtorrent.io for decentralized video hosting and delivery.

Yep, can't integrate live audio via Nostr, nor should you; Notes are meant to be plain text. That type of thing is utterly unsuited to Nostr.

Which is why my mind is blown that people are presenting this deployment of an audio only room as a Nostr based app of some description.

Even if / when you have proper `Sign in with Nostr` SSO, that makes it a Nostr based app like integrating Sign in with Google or Facebook SSO means you have a Google-based or Facebook-based app.

The question was never how much you styled or modified an open source project that has nothing to do with Nostr.

The question was whether you had any actual Nostr protocol integration to speak of. The block seems to settle that question.

I'll accept almost any bet that you're using TCP/IP to scrape the post from a web page URL.

I'm sorry, are you going to claim here that you "built a better alternative" (based on Nostr no less) by git cloning https://jam.systems ? Maybe you should stop calling me a liar before you make me spell it out too clearly. Nothing you're doing has anything to do with Nostr except the letters in your domain name and the target audience you're asking people to flood with that domain name.

It is very generous to describe something that is undone when one clears cookies as a 'one-off process'.

You're just early. People in the future will become wise to schemes unrelated to Nostr forcing people to flood global and their friends non-global feeds.

Using nos2x to sign and broadcast a note makes nos2x itself redundant for the process of authenticating with NostrNests. Just makes people feel better about it.

Remaining logged in lets anyone who sits at your workstation know your Nostr identity by visiting NostrNests.

This defeats the purpose of having a pseudonymous protocol, since any search of your computer -- even if you have your Nostr keys in cold storage and only ever logged in using private browsing -- will identify you. You'll also have all those public unencrypted NostrNests advertisements you posted sitting in public folders on multiple servers to cryptographically confirm your Nostr npub really was the computer's operator.

Alby or a mobile wallet have less than nothing to do with Nostr, either. I've given constructive feedback elsewhere, but here I am defending myself from this accusation of making false claims.

How is the verification post scraped, over TCP/IP or Nostr protocol? If the former, it's absolutely 100% true to say you have zero Nostr protocol integration to speak of. Which is fine, until you call me out for pointing it out.

I'm someone, and I use global all the time. It's beautiful on https://iris.to/global maybe you just need a better client.

It matters to your repute that your verification advertisements are more relevant. You can make them more relevant by including the specific NostrNests Event URL that people can join in right when it's being flooded, rather than the NostrNests domain name only. Take it, leave it.

I appreciate this plain confirmation the 'verification post' was specifically thought of as an advertisement. Of course it's going to flood the global feed when an event is on. You could avoid that by providing a specific relay URL to send it to (some clients make it easy to set per Note) but then it wouldn't be an advertisement.

It would seem far less spammy if it had the specific event URL, rather than your top-level domain only. People could then at least join the specific experience while Global is being flooded anyway.

I reposted the specific Event URL on my Profile while it was on, as you can easily see, so you do have a fan here of what you're doing -- except the spam thing and framing a centrally hosted service that predates Nostr as Nostr-based in any sense but who was the audience of your advertisements. I mean, verification posts.

Even if I posted the authentication Note, I'm willing to bet even that is scraped via TCP/IP to a web client URL rather than a Nostr relay connection. That would be the sensible approach.

Which standards is downwind of any Nostr integration at all. I had a great time, but I don't think it should be mistaken for a Nostr-based service, since I used it without ever communicating via Nostr protocol.

Not the audio, of course, but not even the form that requested my pubkey connected to a relay to try fetch my avatar. It had to be reuploaded and resized to work, because there is no Nostr integration that is necessary.

This is something that seems to infect web3 circles, typically pretending something is blockchain based when it's really not, or requires a blockchain when it does not. My experience at NostrNests was great, but it wasn't decentralized and it wasn't communicating *anything* via Nostr protocol (since I didn't make a post to authenticate). It works without Nostr, to the actual open source software project that predates Nostr behind it be the glory.

Does that sound like Nostr protocol standards being followed, to you? Authentication requires a public Note post rather than invisible Nostr private key validation?

The community was sourced from Nostr, but that's all this show had to do with Nostr.

NostrNests is Nostr only in name. It doesn't even have Nostr key pair integration, it just invites you to input *anyone's* pubkey and upload *anyone's* avatar if you want to be recognized in the room. This is a self-hosted open source project modified with a Zap button that doesn't work and zero Nostr integration.

Which doesn't take away from my amazing experience with you amazing people. But let's not confuse Nostr with https://jam.systems or other open source projects that have nothing to do with it.

Somehow I think this is going to be a losing battle, convincing blockchain enthusiasts to be clear about what is and isn't actually using or even requiring their pet protocol. It's a meme at this point, even Marc Andreessen from a16z couldn't think of a web3 project that actually requires blockchain when put on the spot.

Oh it's not even involved in the login tho, it's just a form that asks for anyone's pubkey (you can put in @jack's) and anyone's avatar to display, it does zero Nostr key pair verification. Just a fork of https://jam.systems