Did I write something incredibly stupid and funny? :)


No, you volunteered for the new super secret project, hahaha
But I would also happily accept any help with this!


A positive approach would be definitively better.
Keep in mind that the title rotate with different sentences, but all are still positive.

And yes, the text can be shortened.


> I would not focus immediately on the negative

I definitively agree!
Thanks for this interesting feedback.


Actually nsec.app is a bunker, I would just be prepared for the future :) in meantime educating a little the users :)
Btw I agree, the majoirity of people simply ignore extensions.


A feedback:
The login screen shows a “nsec / user@nsec.app” suggestion, but it can actually be used with any bunker url; I would highlight this.
Then I think that the main options should be Nostr Connect and the extension, I would move the "danger" nsec option below, with a proper disclaimer.
You should also hide the extension button if it is not present (and maybe show a box that explain why and how the user should install it), currently it just fires an error in console without any visible feedback.


Hahahaha


Can you shill me some great websites/apps that support Nostr Connect (bunker url)?


Thanks for the feedback, I will reflect on this aspect!


2) Would be interesting to know how tech savvy are these people are and how much they trust you :D since usually you should check the link source to initially evaluate the potentially risk of a link. Btw, no links are virus if you don't deeply interact with the page (download and isntall something).
Finally, we are talking about the homepage here, not an internal link with the “strange” url.

5) I didn't say this is explained in the screenshot, I said it's on the page, and I said I think users are inclined to scroll on mobile. Of course the first view has to send a strong signal, and since different people are sensitive to different messages, Njump has an animation that alternates between various phrases that can “hit” the target audience.


There are several strenghts, censoriship resistance is the first one declared in the fiatjaf presentation and currently present in the main repo.
I agree that for the vast majority, the portability of the social graph is a more attractive value. In fact, it is explained in the "You own your audience" paragraph.


I know, quite wordy, but the goal here it is explaining the details, not doing quick onboardng, this from my point of view should be left to the individual apps (spoiler: with an exception, that you will see soon).

Btw, do you refer to the first view, or the whole page?


Really.
None of the proposed pages are low quality, so your this logic should not apply.
Users scroll to have a complete view of the page.


I will steal "a better internet" and add it to the typewriter animation of njump.me


1) Tendentially I agree, “decentralization” is only a tool to achieve resistance to censorship.

2) This make no sense to me, what people think that? There are dozens of “strange” extensions used daily (.io, .ly, .lol. etc).

3) Actually you are right, something has changed, the light version as a poor contrast.

4) "Take your friends with you" make sense, but it's not much business oriented. Maybe "take your social network with you".

5) The page explain just that, doesn't?


https://image.nostr.build/36355bbf82c395163b3b271e9fd8b69b88121343a969c457aae53abc8a4bcaa9.jpg

Actually, I need to add a immediately visible image on mobile.

Any other feedback?


The experience on a phone cannot be evaluated apart from scrolling, so the first screen is not totally crucial. Different matter, however, for the desktop.


Yes, it's a bug in the unstable version, btw now fixed.


Native Nostr groups are a reality thanks to NIP-29, they are a great collaborative development tool, but also a strategic onboarding asset.

nostr:nevent1qqsxws5vjcttj7cwyf6sftq7w3dz7nqaen6e9hhz67vdw0s4twlzd0cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygry26qmn5r8kx3k9397arwllxray3ndfxg9cfkt3lk9umah8t6usspsgqqqqqqsy2wq48


Sorry, just a bug in Gossip rendering!


URL?
I can see only a pic.


Cool!


Definitely better.


It's a solution, I thought about it but discarded the option, I don't remember why.


I have identified a cons: the user cannot verify that the url matches their public key. But how many people remember the hex?


I'm thinking whether it would be better to give bunker URLs a different enconding, e.g. url-safe base64. The current format for a new user is rather cryptic with special chars and some domains hints, but providing little useful information; and it has usability problems, e.g. it is easy to copy it incorrectly after a two-click selection, since this action copies only part of it.

Example:

bunker://8cfec14dc07bcc113fc447aee962af10d17eef6f7582a905f0bb1cd49904fa9a?relay=wss%3A%2F%2Fmyrelay.test.com

would became:

bunker://OGNmZWMxNGRjMDdiY2MxMTNmYzQ0N2FlZTk2MmFmMTBkMTdlZWY2Zjc1ODJhOTA1ZjBiYjFjZDQ5OTA0ZmE5YT9yZWxheT13c3M6Ly9teXJlbGF5LnRlc3QuY29t

A bit longer, but nothing dramatic. Probably I would also update the prefix, from "bunker" to something more nostr related and suggest that it is data that should be kept confidential. Maybe "nsecbunker".
Last, I would add a versioning param, es. v=xx, to facilitate future migrations.

Opinions?

/cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5


If it's possible adding a second row of buttons, you can let the user choose 3 options and put them there. Please verify that, so I can review the design.

I will review Pokey and open an issue with some suggestions.
If you are planning to add some features, please share them, so I can include them in the mockups.


Your are welcome, feel free to ping me if you need some help with the UI/UX.

PS: I don't know if on Android you can actually show a dialog on a locked screen, the alternative is showing more buttons on the notification, but it could be confusing with many items stacked.


I will implement it eventually.


"What I have noticed with big tech is if I think the can do x they will actually do it, and then the next question is if there's anything bad you can do with this tech, they will actually do it"

nostr:nevent1qqs0zdx5lpz4afzpg6wjrf4df28fm2cfzgatnf9jt8afs0j47uwaluqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0z65rp4


Yes, pinned notifications remain in a list within the app, snoozed ones are displayed again after the selected interval.

https://image.nostr.build/c1adc4789a700a750ed760e967859ffcba198b0f4efaccb04c26354665d17ec8.png


Actually Pokey also seems like an interesting solution if you decide to *not* install any other Nostr app on your phone: just get the notification without getting trapped, and put off any activity until when you are at your PC.

nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh maybe you could think about some specific features for this use case, for example the possibility to pin a notification and snoze it, ora add a short note.


Well, speaking URLs are generally useful because more informative, you can know what you are going to open, and so make an evalutation on that. But in the proposed form, just the author while keeping the (necessary) nevent code, are useless imo.


Here you can find a lot of models, with (free?) PDF/AI files to download. So you can easily print and cut it yourself.

https://www.pacdora.com/dielines-detail/custom-dimensions-tuck-end-boxes-auto-bottome-snap-lock-dieline-102012

https://image.nostr.build/d39e4ae7b769c66530b1ee6529adb31c779e6ce8f851c2914c6104e4bd48387b.png


Cool idea, I love these physical and retro things, maybe because I am old.
Unfortunately it is not my area of expertise.


Scammers are doing exactly that with subdomains, I don't think it's a solution.


Njump offers embeddable widgets, for an example see the homepage: https://njump.me


I agree that Njump URLs doen't have a great usability, but are necessary. Screenshots have many limitations, starting with the fact that it has no interactivity to bring the user back to Nostr.
Btw a lot of services have really long and weird URLs, see Amazon.


I learned a little more about why people have such a hard time with bitcoin's "intangibility" while talking to my mom last night.

I asked her what it was like when credit cards were invented, and she explained that before electric cards there was something called a "charga-plate":

https://historyofinformation.com/images/Screen_Shot_2020-08-18_at_5.41.58_PM.png

This was a metal rectangle you would present at shops, which would be pressed into paper to create an authenticated artifact of the transaction.

The precursor to charga-plates was just regular paper checks. In either case though, the mental model is the same, and credit cards simply extended the same mental model of having some physical cash in the bank (whether or not that is strictly true), and authorizing someone else to talk to your bank and pull some out.

Bitcoin completely breaks this mental model. The problem isn't that it's intangible, because we've been using intangible money since the 16th century. The thing that breaks people's minds is that it is intangible, and has no custodian.

When you sign a transaction, who are you authorizing, and to request money from whom? It really doesn't make any sense from the legacy money perspective to authenticate ownership of a UTXO with cryptography, broadcast it to an etherial network, *pay* one of several miners to include your transaction in a "block" (?) so that the math money can be split and some handed to your counterparty.

Anyway, I think this difficulty might exist for nostr as well. Credentials authenticate you with the account holder, but keys authenticate your content with the reader. To make this worse, users have to custody their keys, making them the account holder and custodian — and when they log in to an application, they have to ask themselves permission to create self-authenticating messages! Weird.


I see!


Is it really so bad?
I was speculating here https://stacker.news/items/756409/r/dtonon?commentId=757681 that they have some AI to check potential abusive edits when the context requires it (great exposure and many responses/reactions already recorded).
Maybe I overestimated these big tech circuses.

Btw, I agree, delete and delayed sending is everything we need.


How can you verify that the timestamp is real?


What we needed to clarify this issue, thank you.


# The case against edits

Direct edits are a centralizing force on Nostr, a slippery slope that should not be accepted.

Edits are fine in other, more specialized event kinds, but the `kind:1` space shouldn't be compromised with such a push towards centralization, because [`kind:1` is the public square of Nostr, where all focus should be on decentralization and censorship-resistance](cd8ce2b7).

- _Why?_

Edits introduce too much complexity. If edits are widespread, all clients now have to download dozens of extra events at the same time while users are browsing a big feed of notes which are already coming from dozens of different relays using complicated outbox-model-based querying, then for each event they have to open yet another subscription to these relays -- or perform some other complicated batching of subscriptions which then requires more complexity on the event handling side and then when associating these edits with the original events. I can only imagine this will hurt apps performance, but it definitely raises the barrier to entry and thus necessarily decreases Nostr decentralization.

Some clients may be implemneted in way such that they download tons of events and then store them in a local databases, from which they then construct the feed that users see. Such clients may make edits potentially easier to deal with -- but this is hardly an answer to the point above, since such clients are already more complex to implement in the first place.

- _What do you have against complex clients?_

The point is not to say that all clients should be simple, but that it should be simple to write a client -- or at least as simple as physically possible.

You may not be thinking about it, but if you believe in the promise of Nostr then we should expect to see Nostr feeds in many other contexts other than on a big super app in a phone -- we should see Nostr notes being referenced from and injected in unrelated webpages, unrelated apps, hardware devices, comment sections and so on. All these micro-clients will have to implement some complicated edit-fetching logic now?

- _But aren't we already fetching likes and zaps and other things, why not fetch edits too?_

Likes, zaps and other similar things are optional. It's perfectly fine to use Nostr without seeing likes and/or zaps -- and, believe me, it does happen quite a lot. The point is basically that likes or zaps don't affect the content of the main post at all, while edits do.

- _But edits are optional!_

