Why Nostr? What is Njump?
2023-02-03 22:05:48
in reply to

NostReport on Nostr: THE NOSTR REPORT Notificationdrama Feb 3, 2023 Block Height: 774,912 Moscow Time: ...

THE NOSTR REPORT

Notificationdrama
Feb 3, 2023

Block Height: 774,912
Moscow Time: 4,282 ⚡/ $

—--------------------------
🎙Quote of the Day🎙️
—--------------------------
responds to a question about mass surveillance on Nostr by saying, “Nostr is meant for things that you _want_ others to see.”
Nostr is meant for things that you _want_ others to see.

—--------------------------
🚨Headline Nostr News🚨
—--------------------------
reports that Amethyst was downloaded 36,000 times, with steep trajectory up and to the right. 📈
36,000 Downloads #Amethyst


shows that Damus has 109k AppStore downloads in 3 days. 🤯
109k appstore downloads in 3 days


Nostr network crossed 300k npubs containing profile data 🔥according to
we just crossed 300k unique public keys with metadata!
https://nostr.directory/stats


states “Love the Nostr report. But it ruins my notifications :(“
Love the Nostr report. But it ruins my notifications :(
We’re sorry for ruining your notifications, but we believe this is a problem that will need to be addressed sooner rather than later as the network grows. Please read our official response here:
A message from the NostReport team:

We love the discussions popping up around notifications, tagging, and post length with NostReport. We are a group of plebs that are enthusiastic about Nostr and its potential for changing social networking, its ability to be a vehicle for the value-4-value model and bitcoin adoption, and ultimately its by-design nature that gives us each ownership over our identity and data.

We started NostReport because we saw a need for some way to keep up with the rapid pace of development here. We are early, all of us. As users, client devs, relay operators, nip-05 providers, content hosting providers, and content creators, etc., we are ALL early. In just the last few weeks there have been so many improvements implemented across these segments that it’s very easy to forget how far Nostr has already come.

Regarding NostReport specifically, we had a lengthy discussion amongst our team and we believe it is important to continue giving proper credit and attribution by tagging relevant accounts where appropriate. We will use our best editorial discretion in doing so, but we don’t have any plans to change that approach. We acknowledge that the “earliness” of all of this means not everything works exactly the same as it may if we were on another platform. But we are not on those platforms for a reason, and so we all deal with the growing pains of not yet having features that we wish existed.

Some features we hope to see implemented include the ability to manage notifications, including muting notifications stemming from a specific post/thread. We would also like to see clients truncate longer posts to a certain character count and then giving users the option to “view more.” We have seen this feature on snort.social and believe it is a good way to handle long form posts. Longer form posts also get harder to read with the way some clients auto-refresh their feeds. Even if you click on a post to open it sometimes the client randomly kicks you out of that view and back to the home feed and you lose your place completely. We suggest an option to turn off auto-refresh and give users a way to manually refresh when desired. We would like to see a better way to preview posts and formatting/tagging before publishing. Currently we must DM them to ourselves, which results in even more unwanted notifications for users we tag. We are happy to give feedback or discuss further with any devs that would like more input.

Lastly, we want to reiterate why we’re here. We love Nostr. We want to see it continue to grow and succeed and give everyone back control of their voice and online identity. We appreciate you following NostReport and hope that you’ll continue to give us feedback on how we can improve. Stay classy Nostr. 🤙

much like the rest of nostr, in complete disbelief of the Craig Wright 🤡🌎 case.
This is a completely different case. Craig claims someone stole 100k bitcoin from him and wants the courts to order the developers to write code that reassigns those bitcoins to his control

—--------------------------
🏝️Nostrica Update🏝️
—--------------------------
announces 220 in-person #Nostrica attendees, 400 virtual.
220 in-person #Nostrica attendees

Nearly 400 virtual

Join us: https://nostrica.com/

—--------------------------
🖥️nostr Tech🖥️
—--------------------------
laments the current relay experience on nostr and wants to work on a new future where the relay experience is more seamless.
I think the model of the client that tries to follow someone automatically is not incompatible at all with the model of the client that allows you to switch relays view and puts relays at the forefront of the experience. They are very compatible and the synergy between the two models can create interesting experiences. I wouldn't be unhealthy for some clients to specialize in one model of browsing while others specialize on the other, but a mix would be desirable too.

Also the algorithmic follow-by-heuristics method may work on Twitter-like experiences, but for most of other use cases that can be done with Nostr the browse-relays experience seems to fit much better.

Anyway, the only thing I think is terribly unhealthy is the current ubiquitous model of a "settings" page with a list of boring and meaningless relay URLs and people selecting these once (if at all) and never thinking about them again. This is horrible, centralizating, unscalable, a terrible anti-pattern. I take the blame for writing the first Nostr client with that experience.

Flashback Will
Flashback https://youtu.be/QXd0vLTw6NA

reminds us to be 🙏 nice 🙏 to the devs as most are working on nostr and fiat mine.
If you’re new and wondering why some of your favorite social networking features might be missing from nostr clients- keep in mind nostr is mostly volunteer-powered by developers who contribute their own time and money.

We did have some generous funding from Jack 🙏 which helped create some bounties for various things. Coinkite is also pitching in. But, we are talking a tiny fraction of what a regular startup might raise for just one app. For the most part, devs are donating their own time and money (relay hosting) which speaks greatly about the kinds of people involved and their visions for this protocol. Many are doing this on nights and weekends while working full time jobs. They could be doing other things and getting paid well doing them, but they are here.

Point is, please be patient, submit your suggestions and ideas and please stick around long term because it’ll take a while to be able to even remotely compete with the multi-billion dollar giants.

And of course, donate to the devs whatever you can. 💜 🙇‍♂️ You’ll see them talking about their clients and projects here, and most have lightning enabled.

Nostr is a community effort and everyone can contribute in one way or another. Nostriches ftw! 🙌

Nostr.band relay experimenting with way to limit global feed to your friends (people you follow) and friends of friends.
Since current global feed might be stressful to many, here is another 'safe relay' experiment.

Try adding wss://relay.nostr.band/YOUR_NPUB as a relay (replace YOUR_NPUB with your pubkey like npub1xxxxx).

This way this relay will only return to you events of your friends (those you follow), and friends of friends. So this is kinda wider than 'follows' feed, but much cleaner than the full global feed.

Some clients (iris?) try to accomplish the same themselves by dropping events from 'unknown' pubkeys. The above relay-level filtering works in any client, although you'll have to revoke read perms from all other relays, otherwise you'll be getting the full global feed from them.

Please let me know is this is useful.

One of the most Big 🧠 brain conversations ever to happen on nostr between , and as they debate if clients should select relays for users and if users should write to 2-3 relays or write to all their relays. All to help improve the nostr network.
One thing we should be questioning is the way we’re using (and thinking) about relays today in one capacity...

I think this idea of spraying public relays with our content might be wrong.

And we’re making all these decisions across the board on this idea.

Maybe:

I should really only post a given note to one relay intentionally for public consumption and 1 or more other relays strictly for backup.

Lots of things could be done but imagine some relays offer a /backup endpoint strictly for storage but not to expose publicly.

If I’m censored I can either request one of my backup relays to convert my posts to public or give me an expert so I can post them to a new relay when I want to switch or I am censored.

This would be way better because now there isn’t all this noise in a relay / across relays.

Now the idea of clients becoming browsers of relays makes much more sense and things get a lot clearer for users.

You don’t end up with this “why am I seeing the same post everywhere I go” and, from a design perspective, how do I show users this multiplexed view of a note.

And relays can emerge as identifiable things which they really need to be for nostr to work.

It really doesn’t make sense to spray the way we’re doing it now is what I’m saying.

—--------------------------
⚡nostr Business⚡
—--------------------------
shares his opinion that the Ordinals conversation is FUD from shitcoiners to get plebs to sell #bitcoin. Ordinals would only be a problem if miners colluded, countermeasures by users and honest miners would combat this.
If all the miners colluded, it could potentially ddos, but then there will of course be a countermeasures taken by users and honest miners.

I just think this is a pure attempt at fud to convince people to sell bitcoin and buy shitcoins.

Nostr Plebs suspends accounts due to impersonation. Today suspends first account impersonating a company after being contacted by the actual company. Company inquired how to setup NIP-05 ID on their own domain.
We had our first company contact us regarding ID impersonation at Nostr Plebs. After verifying the information received, the account in question was suspended. The company then asked us how to setup their own NIP-05 ID on their own domain. 👀 They're coming.

—--------------------------
🎩nostr Lifestyle🎩
—--------------------------
Relays having fun
Reading Nostr

—--------------------------
🩺Nostr Health of the Network🩺

Pubkeys 471,480
Events 1,164,417
Relays 280

Source nostr.io/stats

—--------------------------
🔥🔥Meme of the Day🔥🔥
—--------------------------
End of 2023…


End of 2023 …

—--------------------------
Stay Classy Nostr.
Author Public Key
npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk