Why Nostr? What is Njump?
2024-10-31 14:50:18

TheGrinder on Nostr: This week on #nostr. Vitor Pamplona wrote a piece on relay management ...

This week on #nostr.

wrote a piece on relay management
quoting

If you don’t know where your posts are, you might as well just stay in the centralized Twitter. You either take control of your relay lists, or they will control you. Amethyst offers several lists of relays for our users. We are going to go one by one to help clarify what they are and which options are best for each one.

Public Home/Outbox Relays

Home relays store all YOUR content: all your posts, likes, replies, lists, etc. It’s your home. Amethyst will send your posts here first. Your followers will use these relays to get new posts from you. So, if you don’t have anything there, they will not receive your updates.

Home relays must allow queries from anyone, ideally without the need to authenticate. They can limit writes to paid users without affecting anyone’s experience.

This list should have a maximum of 3 relays. More than that will only make your followers waste their mobile data getting your posts. Keep it simple. Out of the 3 relays, I recommend:

  • 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc.
  • 1 personal relay to store a copy of all your content in a place no one can delete. Go to relay.tools and never be censored again.
  • 1 really fast relay located in your country: paid options like http://nostr.wine are great

Do not include relays that block users from seeing posts in this list. If you do, no one will see your posts.

Public Inbox Relays

This relay type receives all replies, comments, likes, and zaps to your posts. If you are not getting notifications or you don’t see replies from your friends, it is likely because you don’t have the right setup here. If you are getting too much spam in your replies, it’s probably because your inbox relays are not protecting you enough. Paid relays can filter inbox spam out.

Inbox relays must allow anyone to write into them. It’s the opposite of the outbox relay. They can limit who can download the posts to their paid subscribers without affecting anyone’s experience.

This list should have a maximum of 3 relays as well. Again, keep it small. More than that will just make you spend more of your data plan downloading the same notifications from all these different servers. Out of the 3 relays, I recommend:

  • 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc.
  • 1 personal relay to store a copy of your notifications, invites, cashu tokens and zaps.
  • 1 really fast relay located in your country: go to nostr.watch and find relays in your country

Terrible options include:

  • nostr.wine should not be here.
  • filter.nostr.wine should not be here.
  • inbox.nostr.wine should not be here.

DM Inbox Relays

These are the relays used to receive DMs and private content. Others will use these relays to send DMs to you. If you don’t have it setup, you will miss DMs. DM Inbox relays should accept any message from anyone, but only allow you to download them.

Generally speaking, you only need 3 for reliability. One of them should be a personal relay to make sure you have a copy of all your messages. The others can be open if you want push notifications or closed if you want full privacy.

Good options are:

  • inbox.nostr.wine and auth.nostr1.com: anyone can send messages and only you can download. Not even our push notification server has access to them to notify you.
  • a personal relay to make sure no one can censor you. Advanced settings on personal relays can also store your DMs privately. Talk to your relay operator for more details.
  • a hidden, but public relay if you want DM notifications from our servers.

Make sure to add at least one public relay if you want to see DM notifications.

Private Home Relays

Private Relays are for things no one should see, like your drafts, lists, app settings, bookmarks etc. Ideally, these relays are either local or require authentication before posting AND downloading each user\’s content. There are no dedicated relays for this category yet, so I would use a local relay like Citrine on Android and a personal relay on relay.tools

Search relays:

This is the list of relays to use on Amethyst’s search and user tagging with @. Tagging and searching will not work if there is nothing here.. This option requires NIP-50 compliance from each relay. Hit the Default button to use all available options on existence today:

  • nostr.wine
  • relay.nostr.band
  • relay.noswhere.com

Local Relays:

This is your local storage. Everything will load faster if it comes from this relay. You should install Citrine on Android and write ws://localhost:4869 in this option.

General Relays:

This section contains the default relays used to download content from your follows. Notice how you can activate and deactivate the Home, Messages (old-style DMs), Chat (public chats), and Global options in each.