No, they are not optional. If edits become widespread they necessarily become mandatory. Any client that doesn't implement edits will be displaying false information to its users and their experience will be completely broken.

- _That's fine, as people will just move to clients that support edits!_

Exactly, that is what I expect to happen too, and this is why I am saying edits are a centralizing force that we should be fighting against, not embracing.

If you understand that edits are a centralizing force, then you must automatically agree that they aren't a desirable feature, given that if you are reading this now, with Nostr being so small, there is a 100% chance you care about decentralization and you're not just some kind of lazy influencer that is only doing this for money.

- _All other social networks support editing!_

This is not true at all. Bluesky has 10x more users than Nostr and doesn't support edits. Instagram doesn't support editing pictures after they're posted, and doesn't support editing comments. Tiktok doesn't support editing videos or comments after they're posted. YouTube doesn't support editing videos after they're posted. Most famously, email, the most widely used and widespread "social app" out there, does not support edits of any kind. Twitter didn't support edits for the first 15 years of its life, and, although some people complained, it didn't hurt the platform at all -- arguably it benefitted it.

If edits are such a straightforward feature to add that won't hurt performance, that won't introduce complexity, and also that is such an essential feature users could never live without them, then why don't these centralized platforms have edits on everything already? There must be something there.

- _Eventually someone will implement edits anyway, so why bother to oppose edits now?_

Once Nostr becomes big enough, maybe it will be already shielded from such centralizing forces by its sheer volume of users and quantity of clients, maybe not, we will see. All I'm saying is that we shouldn't just push for bad things now just because of a potential future in which they might come.

- _The market will decide what is better._

The market has decided for Facebook, Instagram, Twitter and TikTok. If we were to follow what the market had decided we wouldn't be here, and you wouldn't be reading this post.

- _OK, you have convinced me, edits are not good for the protocol. But what do we do about the users who just want to fix their typos?_

There are many ways. The annotations spec, for example, provides a simple way to append things to a note without being a full-blown edit, and they fall back gracefully to normal replies in  clients that don't implement the full annotations spec.

Eventually we could have annotations that are expressed in form of simple (human-readable?) diffs that can be applied directly to the post, but fall back, again, to comments.

Besides these, a very simple idea that wasn't tried yet on Nostr yet is the idea that has been tried for emails and seems to work very well: delaying a post after the "submit" button is clicked and giving the user the opportunity to cancel and edit it again before it is actually posted.

Ultimately, if edits are so necessary, then maybe we could come up with a way to implement edits that is truly optional and falls back cleanly for clients that don't support them directly and don't hurt the protocol very much. Let's think about it and not rush towards defeat.


yo! I'm happy to announce the first release of chachi, a relay-based group (NIP-29) client for the web. NIP-29 allows creating groups that can be read by anyone or only authenticated users. These groups can be open to new members or require explicit approval from the group admins.

Every group gets a chat and a timeline of posts. I'll add more content types such as long-form and video in the future. Check out these videos explaining the main features of chachi.

https://nostr.download/71eedcea101f5fe9f1deb4c534ea3fbae67953e911f85a40fb0ac731b482b65f.mov

Finding and joining groups

https://nostr.download/47b29148c31c08f0295d97b9956396658ac8300d5e73598630fd4fe9996178ab.mov

Interacting with chat messages with reactions and replies

https://nostr.download/2af6f1a9c2f6ad96cdf529836737585a49038e8ba423465d17e96520239215bd.mov

Sharing different content types in chat

https://nostr.download/01f4ed8300b7dad45098780633597e3c1e91c93e13c50fedab6f817541529975.mov

Try it at https://chachi.chat

Source code is at https://git.v0l.io/verbiricha/chachi

Let me know what you think in the #chachi hashtag, this post or the official chachi group https://chachi.chat/groups.0xchat.com/chachi


Cool, congrats!
Happy to see a lot of work in the NIP-29 area.


Mirror Android devices (video and audio) connected via USB or over TCP/IP, and allows to control the device with the keyboard and the mouse of the computer, handy!

 https://github.com/Genymobile/scrcpy


Nostr's bunkers are flourishing

nostr:nevent1qqsds9ywz06m2jswyqcch40q7hphk3shms3a89u746jgpsd787wd66cprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhxgctdw4eju6t09ushemcj


Web.


I'm focusing on the creating the profile, I think this is the first crucial step, then we can redirect the user to any app, web or native.
Amber is great, but unfortunately is not cross platform.


Is that what Damus does now?
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s any details, please?


Yes, solid features and better experience, starting from the onboarding, I'm just working on this.


I totally agree.
However, understandably, some people do not understand the consequences of implementing such a seemingly simple function. Perhaps we should integrate into the NIPs why some architectural choices (or non-choices) are made.


I said "a lot", not every :)
I understand that edit is an interesting and useful functionality, but it has several drawbacks on Nostr. Amethyst is the only that implement *this* kind of edit because others devs agree that the disadvantages are greater than the advantages. There is another proposal (by nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn) that has been discussed and it seems more appropriate.

Btw, long contents (and lists) should probably use the long format, that actually has the edit feature precisely because it is considered important in the writing of an article. Why don't you use it?


Delayed sending is a thing, it could easily solve a lot of basic errors.


With the outbox model, we finally have an alternative to my spaghetti model.

nostr:nevent1qqsgnm06cqmgzfq9cp3pda99k2lc7pj28v2q4d555lf3dukmxlcxlqqpz9mhxue69uhkummnw3ezuamfdejj7q3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqqqqzvv9059


Yes.


Benvenuto!


Formstr, Groups, Coop, Nostrability, and NIP-44. More to come.
https://opensats.org/blog/8th-wave-nostr-grants


Interesting point of view.
By “debts” I was instead thinking of the more occasional and private ones (I lent you a book, you paid for my lunch, I take you to work every day, etc.).

In any case, with this rule even in the financial world the flow of money would happen, you just don't know you have to pay it back and the lender doesn't know he has a credit (not so easy to imagine since transactions are heavily recorded). But things would be built anyway.
Perhaps the lender, seeing that the other is doing interesting projects, would be spurred to do the same with his finances (and thus consequently lend less).


Every day, upon awakening, every debt, material or moral, to oneself and others, is reset. You have no more memory of it, as you do not know that it will be cancelled. Wouldn't that be an interesting way to live? Would good or evil emerge?


Keep it without colors, it's beautiful!


This is self-knowledge


How is the situation different today if you add nostr.wine to both incoming and outgoing mail, or flags both read and write, because you don't know the meaning of the terms and the implications, and then as is typical you turn everything on “to try if it works”?

Since nostr.wine requires auth the app might explain that this relay is poorly suited as a general inbox, but it might still be useful for users registered with it, and then suggest adding another public one, or disabling it as the inbox (read).

nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c recently added a relay testing tool that could be a good example of how to direct the user to the most appropriate use of relays.


I didn't referred the 120 years span to a temperature graph or CO2 levels.
Mine was meant to be a broader discourse, I think I explained myself in the following messages.


Thank you, I will try to read it.

About the erroneous narrative and underlying interests, I think it is interesting and important to talk about it openly. It may not be a scientific subject, but it helps to understand the positions of individual parties, and thus weigh their aims and intentions.


Perhaps my language could have been misunderstood. By “I don't care” I meant what I pointed out in the following note, which is that the fact that they may be telling the falsehood does not change the fact that in the last decades the earth system has been put under pressure by many human actions.

I know very little about this subject, but I have noticed that there is often a clash on the subject of temperature and global warming, when the environmental issues are much broader. Indeed, temperature is only one parameter to be monitored, but there are many others, such as the presence of chemicals in the air, soil, plants and animals. Or like the incidence of certain diseases.

So when I see a graph that focuses on the change in temperature of the planet over 500 million years I sense the risk of bringing attention to a single parameter, which perhaps is indeed completely normal, consequently dragging everything else into denialism.

But as I said, I know little about this area and my reaction was probably too knee-jerk, although I think it has its own logic.


The restriction issue is an additional point, which remains valid for any user interface. I would only start by simplifying the way relays are exposed to the user, but not blocking them if they want to make more complex configurations.


The idea is actually not to have inbox and outbox sections at all, but a "personal relays" section that smartly manages read/write flags behind the scenes. If a relay requires auth to write, the client should (could) disable the read (inbox) flag.

The average person should just add a couple of big free relays and maybe a couple of paid relays. No need to explain much to new users; as soon thwy will understand more about Nostr, they will be free to tweak the details.


So I ask, do you have a scientific answer?
And secondly, what is the purpose of this narrative based on erroneous facts?
I am genuinely interested.


As I said, I know nothing about the IPCC, but the fact that they falsified data doesn't change the fact that in the last few decades, the climate, not only temperature, changed brutally. We should also keep in consideration the timespan in which events happen, not only the absolute values, because time is necessary to adapt. It's clear that "industrialization" moved some values suddenly, and humans have not been able to keep pace with evolution to avoid serious damage.

Btw, what IPCC's final goal?


I don't know what is the IPCC agenda, and actuality I don't care. I neither can do a full research on my own on planetary scale. I just observe the last 120 years timespan, when industrialization and chemicals arose, and evaluate the increasing problems on my local area, related to health,  (physical and psychological) and environment. It's quite clear that we reached great technological goals, that helped extend humans life, at least temporally, and their comfort, but we are also breaking some other balances.

