The answer would depend on your definition of a 'nostr app', let's assume you mean 'why use login with Nostr if you're not building a micro-blogging social media app?'.
If you need some identity system in your app, you generally have two options:
- build your own system, ask users for email and password, etc
- use big centralized providers like Google/Facebook/Github, etc.
With Nostr you have another option, decentralized and built on cryptographic keys, not a closed centralized database with emails and passwords.
If users login with Nostr you can fetch their profile, their following list, their other public data, to personalize the experience in your app, to train your AIs, etc.
If you app has important 'social' component, then you might have an easier start with Nostr where people already have some social graph.
And you can use Nostr for some social parts (comments, reviews, etc) and use your traditional app backend for the rest of it.
Nostr usage in your app is not all or nothing, it's a wide spectrum.
I'm sorry to say that you have 32bit CPU (ARMv7), and I only build for 64bit versions. There are quite a few libraries I need to compile myself to build the app, and supporting several architectures is too much work for me at the moment. If you leave your email at the website I will notify you when the 32-bit build is ready.
Thank you for your interest and feedback, it means a lot to me!
The primary difference is that Syncthing is focusing on synchronization, meaning that some files/folders take space on both devices and are kept in sync. It's essentially a cron-ed rsync (Dropbox is built around the same concept internally).
Recall is primarily a file server. The analogy that I have is that it's a zero-config FTP server with a web client with a nicer UX. Auto-sync of select files is on my roadmap, but at this point it's just a 'remote access to your files in a browser'.
Another big diff is that Syncthing is open source, so it's security and privacy are verifiable. Recall is closed source at this point (although you could peek at the JS client to figure out how it works), and I'm not yet ready to make a promise to open it in the near future. So, be aware.
Thank you for your kind words, I really appreciate that!
Connect your devices once, set permissions, and you can list/search/open/download files from connected devices, over any network (Android only for now).
Search files across devices, it detects text on images and speech in video/audio, making them searchable.
Privacy is great, connection is end-to-end encrypted, search does all processing on device.
Hi everyone, the subj is an Android app that I'm working on, that has mostly replaced a file explorer for me. The app is called Recall. All file explorers are about file location - folder, file name, etc, which you generally don't know or choose when you take pictures or download files.
Recall is about search, it indexes the file contents in the background and let's you search through content. It also recognizes text on images pretty well, so is really helpful with pictures of documents or screenshots.
I'm currently considering whether to keep working on this thing, so please help me decide in comments :)
Great point. Not sure about state channels, but there are proposals for the Lightning Network. You could reveal a packet of data inside the payment confirmation itself, so it becomes atomic [1]. However, there are still issues: throughput, obviously, but then there needs to be a way to check the packet of data for correctness.
It definitely is a variation of that belief. Could you elaborate on why it is mistaken?
I think:
1. Whether something is valuable can only be discovered if you try to set a price and sell it. Until then, you can not know.
2. LinkedIn has big part of it's business selling 'InMail' at around 2$ per piece. So clearly some people's attention is so important that strangers do pay money to send them mail.
I guess so. Seeder would need to send us a lightning invoice, and after we make a payment we'd repeat the request with a proof of payment and the seeder would send us the next chunk of data. AFAIK Bittorrent protocols are quite extensible, and adding such metadata should be possible. However, this (paid torrent seeding) only makes economic sense if all seeders demand payment, and then the cheapest ones will be winning, driving prices close to zero.
Nice idea anyways, great to see people experimenting in the space!
Right! But this time is a little different:
- with Lightning Network fees are actually low, compared to on-chain
- no need for a new email account, instead you can add inbox fee to existing email
- full privacy, as your data never leaves your device, and payments are anonymous
I guess that's mostly because there was no way to do it without intermediaries (banks, paypal etc). Which means that a) fees are generally too high to process micro-payments, b) payment processors require KYC and that's too much pain for a single-shot micro payment, plus your privacy is leaking. Some crypto projects are trying to fix this, but I don't think any of them is ready for 'normal' users.
If you need some identity system in your app, you generally have two options: - build your own system, ask users for email and password, etc - use big centralized providers like Google/Facebook/Github, etc.
With Nostr you have another option, decentralized and built on cryptographic keys, not a closed centralized database with emails and passwords.
If users login with Nostr you can fetch their profile, their following list, their other public data, to personalize the experience in your app, to train your AIs, etc.
If you app has important 'social' component, then you might have an easier start with Nostr where people already have some social graph.
And you can use Nostr for some social parts (comments, reviews, etc) and use your traditional app backend for the rest of it.
Nostr usage in your app is not all or nothing, it's a wide spectrum.