Avatar
Freakoverse
3cea4806b1e1a9829d30d5cb8a78011d4271c6474eb31531ec91f28110fe3f40
I guess I'm one of those #vtubers. Having fun talking about general topics, vrchat/similar, and games. Also #indiedev #gamedev. You can call me: Freak فْرِيكٌ フリク (still learning Nihongo). #envtuber #podcast #gaming #gamedev

People think 'to replace' when they hear/see edit, and that's where people on Nostr are think 'lol no'. But if it's a new post that gets added on top of the OP, and repeats as we see it's history, and replies being attached to whoever version they replied to, is fine imo.

Books sold + under the table deals + 10 to 20% markup on total

On one hand, for my client, making URLs sexy again by making it short and readable is desirable, tho on the other hand I don't want to remove those addresses in case the client domain gets nuked and those shared across the net sexy links won't mean anything anymore / the user can't grab the address to put it on another client.

So sticking with unsexy addresses in favor of ease of interoperability/sharing + in case of client/project nuke.

Reading this and replies, I'm wondering why there's negativity surrounding this?

I got this new protocol explained to me, and I looked into what I can of it, and my end conclusion was: cool, I can put my nostr project/site on this as a backup, along with on Nostr/Nomen combo (another option) just in case ICANN screws me over.

It's silly to get angry at devs who don't nessarily want to work/build on Nostr (/on insert-thing-you-thing-is-important). That kind of contradicts the idea of freedom if you're really for it (similar to people who say something like 'if you don't defend freedom here, the last bastion of freedom, then freedom is lost' some will, some don't. If it's lost then it'll be regained at the same place or somewhere else, if needed enough).

Enjoy freedoms from all angles and make use of what you think is good imo =3

Yeah I'm not saying to have nosterizer requirements and you did great on that.

Though I think the UX issue present here (and you probably already know it) is that of a preventative measure against user error where they might lose their purchases because of incompetence or a lack of knowledge.

I guess I would see this as "perfect", as a buyer pov, if I see a note mentioning the local save part and a warning that I might lose what I've purchased if I'm not careful and it, and mentioning that it would be advisable to log in with nostr and have my purchase get attached to my address with the receipt being saved on relays, so that I would know that my purchases can be retrieved, authenticated, and accessible later on, on any device.

On a different note (UX):

I'm assuming if I lost the link to the already paid content, I can't see it again, yes?

Would be neat if there's a Nostr integration in this, so that I can open a page to see all of the purchases of content I made.

When you see a "test" post on #nostr , it's usually either a:

1. New user checking things out

2. Dev testing out a new feature (or fixing a bug)

Would be cool if someone creates a nip where users can tag any type of nostr post (short, long, ecomm, etc) with custom words.

Similar words adds to it's number.

#nostr

I think this is more like scared as fuck I need protection mentality x3

Got one Amber-like thing design wise (not done / not sure when it'd be done, since it's aiming to be expand on Amber currently does. Looking forward to sharing it when design ready =3)

Ya that's what I noticed too.

When I mentioned I'd see if I can bring it back to life is by implementing it, to be the first nostr client to implement seriously, hit up the creator to soft get back into it as a result and help a bit with financial burned as well as help with designs, and depending on the success of my client it would bring attention to Nomen in the scene (both positive and negative since it got shot down), then hopefully we'd see if it'd properly live or not.

How I see Nomen is just that, a simple name indexer with an end user cost of cheap to expensive depending on traffic, and I wouldn't want control of who takes names and wouldn't want expirations on names either (if someone took google, and the actual company wants the name but aren't successful in buying it off the person, then their name would be google:1 or google:2, depending on when they got the name). Of course it'd also be used as a handle for nostr users.

In regards to how people would check for names, well, a lot of people are already running Bitcoin full nodes, so a one time scan then keeping it running along with the node would be it. Sites/apps would link to such scanners to fetch names and that's it.

One question I had in mind though, regarding pubky, is why another keypairs? Couldn't it be built on top of nostr and use it's keys?