As said, the temperature is just a signal. When the wise man (not me, of course, it's the planet) points to the moon, it is no use staring at his finger.


It should discourage him, suggesting a "sensible" approach.


Yet another #nostr desktop client released!

This was originally a feature of the nostr-relay-tray project, but inspired by nostr:nprofile1qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5qnvvze, I decided to develop it as a standalone application. #devstr #grownostr

Features:
- Relay-Based Browsing: Explore content directly through relays without following specific users
- Relay-Friendly Design: Minimized and simplified requests ensure efficient communication with relays
- Relay Groups: Easily manage and switch between relay groups
- Clean Interface: Enjoy a minimalist design and intuitive interactions

NOTE: Currently, only browsing is supported. Posting, liking, and reposting will be available soon.

https://github.com/CodyTseng/jumble
https://image.nostr.build/0d287ceeef30e51371f236f780758953f6d07572899f185e9e33f5f8b70ee7e2.png
https://image.nostr.build/538ff993f2c2e79adf52893c4d7446a3a7a553f56298fbd17aacb37fef88a680.png


Are you really showing a graph with a scale of 500 millions of years, to demonstrate that there are not problems, now, for the human being? The temperature is just a symptom, not the biggest concern. Think about what you breath or eat.


Other's inbox relay are transparent from user's point of view, who should not have to worry about it.

I think that the main source of confusion is related to the fact the 99% of the time two different relays, inbox and outbox, are not really needed, they can be a single personal public relay.

Clients should just allow to add them, and only in an advanced configuration let the user tweak the read/write permissions (or deduce them by the actual permissions).

Then the user can be allowed to add an optional DM relay (suggesting that it enforces authentication), a search relay, etc.

As you see users think that the relay setting in Amethyst is quite confusing, after the Outbox model update; this approach could solve this.


So completely unrelated. Weird.


Same problem here using and external SSD formatted fat32.
What filesystem are you using?


This event has the wrong hash for this image. How does your client deal with that?

https://mikedilger.com/bs.png


Hahaha I see


https://github.com/fiatjaf/khatru/commit/91e7737ec12483118365a2ab616786a212f5d5b0

Ah, damn, and I was integrating it from scratch haha


Wait

> h/t nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 for adding blossom to khatru

What did I miss?
Is Blossom now included in Khatru?


Damn, you won the race, I'm also working on integrare Blouson in my relay! Haha
Btw, cool!


Cool!

nostr:nevent1qqsvacazw5eg4uwf3h0cea2hutndwldlra247443tpe3wqsg5ajqdgc767089


Murals are underrated art, welcome!


People like and talk about rss readers because they have a paradigm and user interface that allow the user to granularly control the information, not the other way around.

The specificities of an RSS feed are basically twofold: to organise the contents of individual sources in a personal hierarchical structure, and to make it possible to distinguish what has already been read from what is still to be read.

This is quite aligned with the ethos of Nostr, so a convergence seems very plausible and necessary.
Unfortunately, Nostr's developers don't much like lists and similar structures, all preferring the approach of a huge, monolithic feed, where the read status is impossible to manage.
They are so adverse to this approach that practically no clients have a dedicated section for the long format in the user profile!

So asking the rss developers to integrate Nostr might be a good plan to bring in some fresh air. This could also encourage more users to use Nostr for blogging.


The cache bug should have been fixed, can you share an outdated profile?


So double weird.
I tried to search the email that I received, but I cannot find it, trashed.


Just check where the button link leads to.


I received the same email and, damn, the sender is actually Microsoft. Reality poor security management (as usual) from them. But the SPF record exists, so the scammer exploited something else.


I doubt the sender was @microsoft.com, right?
Or no SPF in place? Crazy.
Btw, I'm also getting a lot of phishing emails branded Microsoft lately.


Yes.


I have always used macOS (or whatever it was called before) and owned an iPhone 3/4, but then I switched to Android both because it is more configurable and because I wanted to force myself out the comfort zone of a closed ecosystem. I absolutely do not regret the choice.


It depends what the attacker want to do with your key. For example he could just change your lighting address in the profile to forward himself your zaps. You can also use some tools to list all your events, included those that are not notes, but unfortunately it's not easy to detect if an event was signed by someone else,l. You have to take care of your key in advance.


It is not yet time.


Cool, great progress Jeff!


Now it works, I don't know, weird!


Nice, some suggestions:

- Putting "report" after a "follow" CTA seems weird and has little discoverability, I would move it outside

- The follow button in the modal probably works better at the bottom of the screen, fixed; this incentives scrolling the list before confirming the action

- I would display the original name below the nickname; this help tracking renaming errors and changes by the user

- I would add a "revert" icon in the edit form, to reset the name

- For an app named "Zapchat" I would expect to find a prominent zap button in the profile :)


Yes

https://image.nostr.build/5b97113c2512446f20ce1abed39e1137d0ff0a9dd26cd5a5a90ca796ab012d99.jpg


Thanks!


Does anyone use https://zed.dev?
How good are the LSP extension?
Does it support local AIs?

#asknostr


Some time ago I read some serious critiques about him, but I cannot recall the details. Can you sum them up?


Un classico.


Followed back!


You have to screen the events signed by the key and eventually spot something weird that doesn't belong to you.
Usually the easiest way is to follow yourself.


NIP-89, interoperability wins.

nostr:nevent1qqsqqqpa4juhpdedslss5n44mlkvnhkt7twgdcgw37alpkr29dn0cgsppemhxue69uhkummn9ekx7mp0qgswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgrqsqqqqqpvuc03s


What china do you use?
I use a fountain pen with a water-resistant ink (from Japan, if I remember correctly).


I like to paint watercolours with coffee too!


I just watched the video, really cool presentation.

nostr:nprofile1qqsd4dkxqewy8xum47ctpu0ltgxxsfemeewpjkdyzk9ddfcg286s0dsppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq36amnwvaz7tmwdaehgu3wvduhq6r9wfc82mnt9e6x7erp0yhs4deh46 a little bug report: your web site doesn't have http to https redirection enabled, so the user could hit that weird error and just leave.
Probably your browsers cached it so it's not immediate for you spotting it.


A simple suggestion: build a desktop client.

PCs are a different species than smartphones, they are built to produce things, not just consume them. Therefore they have a more complex, more ductile and therefore more creative environment, which naturally develops skills.


This!


Aurora store is probably riskier that the (sandboxed) Play Store offered by Graphene, used with a Google account created just for that, since it simply add an actor to the supply chain.

Android 15 offers "private space" a good solution to isolate group of apps.


https://github.com/dtonon/chronicle has an optional PoW setting to bypass the WoT. But probably it's not what are you searching.


“There is no putting the genie back in the bottle. And now every government in the world gets to reform itself in light of that knowledge. This is why we're seeing CBDCs… CBDCs are a direct response to #Bitcoin “ - nostr:npub1kvgw6zj55uwvlz5rdqpjm5a5hqah4j3ggza3pfx4umh5k6j00yaqt6v0p2 on nostr:npub10qrssqjsydd38j8mv7h27dq0ynpns3djgu88mhr7cr2qcqrgyezspkxqj8

https://v.nostr.build/pZS2cC86ObISbNqf.mp4 nostr:note1vpylcglhm80n3wjs6hkz6st8cd09jych5l37epcsfjkjr4zc95rq65wnrv


Today is my turn.

nostr:nevent1qqsw05dtjh40jcpe9tths2ehscuqlk5uc9vxnslnwhqnwh5j7spjqmqppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcprfmhxue69uhkuurjdau8jtntwf5hxarpwpekktnvwchs40q5wm


Do you have direct experience with LoRa (meshtastic/reticulum/etc)? I would like to understand the actual range on different terrain/landscapes.


Scary. On which apps did you talked/texted about the products?


Crazy, but really inspiring, well done Max! :)


Or make a new CLI command that simply wraps and calls nak?


Yes, I agree 100%
Maybe I would also remove DMs, since they naturally fit well in a client that focuses chats. And you have Flotilla for that.


https://noogle.lol/?q=daniele+gossip
doesn't highligth my profile, it seems it focuses only notes.


Relays don't have to split in multiple queries, they have to implement a good search using weighted fields, proximity and fuzzy. Often the problem is client side, as you can read from my quick test.


> Language filtering is standard in NIP-50.

Oh sorry, right, checking the video I thought it was a classic req, not a search.


Unfortunately, I can't say the same, check my basic test that I posted a short while ago.


Language filtering is nice (even if not standard), but also Ditto fails by basic test:

nostr:nevent1qqsqqqp5ayhuq60jjtwg9x39ewvdw22zmr3nvge6a9204nsrt56ykhqpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgmwaehxw309a3ksun0de5kxmr99ej8gmmwdahzucm0d5hsh2gz33


The implementation of NIP-50 is usually fine, I think. The main problem is that clients do not use it, and the custom search approaches are rather inaccurate.

My basic test is searching myself by display name (since it's more common), adding a word from the bio; using the name (that on Nostr is not unique, of course), plus an additional keyword should be a basic way to find someone. Example:
nak req --search "daniele gossip" -k 0 wss://......

Results:

relay.nostr.band: found
nostr.wine: found
relay.noswhere.com: error
search.nos.today: zero results

50% success, not exceptional.

Let's see how the search for "daniele gossip" works in some clients:

Coracle: zero results
Nostrudel: found
Snort: found a note, not the profile
Primal: found a note, not the profile
Habla.news: found a note, not the profile
Gossip: zero results
Amethist: zero results
Voyage: zero results
Nostur: zero results
Damus: not found

10% success, disappointing.

Some clients work better with a single world ("daniele"), but it's just a casualty, since a single keyword is often meaningless without a context or a proper sorting.
Weight fields, proximity or fuzzy full text search are still science fiction.

I will do more tests.


Thanks for the suggestion.

It searches just the "display name," ignoring the more important "name" (and probably all other fields). This is, unfortunately, a good example of the state of the search.


Search, the big missing piece of Nostr.
Is anyone working on NIP-50 and related?


> limits 1 author per feed

Good.


Always save the draft and add an auto-delete procedure to purge them with a config (1 days -> never, with default at 1 week).

The best interfacce is no interface, it cannot break, it doesn't need to be explained, it cannot be misused.

PS: In the thread highlight the drafts, for example with a light yellow background, please.


GM!

Reminds me of this: https://i.nostr.build/2a21WjzR6ppDz6P9.jpg


Agree!

nostr:nevent1qqsqqqpl53sk8r6av4xvxafmsmq8hfkk3xyx8n6mugtkcenk64fmr4gprdmhxue69uhkx6rjdahxjcmvv5hxgar0dehkutnrdakj7q3q0000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsxpqqqqqqz37r9x3


It also includes #LoRa for off grid messaging, I supopse it can be used with #meshtastic or #reticulum


https://github.com/lnbits/arduino-nostr/ +
https://www.wiphone.io/ =
FUN?!


True


Keep painting, just that.


Your painting is becoming stronger and more vibrant. And notice that you are using fewer brush strokes...


The resulting feed is quite good!
I would appreciate if the feed could push authors who publish less frequently, but have good content (=historical trend), higher. This would really improve discoverability and variety.

nostr:nevent1qqsz5gdtpk3t07wjtu935u3syzpk6qgvsh6aaw6qghskw9arehj75lgpz3mhxue69uhkzmr8duh82arcduhx7mn99uq3gamnwvaz7tmpd3nk7tn4w3ux7tn0dejj7qg5waehxw309askcem09e6hg7r09ehkuef00jwelu


Interesting graph, what's the source?


It's a work in progress, not yet ready.


I suppose so.


I like this relay-as-a-custom-feed approach. I hope this sort of experiments will force clients to finally embrace single feed browsing, and make it a first-class citizen feature.

nostr:nevent1qqs9qwcy25ac5rn8avzl6mq0na4eqrfv29fxw3nc4y0tuu0a8029nxqpz9mhxue69uhkummnw3ezuamfdejj7q3qutx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4sxpqqqqqqzcu0anh


Thanks Derek, I know I can find it around, but I would prefer a trusted source.


I would like to test Strike but it is distributed only by the app store, and anyway it says that the app is not available in my region (it is), what a mess.
nostr:nprofile1qqsvf646uxlreajhhsv9tms9u6w7nuzeedaqty38z69cpwyhv89ufcqpz9mhxue69uhkummnw3ezuamfdejj70v5n7z can we have direct access to the apk? Maybe also using zap.store could be a nice option.


Doesn't clients usually force the order of incoming data? I think so.


Thanks, good catch, it actually seems a bug in the decoding.


Thanks, I was searching the link to post it, a classic :)


