nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy8hwumn8ghj7mn0wd68ytnddaksz9rhwden5te0wfjkccte9ehx7um5wghxyec4uepvf how did you implement encrypted zaps for NIP 24? Seems like you would need the zapper to support NIP 59
who wants some previews of #newpinstr ? 👀 what do you think ?
https://nostr.build/av/3ce80436a019ab878eabf3fed89c209b212b49e3593eafc6d4aeccabf40367ac.mov
Looks really good
Nice to unplug for a weekend
Pretty sure once I write a DVM there will be no turning back
The lists a relay applies has implications for its users — this might be a service, but is more likely to be a hindrance, because it's easier to apply more filters, but not so easy to un-filter results.
Using lists makes sense, but applying mute lists is probably not a good idea, since you can mute something for multiple different reasons, which is why I mention NIP 32, it gives you the granularity you need to make a more educated filtering decision.
I’ve been thinking deeply about content moderation on Nostr.
I’m very pro-freedom-tech but there are problems we will need to solve to scale and be acceptable to a wider audience of user.
To help get the ball rolling on improving Nostr’s ability to keep bad actors from poisoning the well here’s a proposal for a freedom maximising strategy for dealing with illegal or just insanity content (as determined by Nostr users)
I know this’ll be controversial so I’m looking for feedback and refinements before trying to build something to get this ball rolling.
https://gregwhite.blog/nostr-content-moderation/
Cc nostr:npub1yye4qu6qrgcsejghnl36wl5kvecsel0kxr0ass8ewtqc8gjykxkssdhmd0
I'm glad you're looking into working on this! In my opinion, blacklist providers (and their integration into relays and clients) should be as conservative as possible (limited to illegal content, or inline with a special-purpose relay's mission). For other type of "unsavory" content, you should look into NIP-32, which was built to support multiple ontologies for content classification and rating. I think that will be a much better solution for web-of-trust content recommendations and soft moderation.
Going to spend the morning making a Thread component for NDK to properly render the nuance of nostr threads in an attempt to make nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc happy
GM!
This is extremely hard. What approach are you going to take?
Few things are harder than having a kid in the hospital. I'll be praying for him and you.
closest I can give you 😂
https://zaplife.lol/p/npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
It's a start
Please welcome Spring - the nostr browser.
This is the first public Android release, we're submitting to the Play Store, but an APK is ready for you to try: https://github.com/nostrband/nostr-universe/releases/download/v0.1.0/spring-nostr-browser-v0.1.0.apk
The app is open source: https://github.com/nostrband/nostr-universe/
We believe this category of a Nostr-specific browser is a very powerful tool for all the nostriches and bitcoiners. It takes the experience of using Nostr micro-apps to the next level, and should help accelerate the adoption of non-social Nostr use cases.
Some screenshots are here:
If you hesitate to paste your nsec into the app, we totally get it - just use your (or someone else's) npub to log in and look around. However, if you do add your real keys - those are handled by a separate library, stored in an encrypted form and protected by the Android keystore, inaccessible to any JS code, immune to XSS or app-level bugs.
What you can do today:
- add nsec keys or npubs, switch between keys
- browse various interesting events on the homepage - trending stuff, suggested profiles, big zaps, highlights, long posts, live streams, nostr web apps
- open any event in any web app that supports this event kind and has been published on nostr using NIP-89
- open/close/hide the browser tabs, grouped by app/domain
- log in inside the opened apps as if you have the 'browser extension' (nip-07 interface injected into tabs)
- pin apps/tabs to your app "drawer" for fast access
- access your contact list at the search page, profiles sorted by recently-accessed first
- search through profiles, notes and long posts
- tab menu - if there is an event-id/npub in the url of the opened tab, you can zap the event, or open with another app from the menu (more coming soon)
- context menu - if you long-tap on a link with event-id/npub in the url, you can zap/open-with from the context menu
- nostr: links clicked inside a tab are handled by showing a list of apps that support this event (NIP-89)
- long-tap on a text selection with event-id/npub to open the context menu to zap/open-with
- paste a url to the search bar to open it in a new tab
- paste an event-id/npub into the search bar to open it in a new tab
IMPORTANT: nostr apps running inside the browser tabs can sign events and decrypt private messages without a confirmation screen and your explicit permission - do not use apps you don't trust until we implement proper app permission management.
What is coming:
- key access permission management
- reordering of pins in the app drawer
- more event kinds on the homepage
- search for more event kinds
- tab switcher screen
- NWC to inject WebLN into tabs
- custom feeds on the home screen
- custom tab/context menu items
- DVMs for translation, transcription etc
- and much more!
What do you think?
Plopped my private key in there because I trust you. Coracle and others work flawlessly, I love the idea of a dashboard and accessibility to so many pwas at your fingertips. The completely invisible nip 07 integration is so refreshing. This is a game changer.
Has anyone done a "supporters" view with a historical view of who has zapped you the most? Like zap.life but for your profile.