Keep 5-6 large relays on this list and activate them for as many categories (Home, Messages (old-style DMs), Chat, and Global) as possible.

Amethyst will provide additional recommendations to this list from your follows with information on which of your follows might need the additional relay in your list. Add them if you feel like you are missing their posts or if it is just taking too long to load them.

Final Considerations

Remember, relays can see what your Nostr client is requesting and downloading at all times. They can track what you see and see what you like. They can sell that information to the highest bidder, they can delete your content or content that a sponsor asked them to delete (like a negative review for instance) and they can censor you in any way they see fit. Before using any random free relay out there, make sure you trust its operator and you know its terms of service and privacy policies.


#AlbyGo 1.7 dropped
quoting

Alby Go ⚡ v1 .7 👀👀💪💪
https://github.com/getAlby/go/releases/tag/v1.7

#Yakihonne introduces smart widgets with 2.0. instantly jumped on it.
quoting




got some stats for us.
quoting

GM, Nostriches!
The latest Nostr Review biweekly report (Oct 15-27, 2024) is out, and this time we’ve enhanced it with Nostr Statistics to make our report even more comprehensive!
Check it out here: https://yakihonne.com/article/naddr1qvzqqqr4gupzqavxnnavfdqnx0p29h8vxtstenmds0wy5n0etkm6fs7sjdmgrxv8qq2j6kp52p6rz4z8f48kjetjfpfkw6t5xfn47vs5vl6
Quick review: In the past two weeks
* Nostr statistics show over 170,000 daily trusted pubkey events，approximately 29,000 users have profiles,more than 4 billion events have been published,total Zap activity reached over 11 million.
* 8 pull requests were submitted to the Nostr protocol, with 2 merged. Contributors include and more.
* 40 Nostr projects were tracked, with 12 updating their product developments. These include
@npub142gywvjkq0dv6nupggyn2euhx4nduwc7yz5f24ah9rpmunr2s39se3xrj @npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8
*Over 270 long-form articles have been published, 46% of which focus on Bitcoin and Nostr. Contributors include and more.
*During the same period, six notable events took place.
* Additionally, four upcoming events are on the horizon, such as the Bitcoin Culture Festival 2024, Bringing Nostr to LatAm，LaBitconf2024 ,Satsconf2024,Adopting Bitcoin2024. @npub1ejj803066dh93evzq4sgy02trxe30qna6tcdkx0vqdnmzywks3zsr5n006
@npub1ze93u0u37u3x0gnfffgxl33k60v7t3afs64jgzf4xznapr4ra5us0u3pxq
@npub1ad0ptuzte83alpkpqqctvewlaqj5zq23c83m82xw8apg4t6zlyns6xng2c
Thanks for reading! If there’s anything I missed, feel free to reach out and help enhance the completeness and accuracy of my coverage.

#YakiHonne 2.0 is live
quoting

Announcing YakiHonne 2.0: Simpler, Faster, and Built for Creators! This version brings two main improvements:

1. Complete Redesign:
• Onboarding: Easily create a non-custodial wallet with Npub & Nsec, experience zapping (Lightning payments), or browse as a guest.
• Home & Discover: “Discover” is designed for creators, focusing on rich formats like long-form content, videos, and curated works. “Home” offers a social feed with short notes and curated contents, making it quick and easy for creators to share their work.
• Wallet: Simple setup with easy creation, direct YakiHonne node linking, and multi-wallet support.
• Dashboard: Manage all published and drafted content, check stats, and pick up right where you left off—all in one place.
• Notifications: Reactions, Reposts, Mentions, Zaps, Comments, and Follows now appear in clear, categorized cards.
• Settings: Completely revamped for simplicity, now including profile customization, appearance, relay settings, and wallet management.

2. Enhanced Performance:
Our re-engineered core now supports the outbox model with extensive functionality. Furthermore, Thanks to PabloF7z we now have seamless data fetching, caching, and full support of the NDK implementation.