LoRa buddy

nostr:nevent1qqsgk72mcax5zvj36jclrvwjj4698lgh558r6upjtx80m89cfvjrh5cpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcau4yps

#meshtastic #reticulum #freakwan


If I'm not wrong, nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w some time ago wrote about his experience about filtering out CSAM content.


Yes, groups/relays are only a part of the solution, the general idea is to offer proximity of language/geolocation.


Envisioned

> trying to match the user with the nearest geographic relays, to incentive a first aggregation by culture and language

nostr:nevent1qqsp49qnmtq88lf8gp02vy4u800rgafkqjs9sv032u566fdd8v796nqpz4mhxue69uhhwmm59ej8gmmwdahzucm0d5hsygrmmmmmugka3evlgcqwq3922wsul966nhrayl04svauwldhsjjcq5psgqqqqqqss3yz3p


https://www.lesswrong.com/posts/bshZiaLefDejvPKuS/dying-outside

"I may even still be able to write code, and my dream is to contribute to open source software projects even from within an immobile body. That will be a life very much worth living."

Impressive reading, check also the comments.


They are the worst. Not to mention the absurd complex of apps that connect everywhere, sending unknown data.


That's what I'm doing, you need to remap your muscle memory and accept some little pain, but it's worth it.


I will try it, thanks!


NIP-22 is showing up

nostr:nevent1qqsda2w2nm7mh6m39lpcdvgudrcdtzxcgcvekcfa90yvftlrlmmzwjgppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqjqamnwvaz7tmwdaehgu3wv45kuatwv3a8wctw0f5kwtnnwpskxef0f3m7gm


The rumor should provides a measure of deniability, since it is unsigned.
But actually, if you can decrypt the seal you can also decrypt the rumor, so the layers of separation are not so strong.


Oh right, they are creating a new desktop enviroment, I will check it.


That's cool.


I'm also trying rectangle, not bad.
I think it depends a lot on the screen size. On a small screen many apps require full screen for a good usability, and terminals maybe half or a quarter of the screen.
On a large screen a tiling structure maybe can help to quickly optimize the space.


No, it's a PopOS thing:
https://github.com/pop-os/shell


Even if it's not so hardcore, I like and find really usable the tiling manager included in PopOS


Ok ok, no love for tilling managers by macOS users.
Then, shill me your best choice for Linux!

nostr:nevent1qqsqqqqw2mllnkexz46qzm455jd09xh84rcjnw4t7lgy0nuds0m79nqprdmhxue69uhkx6rjdahxjcmvv5hxgar0dehkutnrdakj7drjear


Do you use any tilling manager on macOS?
I'm trying yabai + skhd, but I'm not sold.

#asknostr


This is why we #Nostr.

nostr:nevent1qqsp82dhrs73akl05vuzvl0uk3ajyw3m45t68eq3j807exgvrwx2v8cpz9mhxue69uhkummnw3ezuamfdejj7q3qq6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7qxpqqqqqqz9g0jzy


Cool!


People seem to be excited about my new project, Flotilla. It's still very much a WIP (probably a month out from MVP), but since it's been discovered I figured I'd go ahead and introduce it.

https://image.nostr.build/b9842d89fdc786ad3e86d692c4b52adce47e1bdd9daaf7d39cbf4806ecb75bc2.png

My goal for Coracle has for a long time been to support local in-person communities by replicating Facebook's events, groups, and marketplace. I've come to realize a few things about this project:

- Facebook is not the gold standard. In fact, people hate Facebook.
- There are many kinds of groups, for many different use cases.
- Very small chat groups work for most use cases.
- For almost all other groups, good moderation is key.
- Decentralization for groups works differently from decentralization for microblogging. Microblogging use cases benefit from simultaneous use of multiple relays. Community group use cases (in contrast to reddit-style groups) benefit from a single relay per group.

This is just the barest summary of what I've learned. But it's all in line with my long-held intuition that relays are, and should be, special. To that end, I'm creating a new client built around the dumbest form of communities that can be created: relays as communities.

Lots of code and specs need to be written to make this work, and as with Coracle, it'll be possible to host your own flotilla instance that only talks to a single relay, as well as use flotilla on desktop and mobile as a PWA and APK.

See the dev preview at https://flotilla.coracle.social. If you're interested in contributing, I've created several issues on the repository that should be good for first-time contributors: https://github.com/coracle-social/flotilla/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22


I also was confused by the UI, but if you use the square button on the right, you can login with a NIP-07 extension.
Then, if you inject https://github.com/fiatjaf/window.nostr.js via bookmarklet, you can also use your nsecbunbker.


Just pushed an little update to automatically include in the backup quoted events (and related reactions/zap) as well.

nostr:nevent1qqsqqqqq8f3e5dd42xu9n7nd8p0vnsy295dzfmld4f6ccal4nygt8sspzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgmwaehxw309a3ksun0de5kxmr99ej8gmmwdahzucm0d5hsnj5kd9


If you write a whole program but didn't make the compiler, you actually have no idea what code you're running.


true


"Test"


What is the incentive of arbitrators?


Winning (maybe) alone vs. Winning together
What do you choose?

nostr:nevent1qqsqqqp2zrs7836tyjlsfe7aj9c4d97zrxxqyayagkdwlcur96t4lasprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsjdqrlj


Love it.


You are out of my WoT.


I suppose it is a question of 'base': those who like pineapple topping have probably never tasted a real pizza from Naples, so on their so-called "pizza" with a so-called "mozzarella" maybe pineapple is fine.

/Snooty mode on 😂


Hardware signer are cool but unfortunately have poor scalability for the masses (cost, shipping logistic, mobile usage). I would aim for multisign/Frost solutions.


Now it should be better, thanks for reporting


Until we have topical relays, I think the simplest approach is for each client to categorise the typology (what nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 is doing with Gossip) and randomizes the assignment, maybe trying to match the user with the nearest geographic relays, to incentive a first aggregation by culture and language.

A variant may exploit an invitation system, such as that of Coracle, and assign the new user the same relays as the one who invited in order to maximise the visibility of both parties.

Finally, when topical relays will bootstrap, probably thanks to NIP-29 groups, a simple "pick your interests" wizard could improve the assignment.

Actually, here I see more engineering than UI, at least for the onboarding phase.
Instead for more advanced users, I would try to surface relays by country, social graph usage and topics.


My dad has several Nikon and Olympus too. I need to load a bw film on the beloved Olympus OM 3 Titanium and take some shots.


Angieneux lenses... wow
But kudos for the boxless treasure.


A piece of history.
Cool stand, too.


And I have the same problem with Voyage, nostr:nprofile1qqswgvmv65ja7706f5a0xe8ajcqdfvgdeeppt2jvx0kh06sggg6ykyqppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3uamnwvaz7tmjv4kxz7fwdehhxarj9emkjun9v3hx2apwdfcz75extm3


I'm looking at 30000 "follow list".
Amethyst correctly loads plain lists, but it seems to discard the encrypted ones.

/cc nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw


> a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays

This should not be a problem, it is how the Outbox model works. Any other additional relay comes from a broadcast from users that interact with the event and this organically increase the decentralization and reachability of user's content.

It seems that you want to create an hybrid client/really, that actually could be useful in edge cases to support "thin clients", especially on mobile.


I told you it's a necessary feature 🤷😂


Thanks, but Gossip produces corrects NIP-51 lists, so the problem should be different.


Interesting.
What's the ultimate goal of this tool?


I actually also remember using an encrypted list on Amethyst a long time ago, but now all my private lists are gone.


The "unfortunately" refers to Amethyst.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z are private lists planned?


I don't grasp your concerns, why would a relay ever decrypt anything? Can you elaborate?


Siddhartha Gautama doesn't seem so primitive to me, and he said a few things about the reality of things.
I think we are improving overall.


U
Yes, unfortunately only public lists.


My journey from North Korea to freedom taught me that true freedom is more than escaping physical borders. It’s about breaking free from systems of control. So I see Bitcoin as a tool to help people regain their freedom, not as a matter of being a "Bitcoiner," but as a way to empower individuals to protect their fundamental human rights.


Welcome! 🙏


PPE Relay - a paid relay that accepts notes on a pay-per-event basis.

wss://ppe.swarmstr.com

Powered by khatru framework by nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgnwaehxw309amk7apww468smewdahx2tckuej4c

How it works?

- For storing an event, the relay charges 1 sat per single event.
- The amount is subtracted from the user's balance each time event is accepted.
- To top up your balance, simply zap any note from nostr:nprofile1qqsqsujjc4r3s683cn8nvda0m8s2z70elp65nml3lvcykqm39w8duucpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjeeaj3 with the desired amount.
- Only kind 1 (note) and 30023 (long-form) events are accepted.
- To view your current balance, tag nostr:nprofile1qqsqsujjc4r3s683cn8nvda0m8s2z70elp65nml3lvcykqm39w8duucpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjeeaj3 with "balance" command.

Repo: https://github.com/ptrio42/ppe-relay

Feedback/suggestions appreciated.

Note: This is an experimental phase so expect some bugs.


Nice cover too


It's great!


In front of a crazy world, this is tenacity.
Stay safe Efrat.


> Technically you would still hold the key as a user,

Good, so we align on my last sentence "paired with a real good UI to enforce the user to keep a backup".
That makes sense.


Chris are the notes synchronized automatically?
If so, can you tell us more about the encryption scheme used?


Cool, just what I was envisioning for abandoning Obsidian, Joplin, and Logseq.

nostr:nevent1qqsqqqrdnaus8g2mdx675jn5q6z27u88njuu09ncnxv6wa494aejwcgpzfmhxue69uhkuenjv4kxz7fwv9c8qtcpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hscqzr5s


Nsec.app and local signers like Amber made custodial providers less interesting for tech savvy and diligent users that know how to self custody; but for onboarding a lot of casual newcomers, a custodial solution still seems a needed solution.

