With AI bots flooding the internet, online reviews and forums have become polluted and full of noise. When words cost nearly nothing, anyone can drown out signal at scale.
Revis is an open-source review platform that fixes this using Bitcoin and nostr.
Your reviews are backed by sats that you and other users attach to them using NIP-57 zaps with ratings.
Revis is:
- Spam-proof: Creating noise has a cost, and filtering it is trivial.
- Censorship-resistant: Built on Nostr. No one can delete or censor your reviews.
- Decentralized: No central authority. Your opinions and reputation are yours.
- Bitcoin-native: Lightning-powered. No fiat. No shitcoins.
Mark your words, back them with sats.
Website: https://revis.social
Source code: https://github.com/aftermath2/revis
Any feedback or contributions very welcome!
is "energy-backed" becoming buzzword for "uses Bitcoin"?
I understand the chain of reasoning, I simply don't like it because there are so many indirections between the energy expenditure by miners and the value at the time of zapping, that the linkage is incredibly loose.
Bitcoin is money and money is a way of, among other things, storing time and energy. Zaps are just a way to transfer those to another entity.
no, money stores neither time nor energy reliably.
money is fungible gratitude
... I noticed that your entire git history is one commit
did you squash in preparation for the release?
these days, it's a bit of a "smoking gun" that the codebase was obtained [e.g. by vibe coding, or purchased from a contractor] rather than crafted organically by an open-source collaboration.
Yes, the repository was previously private and I decided to clean it up upon public release. I'm not sure whether it is possible to make any assumptions based on the git history, but you can check my open-source contributions and other projects in my profile.
thanks, I'm not judging you for not disclosing the raw commit history...
squashing the entire thing into one commit isn't really "cleaning", though, is it?
I hope you haven't run
git gcand maybe kept a tag[1] on the pre-squashHEADpointer.please consider queuing a read of
man git-bisectfor some relaxed day, preferably before you actually need to use it...if you haven't and are a little panicky, just check
git reflog show, and it should list way more commit IDs than you'll ever need, including the relevant one ↩