Hope you enjoy the new decentralized media experience! 🌐✨Try it out here::
•Web: yakihonne.com
•App Store (iOS): https://apps.apple.com/us/app/yakihonne/id6472556189
•Google Play (Android): https://play.google.com/store/apps/details?id=com.yakihonne.yakihonne&hl=en

Thank you for your incredible support on this decentralized media journey!



announces Haven 1.0
quoting

Haven v1.0.0 - now with Blossom Media Server!


Take full control of your media by running your own blossom media server with #haven.

What's new in v1.0.0
- Blossom Support
- Adds Gift Wrapped DM Support
- Removes Kind 4 DM Support
- GCP Backup Support
- Adds Delete Event Support to Inbox Relay
- Other Bug fixes and enhancements

We are yoloing to v1.0.0 because this is now the ultimate personal relay, what else could you need?

Enjoy nostr, h/t for adding blossom to khatru.

Get started today at https://github.com/bitvora/haven

PS: please add blossom upload support to amethyst brother <3

with a NostrHub update
quoting

So far

Achieved: Unified dashboard for all my Nostr apps.

In progress: Reducing domain dependency.

Added: Quick shortcuts for Nostr backups, publishing notes & blogs, and accessing zPay.live purchases.


#BTCPay 2.0 has landed
quoting

BTCPAY 2.0 IS OUT!!! 🚀

https://blog.btcpayserver.org/btcpay-server-2-0/



BTCPay Server 2.0 realigns the internal architecture with the lessons we’ve learned since 2017, positioning us to better support both plugin developers and ourselves as we implement new features.

🌎New interface localization
🧭New sidebar-only navigation
📲New onboarding flow for new users and Point Of Sale
🏬Three new e-commerce integrations @Wix, @Odoo & @BigCommerce
🙌Checkout v2 default
🎨Branding enhancements



While it may not seem immediately obvious, we expect users to see the full potential of 2.0 in the upcoming months, as the ecosystem continues to thrive and build on top of it. With BTCPay Server 2.0, we’re introducing breaking changes in our API that allow us to eliminate the technical debt that has accumulated over the years.

Updating to BTCPay Server 2.0 is a one-way process with no option for rolling back. Because of that, we're making it opt-in, requiring that you SSH into your server and run:

git fetch
git checkout 2.0
btcpay-update.sh

Seamless integration into existing systems remains one of our top priorities, and we’re excited to introduce three new e-commerce integrations that expand the possibilities for merchants:

- Wix
- Odoo
- BigCommerce

If you use plugins with your BTCPay Server, you might notice that some are disabled after updates - we do that to prevent server crashes.

If you use plugins with your BTCPay Server, you may notice that some are disabled following updates - we do this to prevent server crashes. If you rely heavily on plugins for your BTCPay operations, we recommend that you double-check compatibility and look for announcements from plugin developers regarding their support for version 2.0 before proceeding with the upgrade.

has updated their plugin, so take a look at it how they did it as an example.



In the end 💚 Thanks to all that contributed

With 2.0 we wanted to do all the hard work, most of which may be invisible, but it sets a great base on what we’re aiming to do in 2025. Keep an eye on the upcoming minor releases that we’ll ship if we notice any bugs. In the next few big releases we’re hoping to ship some of the most requested features that further enhance our mission.

Super-special shout out goes to our community testers, who went beyond and above testing the 2.0: @cypherpunkstore @JoinStrainly.

We hope you enjoy what this update has to offer. As always, thank you to our invaluable contributors, who directly participated in making 2.0 possible: @dstrukt @jackstar0512 @nisaba @TChileta

Final thanks - of course - goes to https://foundation.btcpayserver.org supporters who are ensuring our FOSS work is sustainable and are helping us make this tech available to everyone!



@BaillieGifford
@Tether_to