I'm reading the MuSign2 and Frost proposals, it's an interesting approach, but how do you ensure a robust infrastructure of more than 3 parties, which should be totally disconnected to demonstrate security? What incentives should these nsebunker providers have? Do they get paid? And should the user choose them randomly and pay them separately? And what happens if a payment is not made or if multiple nsecbunkers disappear at the same time breaking the quorum?

An alternative solution is to offer a single custodial nsecbunker, supported by a well-known entity (OpenSats?) and build a really clear user experience to lead the user (maybe forced after x amount of time?) to self-custody their key. Of course, this kind of structure would immediately become a centralized weakness, and thus a clear target for anyone who wants to destroy Nostr. Not to mention that it is not an absolutely easy structure to create and manage with good security standards; who would actually do it?

I don't know what would be the most effective way to proceed. I would probably try to elaborate the Frost approach, paired with a real good UI to enforce the user to keep a backup and validate it randomly every so often.


New minor release of Coracle is out, now with NIP 55 (Amber) support! Thanks to nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszrnhwden5te0dehhxtnvdakz7qgewaehxw309aex2mrp0yh8x6rpwfjkwcts9ehx2ap0qy88wumn8ghj77tpvf6jumt99uqzpn0wjs7tkxw9r2uy0fndt4m5xua2na3a9peydw6ekzp8lf0xxaqqc2ztx7  for doing what was (for me) impossible.

The updated APK is not yet on nostr:nprofile1qydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnnw3hkuetj9e3k7mf0qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qyjhwumn8ghj7en9v4j8xtnwdaehgu3wvfskuep0dakku62ltamx2mn5w4ex2ucqypuvuma2wgny8pegfej8hf5n3x2hxhkgcl2utfjhxlj4zv8sycc86trxjy7 , but is available on the releases page:

https://github.com/coracle-social/coracle/releases/tag/0.4.11

# 0.4.11

- [x] Add NIP 55 support to Android
- [x] Add negentropy support
- [x] Simplify sync for messages, groups, and notifications
- [x] Small UI fixes


There is no way to lock a name, you can also legitimately be daniele; and this is a different matter from NIP-05, that instead is unique and can be verified.
In your example signing would not help, just check the author npub, that's the source of truth (and indeed it is used in a signature check).

Thank you for building :)


It seems a great update, congrats!


Damn, it's exploding.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is the new lmdb going crazy?


This is cool

nostr:nevent1qqsxez89rcry9u3rqugwgcmxzkdfv9p948uf2twj4l3h5r3hpe45z3spzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyghwumn8ghj7mn0wd68ytnhd9hx2tcejmg2f


"Nostr-PHP dev Live now! Streaming hosted by Sebastix"?
It seems working fine here. Also the app buttons work.


How can they tied someone else pubkey to their name?
NIP-05 includes the pubkey, the client verify that it matches with the pubkey of the (signed) kind:0 profile where the NIP-05 is saved, that's all.
Signing the NIP-05 doesn't improve this process.

Actually, signing NIP-05 could prevent someone, after hacking the server, from modifying NIP-05 itself. But it is a borderline case, adds a layer of complexity, and seems unnecessary for a simple identification tool.


For the Outbox model, here is where all started (it was originally called Gossip, from the name of the client that introduced it): https://mikedilger.com/gossip-model/


I love the blue boar!


Damn, you parked over a police car?!


There should be no delays in accepting notes, but in the last days we got several spam attacks and many relay tried to filter them, so this may have generated some rejections.
I suggest you to use a client that fully support the Outbox model, pick up a couple of public relays and a paid one with a good spam protection, to try to be visible to those using WoT relays.
Next step: run your own relay.

If can be useful:

nostr:nevent1qqsqqqq32xv7lhdrt2fdsp9za5un2wacaz735zqu0zrdlzeyn0mtk3qpr3mhxue69uhkxmm4de68y6t9wvhxv6tpw34xze3wvdhk6tczypaaaaa7ytwcuk05vq8qgj498gw0jadfm37j0h6cxw780kmcffvq2qcyqqqqqqgva957d


It depends on the number of calls in the unit of time.


Yes, it was added to block a possible DoS attack, will be removed shortly.


Is it slow?
I (partially) fixed a problem few hours ago.


And Twitterbot is not better


Damn Amazonbot


In brief

Relays:

https://github.com/dtonon/chronicle
https://github.com/bitvora/wot-relay

Clients:
https://github.com/mikedilger/gossip
https://github.com/coracle-social/coracle/
https://github.com/dluvian/voyage
https://github.com/vitorpamplona/amethyst

The configuration should be fairly obvious, but I will eventually do a long format.


It's on my buy list!
Can you test the range in different environments? I am curious to know how far two such clients can communicate. For example within a city with many buildings, or in the mountains in a forest.


👀
nostr:nevent1qqsxuqzk6ar46mxx0xv02fwrccy0q9zmr9t94m7qusaxjlvkahte3qcprpmhxue69uhkxetvd3shytnwdaehgu3wwa5kuef0qyghwumn8ghj7mn0wd68ytnhd9hx2tcl2aap9


What kind of details might be helpful?


> so if it's not ready it would reject everything instead of allow?

Damn, you are right.


My current relays setup:

- Chronicle relay for inbox/outbox/dm and backup all my conversations
- Wot-relay to access my social-graph notes
- Pyramid.fiatjaf.com as secondary WoT relay + OpenTimestamp
- Nostr.wine to let flow in events outside the WoT with a good spam protection
- A couple of big relays (nos.lol, damus) as outbox relays, without announcing them (Gossip feature)

This setup, together with clients that support the Outbox model (mandatory!), is working extremely well, zero spam, snappy clients and low bandwidth usage.

TL;DR; The Outbox model plus some WoT wizardly, wins


I think the problem is related to the fact that wot-relay accepts connections before the WoT is ready.
In Chronicle I updated the code to avoid that, but it's not a one-line refactoring. This is the starting point of the patch:
https://github.com/dtonon/chronicle/blob/main/main.go#L134-L155

Please check it, if it make sense for you, I can port the patch to wot-relay.


I think I found the bug, patch is coming soon


CATSTRR - a nostr relay that only accepts notes with cat pictures 😸

wss://catstrr.swarmstr.com

Powered by khatru framework by nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8g2lcy6q

Uses facebook/detr-resnet-50 for object detection.

Feedback/suggestions (future relay ideas) appreciated.

Source: https://github.com/ptrio42/catstrr


I just pushed a little but important optimization to properly accept reactions, zapping, and deletion for all notes included in conversations.

*** Important: the default storage is now Badger, so if you need to upgrade a running lmdb instance, please use the appropriate tags explained in the readme.

nostr:nevent1qqsqqqqq8f3e5dd42xu9n7nd8p0vnsy295dzfmld4f6ccal4nygt8sspzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgmwaehxw309a3ksun0de5kxmr99ej8gmmwdahzucm0d5hsnj5kd9


Did you read my previous note about "lists"?
We already have it: https://github.com/nostr-protocol/nips/blob/master/51.md


> That is what the word follow is used for in most social media.

True. Since we had no other tool, which is instead offered by Nostr.
It's all about a new paradigm and offering users a clear way to embrace it.

> Try making a new list type for your special use case like “people I trust” instead.

In this way you defend the legacy position of the usual social networks, to what end? A social graph is not just a feed, it is used and will be used in other contexts, such as checking the reliability of an application (see zap.store).


If publicly following someone is a “vote” and has a bearing on my social graph, I have to evaluate the content that this someone consumes and act accordingly. Of course we can have differing opinions on some issues, and that is fine, but some opinions for some people cannot have any mediation because they are deemed personally unacceptable. In this case unfollow is inevitable.
As already mentioned, there are lists (including private ones) to stay updated on any topic in a neutral way, that is untethered from repercussions on the social graph.
Obviously these are new dynamics, nothing is “right” by definition, but the one mentioned seems to me a good breakdown.

At the UI/UX level it could simply be handled with two different actions, e.g., “Follow” and “Add to my read feed.”
You would not "follow" Taylor Swift but you would keep her on your reading list (named "garden snails").


I see, and make sense, but there are lists for that, right?
I suppose lists are the correct tool to manage content without touching the social graph.


Content can be a proxy for the trust, and in fact it usually is.


Why not?


Spell with me: j-o-k-e
But maybe not, actually, it is an option.


nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 how did this airdropper infiltrate your WoT?
We need an option to automatically unfollow the weak links in the chain, haha

https://image.nostr.build/1ce9e7ec8d802ea931ae6e81654ecec9fadf299f14fcbd532e28caf3ee56974e.png

656769ed2e26d887b430c319c1c0d8fefe0c5c491d4d39eb8823a4aa29733a37


https://follows.nostr.com

The usual suspect


If anyone out there is currently dissatisfied with their nostr client, may I humbly suggest Coracle. It is stable, reasonably fast, and has better feed customization than anyone else. It also now comes in "android" flavor as well.


It should be better now.
Thanks for reporting!


A bit. Work in progress. Please be patient.


It could help communication to users, especially for paid relays.
In addition it could allow to point to a relay without knowing the domain, thus enabling easy domain switch, which would increase resistance to censorship.
Perhaps there are other uses.


What is the status of the proposal to assign a pubkey to relays?


You have waited patiently for this moment.


Maybe add also a "followed" label?


Good question: you need an open relay for that, this currently is the only easy way to "infiltrate" the web of trust.

There are other possible solutions, such as whitelist notes with some PoW, or create an invite mechanism, but they all require some form of agreement by the clients.

By the way this is a limit of all WoT relays. I'm planning to make the WoT check optional and add other filters (keywords, pow, nip-05).
This should help to have a more flexible configuration, still keeping a good amount of protection.


Does it support Amber?


"It means we are actually building a decentralised protocol, not just acting out decentralisation theatre"

nostr:nevent1qqszq47dgyfsaszxhx4yz63lhnz65eeldhmeztgsau27cevvp9s7unqppemhxue69uhkummn9ekx7mp0qgszrq3cgvfe89vadjrp0gaa3xfs82txpx6y5ezwjuufzqu20h5xytgrqsqqqqqpdpveha


I was thinking about that, it's actually a pain.
We can aggregate data, but we loose the signature, so it's useless. Perhaps one solution is to somehow use a Merkle tree structure?
Or maybe reactions are not so important.


> Will nostr require a consortium similar to W3C who maintain the http protocol?

> Can their nsec be linked to face id?

/ nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgnwaehxw309amk7apww468smewdahx2tckuej4c left the room

😂


A NIP-32 label with a PoW invite, attached to the user kind:0?


