Nostr Web Client

An LLM and pandas

Nate 1y ago 💬 2

Is that nostr based GitHub replacement ready yet?

#asknostr

Yes they are lol

Replying to

hodlbod

Thoughts on the John Birch Society?

https://github.com/bitfinexcom/hypertele

Fascists, if I’m not mistaken.

Replying to Xis10tial1

how I do ssh:

Nate 1y ago 💬 1

Holesail uses Hypertele but combines it into an importable npm package.

Replying to

Svetski

Wat mean in plain engrish?

The founder of Holesail, nostr:npub1h5t3asu90f2x48rxtcqkjvwhza7m6kngs7vjyanx8xqyswc6es2s4645z5, has a more detailed critique.

Replying to

Svetski

Wat mean in plain engrish?

curl -s -x socks5h://relay.8333.space:8882 https://nprofile1qqs8a8nk09fhrxylcd42haz8ev4cprhnk5egntvs0whafvaaxpk8plgpzemhxue69uhhyetvv9ujuwpnxvejuumsv93k2g6k9kr/v1/info --insecure | jq

Meaning you can set up a jump server that is exposed on a domain using Holesail, and without the issues that stem from NWS.

Replying to

calle

Huge milestone: First demo of Nostr Web Services (NWS) bringing TCP to Nostr. With NWS, you can host any existing web application on Nostr without having to use DNS or even announce your public IP to the world, simply by sharing your service's npub (or nprofile).

Try it out the demo yourself. Here is a Cashu test mint running with NWS. Let's use curl to retrieve the mint's information. The request travels from your computer to the public NWS entry relay, then through nostr to the service's NWS exit relay. At the other end is a Cashu mint with HTTPS encryption.

```

```

I can't stress this enough: THE MINT RUNS BEHIND HTTPS!

The NWS entry relay can't read your traffic. It's encrypted. We can host public entry relays that can be used by anyone.

This means we can plug the entire internet to it 🌐.

Let's plug it into Cashu for now. Nutshell wallet supports socks5 proxies (that's how it uses Tor). By setting the public entry relay as the proxy, the wallet can now connect to a mint's npub/nprofile and communicate with it via NWS.

This is going to be so freaking cool. And it's going to be a lot more useful than just for Cashu. There are still bugs and issues that need to be ironed out but the code is coming out soon. Watch this space.

Nate 1y ago 💬 7

Anyone interested in this needs to know that you can do this with Holepunch: https://holesail.io/

nostr:note12vy8lmphxyfd7np7t503k8fzs3em2h6szfwad0fkgr6prjkjuhxsddyprj

Replying to

Vitor Pamplona

No, kind 4s don't work with the new encryption scheme in a backward compatible way. :(

We are all focusing on a new kind 14 defined here: https://github.com/nostr-protocol/nips/pull/686

How do this affect encrypting application data? Also, will there be a change to using window.nostr.nip44 now instead of nip04?

If using NIP 78 for arbitrary app data, is it best to encrypt the content even if it’s just simple user settings or just leave it plaintext?

I see projects doing both when I pull the events down from the relays.

#asknostr

If I want to receive Lightning payments on my e-commerce site, what is the fastest way to implement that? Just use @Alby, Lightning Tools, or @nodeless? Any other options?

#asknostr #lightning

Replying to

Guy Swann

It is literally internet magic that I can use a bunch of different #nostr services that all just sign in with the @getAlby extension.

I dont have ANY passwords or account names or emails or privacy issues with even a single one of these services. They all just sign in with my #nostr account and it takes ONE click. On top of it all I'm not putting myself or my passwords or personal info at even the slightest risk by using all of these external services.

I literally am annoyed that the rest of the internet doesn't work like this.

I am making signing in with Nostr or creating a Nostr account the only way to use an e-commerce website I am building. I think the rest of the internet will catch on eventually.

Glad I gave up on Reddit years ago. Having your own token is a red flag.

🚩🚩🚩

#reddit

Got my wife on Keet now that they have audio calls. Works pretty well.

Replying to

HolySats

