You have to look for it in specific places, normally the coffee its average and very frequently barmans burns the coffee 😬
Nostre v0.1.1 'That's a memorable link?'
https://nostree.me/gzuuus@nostree.me
One of the most requested requirements since nostree saw the light was human readable urls, or links that you could easily share, memorable and easily sharable. They're here!
Now you can use your nostr address (nip05) to share your profile, like for example nostree.me/gzuuus@nostree.me, you can try yours, don't forget to share it ;)
Other updates have been:
- Share button in the profile, for mobile browsers.
- Swipe gesture, now you can simply swipe left or right in the profile list to switch between profiles.
- Improved mobile view and different interface improvements.
- Minor bug fixes
Just moved the connect function to onmount. Lets see if that fixes it 👍
Ill look in to it, thanks for the feedback! Appreciate it all :)
Gn🌛
Nostre v0.1.1 'That's a memorable link?'
https://nostree.me/gzuuus@nostree.me
One of the most requested requirements since nostree saw the light was human readable urls, or links that you could easily share, memorable and easily sharable. They're here!
Now you can use your nostr address (nip05) to share your profile, like for example nostree.me/gzuuus@nostree.me, you can try yours, don't forget to share it ;)
Other updates have been:
- Share button in the profile, for mobile browsers.
- Swipe gesture, now you can simply swipe left or right in the profile list to switch between profiles.
- Improved mobile view and different interface improvements.
- Minor bug fixes
Ok I work in public.
In the next iterations of nostree I will be working on:
--[v0.1.x]--
- Adding hashtags to lists, and other possible standard nip 12 tags, like 'g' for geolocation (may make sense)
- Human readable urls through nip05 (ex. nostree.me/random@nostrich.com) and vanityuris (ex. nostree.me/random)
- Separate urls for lists, to be able to share only specific lists
- Implementation of indexDB
- Create guides for user use, 'how to nostree'.
- Improve the explore section with filters to see only lists of your follows, filter by hashtags and more.
- UI/UX improvements
- Folders and subfolders of link lists
- Write extension for nip 51 to standardise kind 30303
- SEO improvements
- Add cookies
--[v0.2.x]--
- Edit profile option
- Use nip78 for user custom settings (Custom Theme and colours)
- relayset customization, and implementation of "gossip model".
....
Send love💜
Consuming content since i have memory. Films, books, tv, toys... Content its everywhere. Important thing how you consume it and be conscious about it. Highly recommend the book 'The Ephemeral Era: Gilles Lipovetsky
Yes, if its free prepare yourself to a potential leak of your data for whatever reason. My choice in this case its mullvad because all the auth sys its based in a number and yo don't give them even an email. Also and v important, you can pay it w btc, ln o onchain
Yes, a non free one, free ones are not reliable. Mullvad, ivpn like the better options
I just get in front of the pc today, all day outside, time to get drunk and hit this mf keyboard 🤟
### #Amethyst v0.73.1-alpha: New Private Message & Small Groups Protocol
This is an **alpha** release of the new GiftWrapped DMs. Please do not consider anything to be actually private until we have a **stable** version. This is early and there might be bugs that leak information.
You can activate this mode by clicking on the Incognito icon on the Chat screen. For now, only Amethyst supports this NIP. Thus we recommend only testing with other Amethyst users. Coracle and 0xChat are finishing their implementations in the upcoming days/weeks.
The claims of this new method are:
- Messages are encrypted with a superior XChaCha algorithm to each participant's public key individually.
- Chat participant identities, each message's real date and time, event kinds, and other tags are all hidden from the public.
- Senders and receivers cannot be linked with public information alone.
- Minimal trust in counterparties: Counterparties cannot expose verifiable details of your message, including the metadata, without exposing their entire user and all of their other messages (private key)
- There is no central queue, channel or otherwise converging event id to link or count all messages in the same group.
- There is no moderation role (i.e. no group admins, no invitations or bans)
- There is no chatroom secret that can leak or be mistakenly shared
- Messages can be fully recoverable in any client (that implements NIP-24) with the receiver or the sender's private key
- The protocol's messages can flow through public relays without loss of privacy. Private relays can increase privacy further, but they are not needed.
- The protocol is extensible to make any other event kind fully private (private likes, private reports, private long-form content, etc)
This implementation is very similar to how Slack manages direct DMs to multiple users. If three users are having a conversation and want to add a fourth person, the forth's user will not see the past. This guarantees maximum privacy: only the receivers of a message at the time of writing will ever be able to decrypt it.
In the near future, we will implement Forward Secrecy through:
- Users will be able to opt-in for "Disappearing Messages" that are not recoverable with their private key
- Users will be able to also opt-in to sharing messages with a new key exclusive for DM backup and recovery.
Details:
- Support for NIP-24 Private Messages and Small Groups
- Support for NIP-59 Gift Wraps & Seals
- Support for NIP-44 Versioned Encrypted Payloads
- Support for XChaCha encryption algorithm
- Fix: Loading of Alby's NWC URI
- Fix: Only requests notification permission once.
- Fix: Show reposts and reactions in search
- Fix: Signed byte used for array slice inside the TLV by nostr:npub1xpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9ms275ams
- Fix: Global feed only shows events from Global-active relays by nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h
- Updates Dutch translations by nostr:npub1w4la29u3zv09r6crx5u8yxax0ffxgekzdm2egzjkjckef7xc83fs0ftxcd
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.73.1/amethyst-googleplay-universal-v0.73.1.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.73.1/amethyst-fdroid-universal-v0.73.1.apk)
Probably password manager no? since it's a newer idea. And nostr suffers from accessible authentication methods that people can use to log in
Both are very interesting projects don't get me wrong:)
I'm going to take a look now, I'm very interested 👀
Introducing...
NOSTR URL shortener
A free URL shortener service enabled by the NOSTR protocol, that is fast and fuss-free, stripped of all bells and whistles and gimmicks.
It just works!
https://nostr-url-shortener.vercel.app/
What I need help with:
- community to decide a short domain name
- a sponsor for the domain
- designs and logo
- just test it
Open source GitHub repo:
Wow nice! New kind 1994, could be good to write a nip for that to be standardized
It describes how to use relays dynamically. The user has a list of recommended relays (kind 1002) and clients (like gossip https://github.com/mikedilger/gossip ) use these to fetch information.
Vaya, perece que nostr:npub1q03juraj84sn323nchqg25ywcsuuzj60zl4f72thy69eph3xt24qc5622l no admite nombres de usuario largos como los que tiene el bridge https://mostr.pub/ de nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 y me ha cortado el usuario de nostr:npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds
Cc: nostr:npub1ln54yvwdtp88j8cltkthe6kpaahdk0f60g56mfdx27tesdktev0st7737w
😂