@LunaNode



@Unbank




goes all-in on #zapstream with the Bitcoin Podcast.
quoting

As is now tradition, THE #Bitcoin Podcast will be live streamed on #NostrOnly via zap.stream

Nostr will continue to be the ONLY place live streams are available for this show.


is working on a new r3emote signer and nsec bunker
quoting

GM! I have been building a new remote signer and bunker. So I decided to make some diagrams about NIP-46.

I think it's important to think about the RPC layer as separate from the Nostr Connect layer. This makes everything make so much more sense, and if you separate the two parts in your code the code is going to be more maintainable.



Multi-million dollar NGO planning to use GrapheneOS
quoting

#GrapheneOS device deployment and management was mentioned in the requirements for a director-level job vacancy in a large (multi-million) NGO about wildlife and environment preservation. Their overall security commitments outside of their mobile security demands is also very impressive.



It is great to see big organisations with big requirements choose GrapheneOS because they know we provide security and privacy other platforms do not have. For too long users with tougher security requirements were left in the dark because every commercial OEM is often thinking about seamlessness or user experience. Users should have the choice to go above.

Let it be a message to every exploit broker and mercenary who tries to use our name / the platforms we support for marketing an urgency to attack our work: You cannot claim your actions to be for the greater good. You want to target a project that protects people in organisations campaigning for a cause far more important than yours. GrapheneOS works for good while you arm oppressors who work agsinst causes like the ones above.

The security community's greatest principle is transparency and you can't claim yourself to be trailblazers when you keep research a secret and we will continue our work in spite.

talking about using nostr in Surianame
quoting

Here's , talking about using NOSTR in Suriname, as a tool for freedom and empowerment.

Sent her campaign some sats:
https://geyser.fund/project/maya2025


Amazing drone show in Lugano.
quoting

🇨🇭 Incredible #Bitcoin drone light show over Lugano, Switzerland! 🔥

#Coracle security issue, reported fixed by
quoting

**Security Update**

I've got some bad news for you guys. This morning, as I was adding error handling to flotilla, I discovered that Coracle has been sending user session objects to bugsnag when reporting errors.

Who is affected: Users who triggered an error in Coracle while signed in with their private key, since December 5th 2023.

What I've done:

- I immediately released a new version of Coracle, both to web and to zap.store
- I have deleted the affected apks from my releases
- I have deleted all my error data from bugsnag
- I have deleted my bugsnag project and rotated my api key, so lingering error reports will be dropped
- I have audited my code for use of the session object to ensure nothing else like this is happening

What you should do:

- If you're logged in with your private key, log out
- Hard refresh the page to ensure you have the latest version of Coracle

The bottom line is that if you signed in to Coracle with your private key, it has been shared with me and with bugsnag. In practical terms, your keys should still be secure, since they were sent over TLS, and have been deleted. But there is no guarantee I can offer that they are in fact gone.

I take my users' privacy seriously. My error reporting implementation doesn't record user IPs, it redacts identifying data, and it allows users to opt-out. I also warn the user when they attempt to enter an nsec into a text field. In this case, I simply screwed up, and I sincerely apologize. Reply to this note if you have any questions.

pushed an update to his inactive user tool. It now has bling!
quoting

!!~YEGHRO INACTIVE USERS CHECKER UPDATE~!!

My tool now glows.
It’s fucking dope.

I think we can all agree this is likely the most important update I could have possibly spent my time getting done.

Https://unfollow.yeghro.site

merged something into #nostter
quoting

So this was merged:





Try opening this note on https://nostter.app/ then clicking on
- wss://algo.utxo.one
- wss://catstrr.swarmstr.com
- wss://pyramid.fiatjaf.com
- wss://yabu.me
- wss://questions.swarmstr.com
- wss://labour.fiatjaf.com

/thread, Happy Weekend
Author Public Key
npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd
Seen on
wss://nos.lolwss://relay.damus.io