https://nostr-delete.vercel.app

Sorry, I heard Failcoin was trademarked by ETH.

Please avoid login with nsec. It’s teaching bad habits for private keys, that flow into Bitcoin too.

Something I’m looking forward to. I’ve only logged into a couple bot/service accounts (like NostrGraph Archive) once. Would love to be able to build a following for side accounts for people who are interested in that space, and post less maybe on this account.

Yep. Happy to contribute if we open a GitHub issue.

I think it needs refinement before striving for more adoption. A new NIP is an alternative, however likely a harder route and just noise… when we can cover way more use cases by amending 42.

I’ve been using a slight modification for web app logins. The only real difference is I send the same event by POST, and call the relay Tag origin, as it’s more generic. Only issue is for browser extension UX that kind is called Relay Auth… which is weird to hear for a webapp.

It also lacks the option for a client to request an AUTH challenge if one has never been sent.

Maybe AUTH is only needed for write, yet a clients can’t ask for a challenge before they first write. They’d have to auth even just to read - which isn’t ideal privacy wise. Unless your relay requires auth to read - again possible.

I think you’re best to split it per app. Likely different authors for the PRs.

What’s the spec?

* add enable AUTH toggle option to settings

* for each AUTH event, sign an AUTH response and publish to that relay.

One issue with the spec is that is doesn’t seem to specify if an AUTH challenge (specifically the first one) is blocking - can you still read/write before responding with an AUTH response? Do you need to queue up all other requests until you first send AUTH?

I think the answer is it depends. The spec likely needs clarification around this.

Here is likely where you’d inject an AUTH response in Damus.

https://github.com/damus-io/damus/blob/02fc065005738abbc84fe8102a48a0e0903f8624/damus/Nostr/RelayPool.swift#L252

Like an /n/AIArt would be an awesome channel. Posts are new images. Maybe a media gallery view type. Zaps go to poster. And comments or conversation fits below. Like stacker news for example.

I don’t know of anyone.

It seems that since Jan, everyone has been focused solely on the kind 1 use case (for client apps), and all channel/group stuff went on hold.

There are some tough issues to solve like how would moderation work. I know we have a count kinds defined, but you really need to be able to delegate moderation, not just have a channel creator or something.

And I only mention moderation because things like off topic posts and other stuff are painful without some kind of moderation. If you don’t like that channel, start your own.

This is most likely a relay selection or connectivity issue on your end.

I’m not aware of any clients who block or mute posts - unless 3 or more people you follow have reported them, or you blocked or muted them yourself.

If they really are spam events, it’s possible relay operators have a spam filter that takes a few messages to trigger, but removes the previous messages as a cleanup.

Not a chat room.

But, it could be used as a channel, posts and comments setup.

Subreddits/topic = kind 41

Posts = channel messages kind 42

Replies to posts = kind 1

Ranking posts and then replies can make sense once you have enough volume.

Agreed.

The Arc iOS app was a good start for channels. It was full of spam and it was too hard to find people actually using a channel.. 99% are dead.

It’s a weird mix between Chatroom channels and chat messages - and like a reddit post and then related comments.

I don’t think we have seen solid UX yet.

It’s also the hardest to manage content ranking, as you can’t just use your following list. It’s the Wild Wild West and you have to rank or filter content differently.

G’day Fernando

Did you say “LinkedIn”?

Here’s five reasons why your colleagues are friends with ransoms from other countries, that somehow know you too, and want to join your network.

—

We’ll just need to add a cost factor to make it prohibitively expensive to try build bot farms (even other human farms, and with a high cost of it gets found out/discovered.

Experimenting and this is badass. On a per event basis, we can get both a timeline of engagement and map it against relay broadcasting of the event too.

With government based currencies, we live no differently to the Medieval times - with kings and nobles, served by pagans and peasants (the people.. us). They control your land, they force you to use their tokens, they devalue your tokens, they tell you what age you can retire (withholding funds), they make laws without the people's consultation or consideration, etc.

When this realisation hits you.. and you remember just how prehistoric and barbaric the medieval times actually were...  why should this be acceptable to anyone?

For Nostr builders, don’t forget there are plenty of $200-250 USD free credits by VPS/Cloud service provides (often 2 month expiry) you can use to help reduce costs.

I don’t care who you use, but here are two examples. Not affiliate links.

https://www.vultr.com/coupons/

https://try.digitalocean.com/freetrialoffer/

This is now life with a new change log page. https://nostrgraph.net/dashboard/changelog

The oldest event I have is this.

2023-01-11 20:07:33.000 +0100

JB was likely the first app to support it, so maybe check release notes for Damus.

https://api.nostrgraph.net/beta/events/76772834388e8f8993cc247f8aeb7ebed4211663e804f368cbd499672559955d.json?pretty=true