The concept of “dumb relay,” as it was initially coined, in my opinion should be framed in terms of minimum and necessary functionality. The backbone of Nostr must be able to sustain itself with relays that expose the minimum functionality provided by NIP-01, each addition being a bonus, cooperating with what clients can make available.
This is not a matter of shifting workloads from one end to the other, but of seeking synergy, where the result is richer than the algebraic sum of the two parts.
There will inevitably be overlaps, redundancies, and that is good, as this is also in its way a form of decentralization on the relay-client axis.


> 1) Trolls will `@` their way onto your relay. It's a loophole you should be careful about using.

Chronicle protects you from that, unless the mention is within the conversation you are partecipating, and the troll is in the WoT. Actually, WoT would be sufficient.


True!


What is this, the "relay release day"?! 😀
Great!


Only if the bot is in your web of trust (so if it is followed by you or someone you follow).


Forgot: thanks to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 for making it possible and fun to create custom relays, and special credit to nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 for the WoT idea/code!


While everyone is getting nervous about spam, say hello to Chronicle!

https://github.com/dtonon/chronicle

Chronicle is Nostr personal relay, built on the Khatru framework, that stores complete conversations in which the owner has taken part and nothing else: pure signal.
This is possible since writing is limited to the threads in which the owner has partecipated (either as an original poster or with a reply/zap/reaction), and only to his trusted network (WoT), to protect against spam.

Chronicle fits well in the Outbox model, so you can use it as your read/write relay, and it also automatically becomes a space-efficient backup relay.

Try it out, and let me know if you find it useful and how it can be improved!


Relay Wizard now let's you choose between multiple relay implementations, including a nip29 relay that supports groups. If you have a relay you'd like to see implemented let me know. Try it out at relaywizard.com #grownostr #relays

If you don't even know where to get started with setting up a server or hooking up a domain name you can also check out relayrunner.org

https://video.nostr.build/610d5da76e5aca6874213adf8fd0ff3ad1c47efed2d23f199b18fe5c9c42649c.mp4


I see.
Maybe you can create a simple command line tool to quey a large set of relays and create the nevent.


Why? Which is the use case?


Actually, I don't know. Probably to incentivize the use of hints. I need to check better.


I confirm that relay.notr.band is not used to look up raw hex ids.


What I was looking for, I plan to make a khatru + blossom bundle, thanks.


If the note was sent to a relay that njump does not know about, it cannot find it and therefore converts it to a nevent. The note was sent to relay.damus.io?


Your mentioned a hex id, not an nevent. What take a long time to load?
All events or just the ones you created manually?


Maybe the first time? For me this url loads instantly now.
I don't see any https -> http redirect; actually the inverse redirect takes place.


Try again now


This seems pretty scary...


Ok, now I understand the "time window" logic. I was thinking about the usefulness of the block hash alone.


An interesting use case, but I doubt anyone would put themselves in such a position!


Hahaha, legit


Can you give an example where this latter attestation might be useful? Usually the need is to prove that something is _older_ than X.


In your note you said the inverse, adding the block hash as a tag. And I can actually create an event today, with yesterday's date, adding a yesterday's block hash.


How can this help with past events? They can easily be forged.


I just tried watching live TV for 10 minutes. Global is less punishing


Coming soon to Gossip:

nostr:nevent1qqsvejfxvvluyyfwmcru8vgff85cndup928zggfhnyj4ns7j4cf40hspypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgswaehxw309ajjumn0wvhxcmmv9uqsuamnwvaz7tmwdaejumr0dshs9easp8


I told you that kind:1 must not render markdown! 😄


Enjoy the nature!


# and @ are the only easily accessible keyboard characters that have a “block” design and so are easily recognized without getting in the way of the next word.

I would use a double #:
##venice

Or maybe !#:
!#venice
(slower to activate, but ! remind the map pin)


The wot network includes your contact list and the contact list of those you are following, so two degrees. It is not configurable.


Add wot.dtonon.com


Interesting. Probably the attestation can happen as optional step after following the user, and be included in the follow list (kind 2). This would make the adoption easier.


Probably when name and display_name differ, and the client shows only display_name.
In this case NIP-05 functions as a name substitute.


Helping, fixing and serving represent three different ways of seeing life.
When you help, you see life as weak.
When you fix, you see life as broken.
When you serve, you see life as whole.
Fixing and helping may be the work of the ego, and service the work of the soul.

-- Rachel Naomi Remen
from the "The will to live & other mysteries"

Here we often call it "building".
Let's do it.


More replies


Interesting approach, but it seems resource intensive (calculate images hashes or similarities for all the social graph is heavy) and I suspect it can be quite fragile. Probably WoT is quicker and safer. Btw, NIP-05 is not involved here, even if it can be used to compose the final score.


Uh, nostr-wasm makes a difference


I know it is for identification, except for rare cases, in fact few weeks ago I updated NIP-05 to clarify that.

And that is precisely why there is no point in showing it everywhere, especially if it is invalid. The point is to simplify the interface (I know, I won you over here, haha) and avoid exposing a detail that is unnecessary and may indeed be confusing.

Intead in the profile, with a proper explanation, it can be useful to debug misconfigurations or have a clearer idea about what the profile is trying to do.

What is this impersonator tag?


It's open.

nostr:nevent1qqsr5u3hyccd2ysy3mrjp62z4c8nvrulgghc3lg86p6afnds9kyaflcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsfxxa6s


https://github.com/mikedilger/gossip/blob/master/filter.example.rhai

- - - - - -

This is a sample spam filtering script for the gossip nostr
client. The language is called Rhai, details are at:
https:rhai.rs/book/

For gossip to find your spam filtering script, put it in your
gossip profile directory. See
   https:docs.rs/dirs/latest/dirs/fn.data_dir.html
to find the base directory. A subdirectory "gossip" is your
gossip data directory which for most people is their profile
directory too. (Note: if you use a GOSSIP_PROFILE, you'll need
to put it one directory deeper into that profile directory).

This filter is used to filter out and refuse to process incoming
events as they flow in from relays, and also to filter which
events get displayed in certain circumstances. It is only run on
feed-displayable event kinds, and only events by authors you are
not following. In case of error, nothing is filtered.

You must define a function called 'filter' which returns one of
these constant values:

  DENY (the event is filtered out)
  ALLOW (the event is allowed through)
  MUTE (the event is filtered out, and the author is
        automatically muted)

Your script will be provided the following:

  caller        - a string that is one of "Process", "Thread",
                  "Inbox" or "Global" indicating which part of
                  the code is running your script
  content       - the event content as a string
  id            - the event ID, as a hex string
  kind          - the event kind as an integer
  muted         - if the author is in your mute list
  name          - if we have it, the name of the author (or your
                  petname), else an empty string
  nip05valid    - whether nip05 is valid for the author, as a
                  boolean
  pow           - the Proof of Work on the event
  pubkey        - the event author public key, as a hex string
  seconds_known - the number of seconds that the author of the
                  event has been known to gossip
  spamsafe      - true only if the event came in from a relay
                  marked as SpamSafe during Process (even if the
                  global setting for SpamSafe is off)


All clients flag a NIP-05 in some visual way if it is invalid. This can happens for a misconfiguration but more frequently when someone try to impersonate. The problem is that this "flag" (e.g. green/red icon, open/closed lock) is not always obvious, also because it is often next to the profile picture, and newcomers may be confused and deceived. Moreover, an incorrect NIP-05 does not always correspond to spam/scam, so it cannot be further highlighted.

Best pratice proposal: just hide invalid NIP-05s in feeds and threads, and show them only in the profiles, with a proper description of the problem.

#nostrdesign


Of course, in fact it is used for identification.


Gossip + Spam filter by rhai script = Relief & Zen mode

Terrific feature nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c


Test replies


nostr:npub17nd4yu9anyd3004pumgrtazaacujjxwzj36thtqsxskjy0r5urgqf6950x nice brand placement

https://image.nostr.build/ac08253690edc7563070237183b0055593398fe880b13771edd32a2cd4160225.png


The grants will continue until morale improves. Nostr Arduino, White Noise, futr, Notedeck, Keystache. More to come.
https://opensats.org/blog/7th-wave-of-nostr-grants


Web-Of-Trust
It is based on the social graph, the connection with people through those you follow directly. It can be used to 'weigh' the trustworthiness of people and then build a spam filter.
Since WoT filters can block unknown people outside your social graph, you can mix it with other techniques to whitelist exceptions, for example PoW (proof of work), some form of payment, profile and text analysis, and so on.
All this refers to the clients' side, on the relays' side we can enforce networks filters and other kinds of analysis.

Thank you for using Nostr :)


But unfortunately they do not (yet) apply WoT within threads.


Usually a newcomer is invited to join Nostr, even if only indirectly by reading an article or watching a video or talk. For the few who start from scratch, clients usually suggest a few people to follow or automatically follow the developer. Basically you always have someone to build wot.

But the point here is that without a sensible filter newcomers get confused, and runs away. The only alternative I can see is a single relay with good spam filters bundled in a client; but it's not very Nostr style.


Yes, it's a surreal mess.


Coracle and Vojage for sure, I am trying to find out if there are others.


The next step in the spam attack: "catch-all" domains to produce valid NIP-05s. Be ready.
Just a reminder that NIP-05 does not verify.


Any client without a life-saving WoT filter is doomed. And it should be forbidden to suggest one to a newcomer.


Digital signatures and how to avoid them
https://neilmadden.blog/2024/09/18/digital-signatures-and-how-to-avoid-them/


Hello from Coracle Android


Two weeks ™


I'm quite busy right now, but If you can't find anyone else feel free to ping me :)


Actually this happened also to me with an old version of Amber and a recent one of Amethyst. Updating Amber solved everything.


Buggy? Why?
I never had a problem.


> Web-development was a mistake.

Don't trigger me, please.


The top banner should not occupy the exact height of the viewport, otherwise the user don't understand that the page is scrollable. Make it 90% and maybe add a slow pulsing arrow that point downward at the bottom.


- The menu is absent on mobile


Looks nice, a quick feedback:
- I would increase the paragraph font size a bit, on dark backgrounds the text is less readable;
- On mobile, I would replace the horizontal carousel with a vertical structure, so the content is immediately visible;


Uh che bello, un po' di informazione in italiano su Nostr, bravi!


And the pow level can also be updated (increased) over time, if needed (will be necessary).


The problem is that it is not backward compatible for existing npubs.
One solution could be to use a NIP-32 tag signed with pow referring to the profile. This way, everyone can validate their own npub.
This also allows one to 'whitelist' someone else, for instance someone who has been invited to join Nostr, making onboarding easier and more pleasant.


I'm ready 😅


https://image.nostr.build/27950a4f01284e235ed5356cf90038e53e7697688f4e05dde9beee8571ac5cff.jpg

