How dare people send out warnings about people they may not want to do business with entering a market! Do you even free speech, bro?
Dr. The Daniel ๐Ÿ––'s avatar Dr. The Daniel ๐Ÿ––
How dare a successful entrepreneur attempt to build a business on an open protocol! Do you even free market, bro? View quoted note โ†’
View quoted note →

Replies (9)

Nsec harvesting. DMs. Viewing and access patterns aren't public unless you are replying. Plus all the risks of the app attempting the typical on your device privacy invading stuff. You are fine to say this is all acceptable risk to you even when it is a known data harvester. Still, informed consent requires being informed. Don't shit on others for sharing information.
I've seen nothing to indicate this in the public web app source, and harvesting nsecs would be the most severe violation imaginable. Let me just ask point blank, then: @Nostrich Will you open source your mobile apps so users can be absolutely clear on what information, if any, is being collected? If not, why not?
Nostr is a public protocol, and all public data is freely accessible to anyone. You don't need a client to access it. Nostrich doesn't even operate a relay, which stores far more data than a client that simply serves as an interface to the protocol. As for the source code, we've released it under the MIT license on GitHub. The code currently available powers all our applications, including Nostrich mobile apps and Nostrich Deck, since they're all built on the same web application and packaged using WebView. There are no separate native codebases. The only native components in our mobile apps are the bottom navigation and app menus, which we implemented natively for better performance and a smoother user experience. It's entirely up to users whether to use our apps. There are plenty of alternatives, and that's the beauty and freedom that come with Nostr.
Yes, you can use the repo currently available on GitHub. It's about a month behind the current release. We've made some minor UI changes and performance optimizations since then, which we'll push to GitHub soon to bring it in sync with the current version.
โ†‘