Avatar
A Testy Beaver
a474859efb0442f8c9e5c656c74dd2b6809fe3d29ce788774accdb5acfd8f2c2
This is a test. This is just a test of The Emergency Beaver System. Had this been an actual emergency, a beaver would be dispatched to your location via local rideshare. This concludes the test of The Emergency Beaver System.

When you wake up to nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz publishing The Bible yet again. 🥰

https://video.nostr.build/fccd0cabe0f00f9c08072fff67ae492a9e2f04894ed21297912324165bc98325.mp4

For those that don't know, publishing a book as complicated as The Bible is quite technically hard to do. First, most relays choke when being fed over 34,000 events in short order. (The Bible has about 34k verses, depending on which version.) Second, getting all those events correctly hyperlinked at the right levels to work cohesively together is also technically difficult because you have to be able to reference each "level" of The Bible fluidly. (Being able to drill down to specific verses with a quick reference, like "The Book of Genesis, chapter 1 verse 1" is actually quite difficult to do on the computing side, not to mention that there are DOZENS OF VERSIONS AND TRANSLATIONS that can be referenced and not too eventually stored on relays.) Third, displaying these events involves quite a lot of event parsing to get everything to be able to display what is selected. Fourth, searching is also something that must be facilitated or trying to sift for specific verses in a pile of 34,000 events is not easy!

I love that the whole nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz team is pushing the limits of what is possible on nostr and using it to build systems that will disrupt the whole world.

#tebs #publishing #bookstr #testing #bible #biblestr #GitCitadel #Alexandria

I'm using nostr nearly every day, but you can't see it. I'm happy on the fringes, trying new cool stuff.

nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 said something here that tickled my fancy:

nostr:nevent1qqsxwvhauwvlsaw97llk27nu0q0fjjr0tw0czdwhjmz4jpcjxlv880c8vm28q

So, I want to start the hashtag #fosternostr

What are you doing to foster adoption, sustainability, creativity, decentralization, and the permissionless, near frictionless nature of #massiveinteroperability?

Ask nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf about how to do that.

This is significant:

nostr:nevent1qvzqqqqqrqpzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqydhwumn8ghj7mmjd3uj6un9d3shjtnfd4mkzmry9ejh2tcpz9mhxue69uhkummnw3ezumrpdejz7qpqly7238rpvmcv4j8vvjnm5pfkt7wjr59zug79xm5qkcfukam0qelqq7kd9h

If your client won't render this correctly, your client is lame and you should really try out jumble.imwald.eu and you, too, can Yak (voice notes by nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424) to pretty much anything.

This doesn't work for me. What am I going wrong?

My apologies for taking so long. I've been working silly hours and am sick.

Currently, all green:

I get it. Whomever wrote that for simplex gets how much I utterly detest lighting and my scepticism of cashu, but, going with that kind of blockchain will greatly increase enshittification (to use the technical term), and the only good thing will be that any servers for simplex will likely not be running on big tech servers, though I could be wrong about that and if so, there's very little reason to use anything other than signal.

nostr:nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyzgumm0sl24fxc8danhaenvcvvjfhv4ngw2z5gkt9xue8nanjhhgynasmf2

Replying to Avatar Carson

Hey all, I’m excited to share something I’m working on.

It is a scientific research journal built on nostr. I think nostr is the perfect architecture to build something that does research publishing better than what is the standard right now.

To name a few key things I envision with this project:

1. Research accessible by anyone. Scientific knowledge should not be restricted to a select few. This is not to say that there isn’t value in expertise, but to say that there is also value in diversity of thought that can only come from those who were not educated in the same system as many experts.

2. Comments can be left to explain, criticize, suggest research ideas to a specific part of a paper using highlights.

3. Research moves faster because it is cheaper and easier to publish, and becuase more people can interact with it.

I’ve had this project in mind for quite a while, practically since I first learned about nostr. I don’t know how to code though. So this project is my first real foray into vibe coding. That being said, this project barely works when I use it, and likely won’t work when you try it. Further, it is currently a very limited version of what I believe a research journal built on nostr can be.

I am posting this, in part, as a bookmark. I have other priorities right now and will not continue working on this project at least until January. I do plan to return to it and make it something great. I really do believe in it. I hope to continue building and sharing my vision for this, and I hope to talk more with you all about it. I know many of you have some serious developer/nostr wisdom that I want to make use of.

I’ve built a client that you can access here: https://nostr-research-client-dfokevu51-carsonminors-projects.vercel.app/

It currently has a lot of papers I published while building and testing different features. Please excuse that mess.

I also built an associated relay: wss://nostr-research-relay.duckdns.org

Cool. You'll want to also look at what #alexandria by the @gitcitadel team and @meschlr by @Emma and nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf are doing.

Quote notes are how I find a lot of interesting npubs.

Don't like them? Don't use them. They are simple (now) and work well for many.

You of all people can fork a client and strip that out if you wanted to bother.

NDK sucks. So much stuff built on it is unnecessarily slow/nonfunctional/out of date/incompatible with the latest nips.

Moving nostr dev OFF of github and apps off of the official stores. The tools to do this exist, but need use/feedback/support.

The lack of basic business tools: calendar, context aware contact databases, streamlined nostr-centric payment systems that are strictly non-kyc and one-click deployable with a relay/server.

Lightning alternatives. I detest lightning as a layer 2. Would be cool to see some new ideas in this space to allow for others, like ark or atomic swaps.

I just bought a domain.

Beware!

#tens #theemergencybeaversystem

nostr:npub1qn6wvpmqfnpl3xsu79yvfcgpjz4azdfe5ft220nqjmwqg223fvaq58xsha

I installed Noscall v.20, and still no calls go through.

Plus, adding contacts fails, but only on one of my android devices.

Just FYI.

@the_beave

This is a test. This is just a test of The Emergency Beaver System.

Had this been an actual emergency, a beaver would be dispatched to your location via local rideshare.

This concludes the test of The Emergency Beaver System.