https://image.nostr.build/1fa8079eb0896844f4c7827fba869e3c5b61377c7dfa354ced396c7a479bc0b0.jpg


Check it out, HRF just announced their list of grantees, and Coracle is on it!

https://www.nobsbitcoin.com/hrf-bitcoin-development-fund-grants-10-btc-to-20-projects-worldwide/

Related: I'm looking for a contractor to help me push Coracle's development forward. Please get in touch via my job posting if you're interested in working together!

https://bitcoinerjobs.com/job/1561575-web-application-developer


Trying to put together a T-shirt design for Coracle, any designers/illustrators want to take a stab? Will pay/zap.

Here are a few AI-generated images that approximate what I'm going for.
https://image.nostr.build/35c6ff139a65e1154a55658cda0247659388d0f79830aceb1f545aa47b1b0c7d.jpg
https://image.nostr.build/3b44f69152d5a00f449a832af4bee520a4ae5256ecca7d2718fd5251cf12f785.jpg
https://image.nostr.build/eb4d9384935d6504ed2da4dfe8cc337bbbc69cb1df157239f7b151ca6e9d7914.jpg
https://image.nostr.build/3a8906581680e614a9cb8a16cbe688118cf7d9d3dd6f6dd6d721f634feef73d0.jpg
https://image.nostr.build/37d4d9299fabaddcdcf922f9429daf8ace08bb1876136bfbe7d1139bd7c2ca78.jpg
https://image.nostr.build/826f5baf82a7da159d3f932842c3e9e4248da094872571728d8918ec3e41e802.jpg


Probably a dumb phone is too brutal, and insecure. A better option would be a smartphone installing only a few essential apps and an anti-addiction launcher. I find that https://github.com/tanujnotes/Olauncher is really good in this respect.
But as always, it depends first on the person's needs.
Another problem is to minimize the physical presence of the phone, it is quite difficult to find a good compact/light phone nowadays.


Yes, it's what clients currently do.


I agree. Relays can work at the network level by eliminating the most obvious attacks, while clients can offer fine-tuning preferences to strengthen filters as needed.


NIP-05 should be use to identify an user, not to verify it. A signed NIP-05 would be rendundant.


And it will find a mismatching public key.


It could be, but they require their own app. Nonsense.


Let's say your profile is on all the bot lists.
The average user sees less spam. Unless they follow you!


Unfortunately, many banks require an app for 2FA.


Probably Evgeny Poberezkin by “resistance to censorship” refers exclusively to public messages that need to be spread as widely as possible, but this is not the only case.


If not face-to-face, each communication requires an intermediary to store/deliver the message. Censorship resistance, defined as the ability to resist suppression or modification of a message (private or public), could help by eliminating the one point of weakness and thus increasing deliverability and system performance.
I think we should first agree on the meaning of "censorship resistence" and "privacy".


Why?


Censorship resistance and privacy, are they really mutually exclusive?

nostr:nevent1qqs82u5gxj95wdnv822my8a4l7duhjvltchdvpyafg3q2efkdv8f5cgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygzwhzp3p445ak2ud4n289dn6084txu9ltkg7a53mt75qk5jup2ad5psgqqqqqqsujat99


You can  use the sandboxed version of Google Services shipped with Graphene, maybe on a separate profile, and with a throwaway account.


What do you mean with "replace"?
On GrapheneOS you can install any Android app, but with a really strong permission management.


njump.me


Fixed.


It seems a bug, I will check, thanks for reporting.


Habits forge misunderstandings.
It is not obvious how one should live in a world of free speech.

nostr:nevent1qqs2ufq3y85w3ya7jx4e7utfssjfq98kyupt3nj9duq2zvw2gs8qvngpzpmhxue69uhkummnw3ezumt0d5hsygq9qvjw6hur526kj2z78ea7gxcpr0x7d0hg6tj0wvhn0czwnx3tpgpsgqqqqqqsw7m00x


nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr Primal's CDN doesn't apply any optimization, right? Some images are hitting hard at 7MB each. Maybe a sensible resize could be a good idea both for the end user ux and your bandwidth costs.


Welcome Alex, keep building and working for a better world! 🫂


Check Midori.


There are a lot of good quality brands around, usually the most important point is choosing an acid-free paper. Then the choice is also related to what you use to write, e.g. pencil, pen or fountain pen.
Btw, I always choose notebooks with dotted pages, I find them very pleasant to write and sketch.


nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc, no pressure 😅


So go on and build! :)


It is rather inaccurate, we have a lot of cli/server software and developers working freely or with their own business strategies.


njump.me has clickable tags now: https://cdn.satellite.earth/dd1712f9164738e30a06d98c6929764cef1ea071a28a18ef758d6bb47b235bc0.png

This is clearly an Earth-shattering event.


GM Nostr. 🌞

I feel like we're on the brink of something really really big here. The planets are aligning, the momentum is building. The world needs Nostr (and just might be ready to hear and act on that fact).

Enjoy this part. The before. The beginning. It feels scrappy and fragile; all the features are broken, we're not sure it's going to work at all. But in a few years we'll all be longing for this period again. 🫂


OpenSats is proud to provide long-term support for Jason Donenfeld, a pivotal figure in developing essential cryptographic and networking tools.
https://opensats.org/blog/jason-donenfeld-lts-grant


Hahaha


Good question.
They call it "deactivaction", and after 30 days the account is deleted, but they don't say what happens to the data. I will search if there is any GDPR procedure to request a full deletion of all data associated with my account; this should be possibile by law, IF I don't accepted some small fonts conditions where I allow them to keep and use the data perpetually.


As stated in my previous note, I cannot understand how a webview inside a bot is easier than a link opened with the user's browser. Please elaborate.


Same problem here, Android/Chromium.


It looks nice, but doees it really help to enter Nostr? I tested it a little bit and it doesn't seem to have any particular integration with the chat, it's a only a webview within Telegram, or am I missing something?
Is joining a Telegram bot really easier thant redirecting to the corresponding website (https://nostrx.xyz/)?
I think we should invite users to *move out* from Telegram, asap, don't keep them comfortably there.

I don't want to be a killjoy; it's just honest feedback. Keep building :)


I have just started running nostr:nprofile1qqsp2k6lqqqw5uyaeaaeayjd22yu9rymg9ntqsu66kplcc9uu75khtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzfmhxue69uhk7enxvd5xz6tw9ec82cspz3mhxue69uhhyetvv9ujumn0wd68ytnzvuawauwv and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz's cellar.nostr.wine which is not going to delete them -- and to some other relays.

Somehow this will protect the humanity against the AI takeover in the future, so I recommend other people to do the same with other events. The source code is at https://git.fiatjaf.com/ots_nbot and you can customize the relays, kinds and authors it tries to timestamp, among other things, via environment variables.

If you don't understand how such a simple gesture has such immense powers, listen to Antihashed Podcast episode where this is explained, or ask nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw.


That's really cool.


Congrats Mike!


Well done!
Mine was also from 2008/2009, no regrets.


Really cool!


Breathing exercises.

Example: 4 seconds of inhalation, 8 seconds holding, 8 seconds of exhalation 4 seconds holding.
Inhale first with the diaphragm and then ascend, exhale first from the chest and then descend.


Domains are a frightening weak point.
https://labs.watchtowr.com/we-spent-20-to-achieve-rce-and-accidentally-became-the-admins-of-mobi/


Just now I realised I still had a Twitter account, Nostr made me completely forget about all the other useless social media.
Problem fixed, a little less entropy in the universe and more free speech signal.
 https://image.nostr.build/7faea713046e008c70d03f82d84f6b70bcaed0f250133f1580af0ef1d6e7c264.jpg

nostr:nevent1qqs8xqp5ymdtcj2g3l5sxpqpg4eyd0sjtklw8s5s0v6y0e72z6u2z8cpz9mhxue69uhkummnw3ezuamfdejj7q3qqny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysxpqqqqqqzs6c26y


The telegram version works, the web one is blank, weird.


Perhaps a data-only sim with SimpleX?


Hahaha
I'm tempted by one of these:

https://www.seeedstudio.com/SenseCAP-Card-Tracker-T1000-E-for-Meshtastic-p-5913.html

https://muzi.works/products/h1-complete-device-heltec-v3-running-meshtastic


Welcome!


Why did you choose the this hardware?
I am still looking for the best choice.


A robust client that doesn't suck your time and improve the signal, try it

nostr:nevent1qqsd5qjm8ge0f7fpxyznqnt0awm0vdaeuv7y3unwvu9w4nx60fnqqzgpzpmhxue69uhkummnw3ezumt0d5hsyg8yxdkd2fwl08ay6whnvn7evqx5kyxuuss44fxr8mthagyyydztzqpsgqqqqqqs8jvtdl
nostr:nevent1qqsd5qjm8ge0f7fpxyznqnt0awm0vdaeuv7y3unwvu9w4nx60fnqqzgpzpmhxue69uhkummnw3ezumt0d5hsyg8yxdkd2fwl08ay6whnvn7evqx5kyxuuss44fxr8mthagyyydztzqpsgqqqqqqs8jvtdl
nostr:nevent1qqsd5qjm8ge0f7fpxyznqnt0awm0vdaeuv7y3unwvu9w4nx60fnqqzgpzpmhxue69uhkummnw3ezumt0d5hsyg8yxdkd2fwl08ay6whnvn7evqx5kyxuuss44fxr8mthagyyydztzqpsgqqqqqqs8jvtdl


Full dump of nostr events collected by nostr.band crawler for you to play with (550Gb): https://media.nostr.band/events.jsonl.gz

If you wanted to do research, data analytics, calculate stats, etc - that's your chance.

Contents:
- 550Gb of nostr events in jsonl format, gzipped
- no data about source relay
- some event kinds are absent (DMs, other encrypted stuff, ephemeral)
- some duplicates are possible

Will publish regular updates on this data set if someone makes anything useful out of it.

Thanks nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p for the push.


It's from the creator of Redis 👀


#meshtastic people, what do you think about https://github.com/antirez/freakwan ?


And FreakWan:
https://github.com/antirez/freakwan

From Salvatore, creator of Redis


Gossip toolbox 🔥

nostr:naddr1qqdryvpjxscrjvf39438jefdvfuk2ttjv4cxc7fdva6hjq3qacg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeysxpqqqp65wksr8ar


Hahaha


I have to start populating Italy...


Your own note 😂


Njump currently renders images, but only if they are on their own line. I will try to see if I can improve the parser to manage inline urls, but it's not a priority given that most clients format them correctly on upload.


