I think
@AQSTR and
@zapwork are highly interesting... I tested aqstr today, and the tasks were indeed almost instantly detected as done, and immediately paid out. I have to admit that is very cool!
I think there's value in things like this, but I also wonder about the validating effort beyond what can be automatically gauged.
For example, asking people to like, reply, repost or quote... these are fine and good. But I'd consider these "micro tasks". What about more high value things, like:
- Submitting a PR to a git repo.
- Uploading a picture of you doing something.
- Writing a more in-depth post about a topic.
Part of me feels like an element of manual validation may be required for higher value tasks.
As for
@zapwork, I think this is also a highly interesting take in terms of online recruitment for jobs. There's nothing much posted there yet, but from the application process, it feels like it could be a good match for some jobs such as copywriting, or ad-hoc stuff.
Particularly where reputation/trust metrics can be used.
Interesting space that's developing! Really neat to see it on #nostr!
We have migrated all event data over as well, so if you were using the superfriends relay before, your data should still all be here. Everything should work exactly as it did, except much more performant! This means feeds load much faster, events read/write much faster, and less error-prone.
As always, anyone is welcome to use it: wss://nostr.superfriends.online
nostr-rs-relay has been fantastic over the years, but the backend on sqlite3 was a major bottleneck for public relays. Even with loads of fine-tuning, there is only so much you can do with sqlite3, particularly if hosting a public relay (I think it's great for private/small relays!)
I like that strfry uses LMDB which is much faster and scalable. It also is more actively maintained and has some great tooling built in for plugins and extensibility.
If you have any problems, please let me know.
Enjoy! 😻💾
View quoted note →
It's very clear what the way forward is, however it's down to universal robust implementation from the various clients and usage of personal relays (or at least trusted ones where you can delete).
