Apparently Santa is on #nostr and uses @YakiHonne πΉπ
View quoted note β
arfonzo
arfonzo@superfriends.online
npub1p26s...60yv
πββ¬ Nerding, horticulture & humble servant of cats. π
β‘ I run the superfriends relay at wss://nostr.superfriends.online | π§
tor: ws://sprfrnsx2nhyc6mkkb4hi2hauq7kd3ckudkj3v7djbw4wopqfcotw4id.onion
π€ Here for the decentralisation, not for the maximalism.
Hey #asknostr: what are some current, popular ways to write long form articles for #nostr? Few years ago I used @Habla News, is that still the way?
Are there alternatives?
I've had issues in the past with Markdown rendering issues on habla (although I'm generally happy with it), just wondering if there's alternatives that support Markdown-based drafting rather than WYSIWYG.
arfy's musings on privacy:
This is a great post and resonates on so many levels.
I used to be like this, for ~25 years. It was extremely difficult in the later years. It was easier in the days of dial-up BBSing, and when the internet was much younger. Privacy and anonymity were very much the de facto position back in those days of the early 90s. I have wild stories of hacking and phreaking back in the day, but those are tales for another time.
Anyway, life and work got in the way, and I eased up on this position. Feelsbadman, but it is what it is. :goberserk:
I still value my privacy, use VPNs and things like tailscale with my own hosts around the globe to protect my privacy. But I'd be a liar if I said I 100% cover all my tracks, all the time. Far from it.
Kudos to anyone still making the effort to remain truly digitally clean. It's such hard work, and I respect people highly for trying to maintain it. :MEOWDY:
View quoted note β
For anyone who is interested, apparently jumble has this "feature": if you specify just one single relay instead of the default optimal relays, you will end up with a protected event.
Really wish we could toggle this behaviour, because I can see a lot of instances where it's not the desired behaviour for the user.
I'm simply testing some code tonight against a single relay, and running into this. If you understand the problem, it's easy to just use another client, but it can be confusing if one is unaware.
View quoted note β
Grab an event based on its hex identifier, with `nak`:
(command line tools are arfy's fave for this reason, their flexibility is so great!)
View quoted note β
Update on the superfriends #relay:
Now that superfriends has migrated over to #strfry, I've been able to shut down this extra proxy filtering service I had in front of the old relay, which would blacklist known spammers.
In lieu of that, I've ported my proxy filter code into a blacklist plugin for strfry. It's absolutely amazing how extensible this is! I love how I no longer need to run an extra service, and the plugin is called as needed to do the same thing. :catTime:
View quoted note β
Hey @fiatjaf is there a way to fetch a hex string event with `nak`?
For example I just want to fetch a post, or reaction event, based on a hex identifier.
Thanks!
it's funny cause it's true πΌ
View quoted note β
I feel this a lot, these years. π
View quoted note β
oh. cool.
We didn't need those VPNs anyway.
View quoted note β
@grok is this true?
View quoted note β
I am loving how #strfry can hot reload most configuration changes without restarting! Absolutely awesome #nostr relay. It's only been a few hours since migrating and going live, and I already love it. :MEOWDY:
Amazed I could migrate all events from nostr-rs-relay and import them into strfry without much fuss. I was honestly worried I'd have to lose data in order to migrate, which is why I held off for years. :goberserk:
View quoted note β
Hello frenpais! Well, I've finally done it! The superfriends public #relay has just migrated from nostr-rs-relay over to strfry! πΌπ₯
We have migrated all event data over as well, so if you were using the superfriends relay before, your data should still all be here. Everything should work exactly as it did, except much more performant! This means feeds load much faster, events read/write much faster, and less error-prone.
As always, anyone is welcome to use it: wss://nostr.superfriends.online
nostr-rs-relay has been fantastic over the years, but the backend on sqlite3 was a major bottleneck for public relays. Even with loads of fine-tuning, there is only so much you can do with sqlite3, particularly if hosting a public relay (I think it's great for private/small relays!)
I like that strfry uses LMDB which is much faster and scalable. It also is more actively maintained and has some great tooling built in for plugins and extensibility.
If you have any problems, please let me know.
Enjoy! π»πΎ
View quoted note β
We have migrated all event data over as well, so if you were using the superfriends relay before, your data should still all be here. Everything should work exactly as it did, except much more performant! This means feeds load much faster, events read/write much faster, and less error-prone.
As always, anyone is welcome to use it: wss://nostr.superfriends.online
nostr-rs-relay has been fantastic over the years, but the backend on sqlite3 was a major bottleneck for public relays. Even with loads of fine-tuning, there is only so much you can do with sqlite3, particularly if hosting a public relay (I think it's great for private/small relays!)
I like that strfry uses LMDB which is much faster and scalable. It also is more actively maintained and has some great tooling built in for plugins and extensibility.
If you have any problems, please let me know.
Enjoy! π»πΎ
View quoted note βHey @AQSTR, is there a reason the replies on the webapp are capped at 280 characters?
Would be great to be able to post longer form replies there!
So glad I left that shitshow years ago. Absolute clowning.
View quoted note β
This is my guy, Shadow. πββ¬
Yes, it's also him in my pfp, and my profile banner.
#catstr
View quoted note β
This is a great point and I've postured similar thoughts in a post a few days ago. I don't think exclusivity is intentional these days but there's a real microcosm of ideologies that challenge wider adoption. Both technical and content-based.
View quoted note β
View quoted note β