LOL. I went to change tires for a season and wrote at least a half of a new article regarding CBDC. When I didn’t touch a tea they gave me they were like “you’re one devoted worker to your company.” And I was like “yea, making world a better place is my duty.”

I didn’t mean insurance. I meant Bitcoin, ofc. 🧡

WiFi is super slow though. Hence the surfing of Nostr in between page reloads lol

Replying to

HolySats

LOL. I went to change tires for a season and wrote at least a half of a new article regarding CBDC. When I didn’t touch a tea they gave me they were like “you’re one devoted worker to your company.” And I was like “yea, making world a better place is my duty.”

I didn’t mean insurance. I meant Bitcoin, ofc. 🧡

Haha Awesome

Nate 2y ago 💬 3

Sitting in a car dealership for 3 hours today. Going to code while I'm here, hopefully nobody thinks I'm terrorist hacker or something. Lol

Replying to

🟠 isolabellart

🎬 Just watched Our Flag Means Death 🍿

My verdict: 8️⃣! ✨ nostr:npub12zxgk9lpn2l5uzgtcraly54luqpa0nyv6a6jmuep298kcwfaru0qrg3sj2🎥🥔😁 #NostrPotatoes

Hilarious show

Replying to

Majere

I gotta finish Second Foundation first but it’s next on my list.

If you haven’t checked them out I highly recommend the Foundation series by Isaac Asimov

Love them, the tv show was not nearly as good

Running nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg caching service on Replit was easier than I thought. lol

Replying to

pedja

i'm sorry for late reply. i was going through body detoxification.

only primal clients should use wss://cache2.primal.net/v1 for number of reasons. your local cache instance is available at ws://127.0.0.1:8801 (this is default address on which server is listening which can be changed). if you want to expose the cache instance to public you should use nginx or some other webserver which can do reverse proxy and provides TLS for security.

No problem, thanks for the help!

Replying to

pedja

congratulations! clients of primal cache instance are using websocket connections to send API request messages and get back API response messages. available API requests are defined in file called app.jl but i would suggest, beside looking at that code, you take a look at live communication between primal webapp (at primal.net) and primal server. in your web browser you should be able to open devtools/network tab, and select websocket connection to wss://cache2.primal.net/v1and look at the messages that are being sent and received. there you will be able to see common structure of each API request/response that the webapp is using which is almost everything currently available from our cache instance. webapp usually is the first to use new features and then i tell the same suggestion to our mobile app developers when i want to explain new API requests. ofc sometimes i have to additionally clarify some aspects of new API requests since nobody knows all the details which are sometimes important to mention. that's it. and feel free to ask again.

nostr:nevent1qqspmpu3un24yrtrw2z2kxnltapqrkdqefn5tmx7p4c2u6pnssv2z9qpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzq5t2m5v6scdz7s5uejyrleejgvte655cyjxgyltgltlgytnf0sq5qvzqqqqqqykzdwum

I think I understand the structure of the requests/responses and I figured out how to call the Julia functions in the nix-shell.

What is the url for the websocket of my cache service instance that a client I am building can use? Or, did I read the readme wrong and clients I build should just connect to wss://cache2.primal.net/v1?

Thanks!

Replying to 516add19...

These schools taking in international students are diploma mills.

Every college is a diploma mill. The ones taking international students are just more desperate. If you take inflation of the money supply into account, most of the students will never be able to make back the value they gave for their degree.

Replying to

pedja

congratulations! clients of primal cache instance are using websocket connections to send API request messages and get back API response messages. available API requests are defined in file called app.jl but i would suggest, beside looking at that code, you take a look at live communication between primal webapp (at primal.net) and primal server. in your web browser you should be able to open devtools/network tab, and select websocket connection to wss://cache2.primal.net/v1and look at the messages that are being sent and received. there you will be able to see common structure of each API request/response that the webapp is using which is almost everything currently available from our cache instance. webapp usually is the first to use new features and then i tell the same suggestion to our mobile app developers when i want to explain new API requests. ofc sometimes i have to additionally clarify some aspects of new API requests since nobody knows all the details which are sometimes important to mention. that's it. and feel free to ask again.

Thanks!I looked at app.jl earlier but got lazy when I saw Julia. I’ll look again 🤙