You need  also the contributor's branch, plus adding the new origin:
```
git push contributor local_branch:contributor_branch
```
Yes, quite pita.


Uh, is it not enabled by default? Bad UI.

https://github.com/mikedilger/gossip/issues/851


Hahaha
Just few days ago I found out a plain solution without the gh client:
`git fetch origin pull/<PR_number>/head:local_branch`


No, it also works directly with naked relays, just as with a tor browser one can visit any website.


The mentioned problem is related to the "old" NIP-04 specs, with which DMs leak metadata. The new NIP-17 version is safe.
Tor has no role in this.


Probably you don't have Orbot running as proxy. This update will remove this additional step.


It depends on whether Orbot is used as a VPN or as a proxy. In the former case, the application cannot escape Tor, in the latter case it can of course, avoiding using the proxy.
So Orbot as VPN is safer than current Amethyst's implementation, while the new built-in support has the same robustness, but avoid a dependency and all the troubles related to the configuration, offering a better experience to the user.


> Emojis are up to interpretation by the viewer and may not always be interpreted to mean what the originating poster intended. This is just the nature of symbols, culture and context.

Exactly. See the 🤌 case.


I'm quite surprised that Amethyst creates a reaction on the user's behalf; I really don't see the utility and, as you explained, this action can have severe consequences.

I didn't know about this Amethyst automatism since I don't usually report using kind 1984, exactly to avoid being linked to questionable content.
I think nostr:npub12m2t8433p7kmw22t0uzp426xn30lezv3kxcmxvvcrwt2y3hk4ejsvre68j is a good solution.

Finally, if you really must choose a negative reaction, why not use “-” as NIP-25 requires? At least clients would hopefully not show these notes as pinned content in the user's profile.


Follower counts must die: nostr:nevent1qqsva7cvqg50mq58qf4g7d993235fp3nawt2z59v4drqd5d9uhx9y9qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyqy2ts


ReplyGuy spam sucks, however it's allowing for the emergence of a stronger and more robust Nostr. If we have a wide open communication protocol, that means that anyone and everyone can participate if they choose to do so. ReplyGuy is nothing. Trust me. It's so insignificant compared to what's coming in the future. ReplyGuy is a wake-up call to developers, but also to users too. None of us should be complacent when we need to be vigilant with our social communication. This is a mere scrimmage for what's coming down the road. Use this time to build solutions. Use this practice game to fine tune your relays.

You can choose paid relays or choose smaller community relays, such as those built on WoT or other metrics.

We have a lot of choices for paid relays. Maybe you'll use nostr:nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzamhxue69uhkxun9v968ytnwdaehgu3wwa5kuegprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qyt8wumn8ghj76twvfhhstnwdaehgu3wwa5kueg6jsgtg's wss://nostr.wine or nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpzpmhxue69uhkummnw3ezumrpdejqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd8wgv5w's wss://nostr.land as your paid relays. You can find more at https://nostr.watch by nostr:nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az72445kh.

What are WoT relays? These are a semi-new concept. They can be invite only or they can be constructed via a person's personal Web-of-Trust follow list.

For example: You use use wss://pyramid.fiatjaf.com by nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp if you are invited by an existing user.  Additionally, you can use wss://wot.utxo.one or wss://nostrelites.org if you're in the Web-of-Trust of either nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7znxpeu or myself. (Meaning one of us follows you or one of the people we follow follows you, going one layer deep in our social connection.)

More WoT relays will pop-up or already do exist.

As the outbox model grows and gains popularity, smaller community relays will become the normal way that people use Nostr the most, IMO.

If you're a relay operator that's combatting spam, feel free to shill it down below in the comments.


> and load all the event ids individually

So two REQ instead of one. I am happy if this is not a burden.


For testing, a service could actually be useful. But filtering notes tagged by a third party should be definitely more complex, right?


But nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd saw them as PRs, and so collaboration:

> Multiple tips: The git graph has multiple tips, symbolizing multiple PRs ahead of the central master branch. This really represents gitworkshop as a place to view, discuss, and collaborate on code proposals.

The versatility of logos :)


To me it looks like they are diverging, it reminds me more of a fork than a collaborative situation.


I suppose that the tagging UI is quite trivial, you just need an single icon that iterates the languages in loop when pressed. And many users will have just one language, so they do not have to touch anything after the onboarding.
Then using a service you cannot "upgrade" to the region labeling, and you have to manage the incorrect detection issue; finally a service have be manteined and be economically sostenibile. Better to offload this easy task to the users.


Nice.
I probably would rotate the git workflow 180°: usually a git history has the the most recent commits at the top, and display a merge highlights collaboration.


It's exactly what I'm proposing :) In fact I mentioned NIP-32.
The group of clients embracing this idea is just to offer an interoperable feature, and so collect more feedbacks.


Be curious :)


I don't think any client has tried this. Such an experiment should be tested by a client with a large user base; or better with an interoperability orientation, by a pool of clients, so to bring in different types of users and points of view.
In addition this is an addition that doesn't cause any incompatibility issue to the protocol, it can easily be deprecated by clients if it shows little utility. It's not even necessary to touch the NIPs, it's sufficient to take advantage of NIP-32 labels.

In brief:

1) When logging in and creating the account, the user can choose one or more languages.
2) When browsing a feed the user can select a language to filter the notes.
3) When the user enters a thread from a filtered feed, the client shows all the notes by default, and if possible it translates replies to the original language used in the feed; in addition the user can force a language filter at thread level, too.
2) When posting a note the user can indicate what language it is using, by selecting one of the preselected ones; optionally the client can detect the used language and select it automatically, allowing the user correct the choice.

A slightly more complex version, from a user interface perspective, may include not only the language but also the region; and this also is backward compatible using NIP-32 and simply *adding* an ISO-639-2 tag to the basic ISO-639-1 one (since relays cannot filter by prefix, right?).


The solution is quite obvious: let the user specifying his own language, use it in a tag, and let the user optionally filter/download only the selected content.
Local bubbles can be a problem in the long term but are important for welcoming new users, especially if they are not able to speak a foreign language.
Knowing that this option is standard, would make people more inclined to freely switch language when posting, truly enriching the linguistic and cultural presence in the network, and so promoting Nostro locally.
Instead now most use only English, this proves something is not working right.


Anche io scrivo solo in inglese, ma questo purtroppo porta un appiattimento linguistico e crea anche una barriera d'accesso non indifferente.


This


I agree. And I have said so from the beginning. It was thought that language-specific relays might help, but that seems impractical in the short term. And we really need good onboarding and experience to create momentum.


Hahaha, yes a bit desktop maximalist.
But the explanation is well done.


This is promising:
https://how-nostr-works.pages.dev/#/outbox


Very long thread with some interesting thinking on the current login patterns via email:
https://news.ycombinator.com/item?id=41475218

Certainly the management of a private key is more complex and requires well-crafted procedures, that we are still fine-tuning with Nostr. But at least when it is ready, we will be able to offer an open, bigcorp-free single sign-in procedure and free users from the madness of many passwords.


Hola! 🥳


Correct, I missed the "you trust". I should read better before replying haha, sorry


I like gray hair, it communicates naturalness and self-confidence, if it is well groomed.


Not always true, an impersonator can easily create thousand of followers.


Sorry very much, my fault, I didn't see you mentioned them at the beginning of the sentence. I was thinking you was asking us for a feedback just using the picture!

This is a case where the nip-05 helps as verification tool: nostr:nprofile1qqsvnx99ww0sfall7gpv2jtz4ftc9v6wevgdd7g4hh7awkpfvwlezugpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsg5cway's nip-05 uses the official SimpleX domain, so it's the correct one. This is a better indicator than any followers count.
The other one is an account from a Mastodon bridge, maybe it also legit, I cannot say.

Sorry again for the poor response caused by my distraction.


Inspiring thinking, thanks for sharing.


How can you ask for an account verification just using the name and a profile picture? Npub is the way.


This seems a good starting point:

nostr:nevent1qqsyw79njmwtxzz6l6mx8az49hx3dcnqqfu0dj3ukqharvzkr8mavrcpr9mhxue69uhkymmnw3ezumn0ddhhgctjduhxxmmd9uq2a0fw


Cool!


Web of Trust Relay:

This relay looks at who you follow, and who they follow, and saves every note in this trust network automatically.

I added it as my only relay in amethyst and spam is now completely gone.

Anyone in my web of trust can use my relay:

wss://wot.utxo.one

But the much better solution for nostr is to run your own WoT relay

https://github.com/bitvora/wot-relay

ps I'm faster than nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp


Add xDBupZD as additional string, it matches the profile pic


Sorry, I didn't take note before updating.
Maybe I was just using a quite old version.
PS: an integrated notification of new versions could be a good feature for sensitive apps like Amber.


I just updated Amber and now the problem seems to have been solved.
Before, when I was composing a note, every few characters Amber would slide in and out automatically, it was a mess.
The nip44 problem is different, it was already there, the remember flag is not respected.


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z after this update the combo Amethyst + Amber is unusable, there are constant transitions between the two apps, maybe the culprit is "Adds sliding animations in all inner screens"?

Then there is still the problem of nip-44 decription: the permission is not remembered and it pops up randomly. Maybe something related to Amber? nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5


Yes, I talked about the client perspective but the relay part is also really important, of course. As you say, at relay side things are harder since they don't have direct access to the social graph.

The usual proposals here seem to point to PoW, a payment or an invitation, to unlock access. But I fear that all these approaches could create a lot of friction and slow down onboarding.

Even network filtering does not seem very effective, when you have disposable key pairs and VPNs.

I would avoid to delegate to AI this job, this would really escalate to an AI vs AI fight.

Do you have any other ideas?


I agree that we should start restrictive, a first filter by WoT should be sufficient, then we can mix other variables.
Also the UI should adapt, for example temporary hiding instead of filtering out completely, to let the user dig in false positive and unlock them.


ReplyGuy Is evolving, a positive stimulus for relay and clients to improve their filter capabilities.


Crazy.
But actually they can be benefit from Nostr, they should only pay attention to use or bootstrap relays in other countries.


I ask those who have been there. When you haven't dreamed for months and you start again with some crazy idea concerning Nostr and in the dream you try to convince the people you're working with... is it good or a complete burnout? 😅


Why?


Sure, in fact NIP-05 was recently updated to highlight also this edge case:
https://github.com/nostr-protocol/nips/blob/master/05.md#identification-not-verification


I love what nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy is doing with npub.pro and nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk with Oracolo and nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p  with Ditto - making it easy for people to have their own corner on Nostr will encourage more people to get their own NIP05 and expand the web of trust.

It’s like a cypherpunk geocities/myspace hybrid forming here