Avatar
🫥
f5c60627da0f155e7b494b7722b3c2cd17aff7b8cc9f9a5344ebdb056c53d50b

Lobesters "face" looks like how I would imagine some alien creature.

Realized what happend, the article's author is on my block list so that is likely the reason behind that there is just an empty space there until a press reply.

I'd like to disagree that they are gamifications, as reactions are a simple and quick way to give feedback and zaps are great value 4 value option. But you do you man, if people want to participate let them, if you want to build it into the app do it is your app.

I think most of these "features" are there to make people addicted to games grind hard for nothing, which I think is not needed here and would be annoying but it couldn't be enforced to participate in this stuff beacuse you can do anything in nostr and you cannot be forced into this things by "a platform owner". Some people just need to go out and touch some grass and find events, and achivements in real life.

I mean request to join or invite only and maybe a "sticky" relay (that the community is restricted to a relay hosted by community members) or the use of encryption.

Replying to Avatar reya

A new version of Lume has been released. You can download here https://lume.nu

It's mark a milestone of Lume and of me. But the my work isn't stop here, a lot of exciting things will come to Lume in future, stay tuned for more updates

Roadmap v1.1.0: https://github.com/luminous-devs/lume/issues/46

You should add a link to the github repo on your site.

What about extension or desktop/phone apps, software. It would be way harder to push any malicious code out as you can have update being restricted to only signed updates that means the doesn't need to trust the server where they get the update from, which is not true for web apps, everytime using webapp they could be served with malicious code. I am not sure about what kind of update security extensions have but with desktop apps and on android this could be achived. The thing with other providers like facebook, twitter and etc is that they do not store an encryption key, if the password gets leaked they can always change it in their db( after they verified the user), which is not possible here as the only verification (and the "source of truth") is the private key.

Replying to Avatar jb55

false

so you going to have dozens of runtimes and compliers?

Than it's going to be impossible to implement and standardize it.