-
If it helps, it use to return `[]byte` and khatru Blossom's API own example was broken until a couple of weeks ago. It's ultimately Fiatjaf's decision of course, but, from my perspective, feel free go for it.
-
I’m using Mise to handle most of my dev tool needs. Not just downloading and managing different versions of my tools but also automating tasks like activating Python virtual environments and installing default packages; automatically setting JAVA_HOME (Java, Kotlin, Scala, etc.), handleing all the gazillion different (and almost equally awful) JavaScript runtimes and package managers; Rust/Cargo, Go, Ruby, Swift/SPM, and more. You name it, Mise handles it well.
Thankz to Mise I’ve uninstalled about half a dozen language-specific environment management tools and trimmed my .zshrc. By far one of the most underrated dev tools I’ve come across: https://mise.jdx.dev/
-
Thank you, Beave. Intention is what matters. I’ve probably been zapped about 10k sats since joining Nostr. Almost enough for a cup of coffee and a sausage roll where I live (though, of course, that’s if you don’t count the tens of thousands of sats I’ve zapped to others or the 100k or so lost experimenting with non-custodial Lightning :)). Absolute generational wealth being accumulated here on Nostr by pleb devs!
-
Thank you, kind madam, not only for the sats but also for your many contributions to the very same free internet tech I enjoy. From one non-local-celebrity dev to another: you are awesome!
-
I believe you. Thanks for trying anyway :)
-
GM, Nostr! ☕️☀️
Anyone up for zapping a non-celebrity developer a few million sats for their efforts fixing broken things around Nostr? V4V, right?
No? Worth a shot. Maybe next time?
Alright, thanks anyway!
https://image.nostr.build/25a7c56e832376dbeba4c39428c59c05180a98d6ee8cea69ce28c5e88306904e.jpg
#GM #GoodMorning #Nostr #Memestr #Devstr
-
GM!
-
Looking good! If you’re open to a small suggestion, and if fiatjaf doesn’t mind introducing some early-stage backwards-incompatible changes to khatru's Blossom’s API, I think you could simplify things by changing the return type here https://github.com/fiatjaf/khatru/blob/76ecf4f7914a93b7ec4f0cc0c823304a7402adab/blossom/server.go#L18 to `io.ReadSeeker`. This would allow you to eliminate the `io.Copy` fallback code and the `Content-Type` handling, as `http.ServeContent` also takes care of that for you. It even handles ETags and cache-related headers, so I’d expect your patch to significantly improve things for all clients—not just iOS. Well done!
-
"Editing kind 1 notes is bad [...] something, something [...] hard to implement [...] something, something [...] centralizing". He's automatically editing his posts to prove the point. If you are on Amethyst you can still click the post (only once) and see the original message. Or you can click the edited post a gazillion times for entertaining purposes.
-
I unintentionally forked the conversation above. I don't have an iOS device but happy to help if you get stuck :).
-
Try to replace `io.Copy` with `http.ServeContent` and see what happens (you can fork Khatru and use go to replace khatru dependency in Haven, this is how I tested all of the CORS stuff before)
-
https://pkg.go.dev/net/http#ServeContent - this is what you are looking for (it will handle partial byte ranges and all mentioned headers).
-
GM random Nostriche frwn. I hope you have a great day.
-
GM. Brilliant view.
-
GM Nostr! Happy Monday. 🥶🥱😋☕️💪🏃♂️
#GM #GoodMorning
-
GM fren!
-
GM 🍊🔥
-
GM!
-
GN Nostr! 🌙
-
GM!
-
I had to check 🤣 (this doesn't count folks using encrypted mute lists). Still a long way to go to reach Bluesky numbers.
https://nostrudel.ninja/#/u/npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424/muted-by
-
No need to compromise. Docker/Podman support is alive and well—just not in utxo's / bitvora's repo. Here's my repo, where I’ve been actively maintaining and improving containerization support:
https://github.com/aaccioly-open-source/haven/
Aside from ironing out bugs, I’ve improved the image build process so that rebuilding Haven’s image now takes only a few seconds on my hardware. Additionally, the final image is much smaller than before—just a few dozen megabytes depending on the platform, compared to the previous 1GB+.
The current image version is also (hopefully) more secure, as it can be run in a rootless Podman environment. The compose file includes a pre-configured Nginx reverse proxy and automatic HTTPS certificate renewal, similar to the version I previously contributed upstream.
nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3vamnwvaz7tmwdaehgu3dwfjkccte9eshqup0qyghwumn8ghj7mn0wd68ytnhd9hx2tcht4zgq also has a repo with Tor onion service support. He has applied a very similar set of optimisations to his repo's Dockerfile as I’ve applied to mine, so whichever version you choose, you’ll be in good hands.
-
GM!
-
GM Nostr! Today's mood in emojis: 🥱🥶🏠🐈⬛️
https://haven.accioly.social/21358377f7403ef290e8c233557f7651c7dcf92cb52e8d4dbfd1dc25896ec235.jpg
#GM #GoodMorning #Catstr #Caturday
-
GM. I hope the noisy neighbours are over with their Saturday morning "fun" :).
-
Fedora user with a "Gentoo" coffee setup here.
-
Yes, other from setting the proxy to use HTTP/1.1 and enabling 𝚔𝚎𝚎𝚙𝚊𝚕𝚒𝚟𝚎, Nginx requires additional tweaks to the HTTP 𝙲𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗 header: https://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive.
The instructions in the Nginx manual don’t seem to work well with WebSockets BTW. Fortunately, the nginx-proxy template bellow handles most of the heavy lifting, including workarounds for the 𝙲𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗 header:
https://github.com/nginx-proxy/nginx-proxy/blob/main/nginx.tmpl#L446-L473
I’ve just confirmed this by logging 𝚑𝚝𝚝𝚙.𝚁𝚎𝚚𝚞𝚎𝚜𝚝.𝙿𝚛𝚘𝚝𝚘 in Haven. It’s receiving HTTP/1.1 requests from Nginx. I suspect the reduction in CPU usage is due to fewer TCP sockets in 𝚃𝙸𝙼𝙴_𝚆𝙰𝙸𝚃 state.
-
𝐓𝐈𝐋: When acting as a reverse proxy, Nginx uses HTTP/1.0 and doesn’t enable 𝚔𝚎𝚎𝚙𝚊𝚕𝚒𝚟𝚎 (HTTP persistent connections) to upstream servers by default. My reverse proxy was happily responding to clients using HTTP/1.1 or HTTP/2.0 while still using HTTP/1.0 to connect to my personal relay.
I didn’t think it would make much of a difference, given that Nostr is WebSocket-based—i.e., HTTP connections are quickly upgraded with:
𝙲𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗: 𝚄𝚙𝚐𝚛𝚊𝚍𝚎
𝚄𝚙𝚐𝚛𝚊𝚍𝚎: 𝚠𝚎𝚋𝚜𝚘𝚌𝚔𝚎𝚝
Plus, my personal relay isn’t exactly handling a lot of traffic.
Nevertheless, configuring a small number of cached connections apparently reduced CPU usage, not only for Nginx but also for Haven itself. The more you know...
I’ve enabled persistent connections for Nginx on my Haven repo and merged nostr:npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz's latest contribution from upstream. Do let me know if you encounter any issues.
https://www.f5.com/company/blog/nginx/avoiding-top-10-nginx-configuration-mistakes#no-keepalives
#Haven #Nginx #HTTP #ReverseProxy #WebSockets #Nostr
-
There’s not a lot of money coming to devs from user Zaps, unfortunately. There’s also not much goodwill from alternative funding schemes or experienced OSS devs, thanks to Nostr’s reputation as an ad board and marketing tool for crypto companies.
As it is, the Nostr network self-selects for these companies and their potential customers, mass producing content that’s basically boring to everyone else.
The few users who stick around mostly give up on Kind 1 notes and retreat into closed communities. There might be a handful of people willing to play the role of activists or post other types of content regularly, but these are exceptions that prove the rule. You can't really curate your feed for content that isn't there. Algorithms won’t fix this either—it’s not a content discovery problem; it’s a community self-selection problem.
This isn’t some big secret or shady crypto conspiracy, though. Phrases like “The purple pill helps the orange pill go down” and “Keep Nostr weird” are some of the most popular Nostr influencer slogans. Even assuming good faith (and I know there are genuinely enthusiastic Bitcoin folks who aren’t out to profit off new users, as well as people who sincerely enjoy Nostr weirdness), the network’s self-selection and funneling of potential customers toward crypto companies is a feature, not a bug. Of course crypto companies are willing to invest development time and sponsor some Nostr devs—their incentives are perfectly aligned.
I wish it were different because Nostr (the protocol) has real potential. But as it stands, the ecosystem will keep self-selecting for crypto customers and crypto-backed devs for a while. Unfortunately, this comes at the expense of Nostr’s growth, value, and resilience as a network. Some very smart people (including some of Nostr's OG devs) are very aware of this and advocating for change.
Will things really change? I don’t know. Nostr’s in a semi-cozy “local maximum” right now, and the will to change might not lead to meaningful action. Even if action is taken, there’s no guarantee it’ll result in the outcomes users expect.
-
GN Nostr 🌙!
-
GM!
-
GM!
-
GN! 🌙
-
"Could not resolve https://fertschnigfotography.com/.well-known/lnurlp/albyhubtest. Check if you are connected, if the server is up and if the lightning address albyhubtest@fertschnigfotography.com is correct.
Exception was: timeout".
Let me know when you fix it and the ⚡️⚡️⚡️ is yours :)
-
I was just going to tell you that I've build it and it has worked for me, thanks. Can I Zap you directly for the "bounty" or is there some sort of procedure to follow?
-
GM fellow cat person
-
GM!
-
Hopefully Amethyst will support Blossom by itself soon. noStrudel already does.
nostr:nevent1qqsfdtsydmzzue3er2xc0m2735peqr7kmsw8xklj9d3ux0xhzgpuhnsj8j83h
-
I do, especially during Git merge or rebase conflicts. JetBrains IDEs provide full code completion in the diff/merge view, and I always have the full test suite running in the background. There’s no reason not to do it (well, other than when you are dealing with crappy code with no unit tests which is unfortunately the reality of a lot of projects).
-
It always did. Folks just had to know how to enable "Desktop mode" :)
-
nip05 domain-wide blocking with "hidden words" isn't working for me (Try to add `mostr.pub` to the hidden words and switch to Global - warning Mostr is pumping a lot of awful stuff across the bridge and isn't representative of most Fediverse content at all).
Amethyst folks are already working on this. I'll try to build the PR later today.
nostr:nevent1qqsd0zh0k43lkwxje8xde4efrwgdwvgt4tcw932wf8qartatgdrv3dsprdmhxue69uhksctkv4hzuctrvd5k7mre9eek7cmfv9kz7q3qa6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajqxpqqqqqqzn8smax
I'm still looking for an solution for noStrudel though.
-
Good Morning Nostr! 🌄☕️
#GM #GoodMorning
-
nip05 domain filtering maybe? (Extract note author's pubkey, query associated kind 0, if nip05 key contains `mostr.pub` discard note). Not a general solution, but likely good enough to mute Mostr and other gated NIP-05 enforcing communities.
-
GN Nostr. I won't be online tomorrow (I mean today :)) so enjoy your Sunday! 🌙
-
Thanks for the suggestion Dee Kay. Here it is: https://github.com/vitorpamplona/amethyst/issues/1173
-
Unfortunately no joy. Apparently hidden words won't match partial NIP-05 addresses.
-
Thanks! I’ll try this before dynamically building a mute list. Individually blocking every Mostr NIP-05 address doesn’t seem very practical—it would likely create a massive mute list, and I’m not sure how well clients would handle it. I’m already having issues with a much smaller mute list.
-
Just reposting this here in case anybody knows how to block Mostr notes in #noStrudel
nostr:nevent1qqs2lxuzv9ws063enurmhx9pfz4cftj06mk0haf0m7a0m9zgv055vhcprdmhxue69uhksctkv4hzuctrvd5k7mre9eek7cmfv9kz7q3qa6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajqxpqqqqqqzgwhxwr
-
Does anyone know how I can stop seeing `Mostr.pub` notes in Nostr clients? I’ve already removed wss://relay.mostr.pub, but Mostr content still shows up for me in Amethyst and noStrudel. Is there a way to block or mute all notes from a specific relay?
Nothing against the Fediverse by the way—I have dedicated clients for ActivityPub. I just want to filter out Mostr’s unfiltered hot garbage.
#asknostr #mostr #amethyst #nostrudel
-
GM!
-
Quick, hide before Nostr Influencers start marketing the revolutionary USB Network.
-
Interesting experiment! It even created a new programming language on my behalf—Kocala, the Kotlin + Scala hybrid that nobody asked for 😄.
https://haven.accioly.social/b43bf8f174d9c1a95c355a0b7ed9d232830553bd36acb54d4cbdbae227301389.webp
-
Enjoy the conference! nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 yoloed my patch into master, so I guess the release candidate stage is officially over 🤣. When you get a chance, please test it from master, and if you find any Blossom-related bugs that slipped through, feel free to DM me or log an issue in my repo: https://github.com/aaccioly-open-source/haven.
https://haven.accioly.social/e15ef942cad2d7348c9a136d8588531fa61e90c62cc9ef7b0fc8816d2da0da27.png
-
nostr:nprofile1qqsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4cprfmhxue69uhk6etdwfjkccte9enkjunfdehjummjvuhszxrhwden5te0dehhxarjxghxw6tjd9hx7tn0wfnj7qgcwaehxw309ahx2un0wd68ytn8d9exjmn09ehhyec588pjy, nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3vamnwvaz7tmwdaehgu3dwfjkccte9eshqup0qyghwumn8ghj7mn0wd68ytnhd9hx2tcht4zgq, nostr:nprofile1qqsphkn7raeed0dz68hejqea4r7jmsmzsyrephumuch4jypchwtufkgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uq3zamnwvaz7tmwdaehgu3wwa5kuef0vpm22w, nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wf6k2tnrdakj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9usc5pxf
-
https://haven.accioly.social/73935948d2176c6fc8738958ae07fe0fa91087dc0f5b31ceaff724a4d06ac4ae.jpg
GM, folks! As promised, you can find a release candidate version of Haven with enhanced Blossom support below. This version works without reverse proxies or hardcoded CORS headers. It also hopefully fixes some goroutine leaks and routing conflicts that were causing Haven to crash.
I've already submitted a PR upstream, but for now, I'd be grateful to anyone willing to test this—especially with Blossom clients other than noStrudel.
https://github.com/aaccioly-open-source/haven/tree/rc/blossom-fixes
#GoodMorning #GM #Haven #Blossom #Relay #PersonalRelay #MediaServer
-
I ended up logging in with my nsec as well. I’d prefer to use Amber, but it’s a hassle to fix my mute list every time I use Amethyst.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z, nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 , sorry to bother you, just in case you weren't made aware of this issue already: the latest Amethyst fix for mute lists seems to be causing issues for me. When I log in through Amber, I have to edit the Security Filters to properly load my mute. I’m using Amethyst v0.92.7 (tested with both the Google Play and "regular" versions) and Amber v2.0.8, with Amethyst fully trusted on Amber.
-
nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 - Finally a PR for Haven itself: https://github.com/bitvora/haven/pull/53/files
-
I'll try all of this, thanks. My findings so far are:
1. Logging in directly with my nsec "fixes" the issue.
2. Logging in with Amber and adding a new mute word also loads the mute list.
I'm on Amethyst v0.92.7 which supposedly fixes the mute list issue (and Ironically I haven't noticed this issue before).
-
Thanks for the zap nostr:nprofile1qqsdmpqwgvae0pu4hv66gz9uv8hhaxtg3wstzehcedx8e67t2vvwevqpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshsfyu3ds!
-
GM folks, happy Friday!
I’m still working on Haven. It’s been a busy week, but you can expect an RC version in my repo soon, followed by a PR upstream sometime this weekend. The functional coding part is already done; I just need to clean up the commits before making it public and sharing it upstream.
#GM #GoodMorning #Devstr #Haven #Blossom
-
GM!
-
Same here. I mean, my mute list mostly just grows over time. I check it occasionally and haven’t regretted muting anyone "unfairly" yet. But muted words come and go. Every few days there’s new "Nostr background noise" to filter. There are always trending "themes" that everyone on Nostr feels compelled to write about. Given how small Nostr is, the "Twitter trending topics" experience gets old pretty quickly. Trending topics often completely dominate both my follows and my "tamed global" feeds.
Right now, my weekly theme filters revolve around: US elections, BTC ATH, Ross Ulbricht, and editing kind 1 notes.
By next week, the Nostr hivemind will move on to a new set of themes, and I'll update my filters accordingly.
-
Thanks, D.O. Unfortunately, the confirm button didn’t change things for me. When I log in, my mute list still doesn’t load. However, adding a new mute word does make it load. Is your mute list loading automatically when you log in?
-
Ok, apparently the zap.store version of Amethyst does load my mute list, but I had to add a new hidden word for it to load properly. My "tame" version of Nostr with cats, art, and software development (minus the "Nostr Influencer" content) is back. Please don’t expose me to unfiltered Nostr content ever again.
A proper mute list really is the best algorithm.
-
Other than #Amethyst, are there any other clients that support encrypted mute lists (Kind 10000)?
#asknostr #devstr
-
Have you found a solution? I'm facing the same issue.
-
#lobsterstr? #lobster? 🦞
-
GN Nostr
-
I'm not sure if this counts as "turning off edits," but you can click the top right of edited posts to view the original note. I'll edit this post on purpose so that the differences between the edited and original posts are obvious.
As far as I know, there's no way to fully disable this feature (other than cloning the repo and patching it yourself :)).
This is the original note.
-
Flameshot, Shutter and Ksnip are all great tools.
-
Test Haven + updated Khatru: https://haven.accioly.social/cb60aeb602cbea245a4e98efd624d5c48410bdabbe3bba7a668e3cd352617b47.jpg
Look, Mum! No reverse-proxy magic needed for Blossom!
-
GM!
-
GN Nostr.
https://image.nostr.build/2a260dc184d40ce10ea1b6d82f4efbd746dda130f5bdf4a4d7d8414280857c41.jpg
-
Yeah, it’s brilliant for testing relays during development. Instead of keeping two separate browser tabs open using Nostrrr, I can now view notes in both my Haven Inbox and Outbox relays side by side. Since I’m running multiple instances of Haven for development purposes, this is a blessing.
-
I’m playing with it right now—great UX! Just a few weeks ago, I didn’t even know how to explore individual relays, and now I’m absolutely spoilt for choice. Thanks for sharing.
-
Sure. Good talk.
-
"Some Nostr devs" is purposely vague, and so is "forked Nostr". Should this conversation really be so abstract?
-
Also nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr — as promised, a small PR to expand and clarify preflight requests and caching: https://github.com/hzrd149/blossom/pull/34
Let me know what you think.
-
This guy derives… and integrates!
-
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 - incoming PR: https://github.com/fiatjaf/khatru/pull/17
-
GM Nostr
Test Blossom - no upstream CORS headers
https://haven.accioly.social/50683519ca5873916d30134e25ea317a28fc8d7a0877b707a75346250bf9fc37.jpg
#GM #GoodMorning #coffeestr
-
GM!
-
My hero! Keep me posted please (I can try to help as well. But Android development is a bit out of my comfort zone)
-
I agree. The story about this is that I made a small fix to allow GiftWrapped DMs and some time later nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a removed supported for Kind 04 DMs. I don't know enough about NIP-17 to claim compatibility, but GiftWrapped messages are working (as in, if I remove all my DM relays but Haven I'm still able to send and receive NIP-17 messages). If anyone more familiar with the NIP is willing to certify NIP-17 compatibility I'm happy to change support metadata (I myself don't know enough to claim NIP support one way or another).
-
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau, Sir, just reiterating the ask to fix Amethyst not to send non chat related events to DM relays.
https://image.nostr.build/c241ab00b8fc663a7e472739ae6c21ae3464adb59a99d8b26f96577c4ad72e0f.jpg
-
Haven also supports NIP-17 (it doesn't show up in the metadata but it does accept GiftWrapped messages).
-
Testing Haven, Katru, and Blossom with a custom Nginx client_max_body_size setting. Uploading an image larger than 1MB.
https://haven.accioly.social/c77fcbf917d1fb026138e9b6dd156a4d8eb4372e627aba332ac67b112b414ea5.jpg
#catstr
-
Squeakers on BlackArch approve this message.
-
Not Fiatjaf, but maybe propose your own List / Set (https://github.com/nostr-protocol/nips/blob/master/51.md). If this is related to storing encrypted mnemonic words as per one of your recent questions I think that it may deverse its own event kind.
-
Well, it’s been trained to parrot content from sources like cookbooks, self-help, health & fitness, fashion, and family & relationships. So, all things considered, it’ll probably make slightly better decisions than horoscopes, fortune tellers, or a Magic 8-Ball.
-
I'm no longer using it, but zapping you anyway :).
-
GM!
-
GM Nostr.
https://haven.accioly.social/99473aa6e3f34ad7655fa5ddcfd0803c8554cbba9ac6e3484f119e66d9942a7c.jpg
#GM #GoodMorning
-
+1. Don’t get me wrong; I don’t miss code with 12 levels of inheritance from the early 2000s, and I’ve adopted a lot of functional idioms from my time with Scala. Nevertheless, looking at the state of most JavaScript codebases today makes me want to cry.
-
Yeahp, lots of interesting new ideas for sure.
-
+1. Plus, Nostr can sometimes feel like a targeted ads platform for certain Lightning ecosystems. Very few people are willing to admit that running a Lightning node to transact just a few thousand sats per month actually sacrifices not only convenience but also time and hard-earned sats.
To be clear, nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3vamnwvaz7tmwdaehgu3dwfjkccte9eshqup0qyghwumn8ghj7mn0wd68ytnhd9hx2tcht4zgq, I'm not talking about you—you're not trying to hide information or mislead anyone. But I enjoy being a bit of a contrarian. There's too many people on Nostr funnelling users toward the same two or three companies selling "convenient" Lightning software and services. I’m 100% in support of users running CLN/LND nodes, as long as they have a clear understanding of what they’re getting into and why.
-
I gave up on running ligthining nodes just to Zap people here on Nostr. I'm not using ligthining for anything else. I'll accept the risk if WoS loses a few of my sats.
-
SSL is also a pain + expensive with .onion addresses. Hopefully they are working in replacing CA's alaltogether.
-
Still can't zap you from WoS :)
-
This one is on me Ben. Don't worry, Haven will have proper CORS support OOB soon. I just need some patience as I'm travelling and working on a gazillion other things at the moment and I want to get this right.