Started tinkering with a new project that I'm definitively going to need some help with. but the idea is to build a simple static file manager for nsite stuff

The goal is to allow users to easily login with the various keys they use for their nsites and manage relays, blossom servers, and the static files

Really I just want visibility into an nsite, to show the user what it is an how it works

Its deployed here https://npub125vreuyn6fqg6d6fz6dhmskv9u4qz5uf5rhdg3ymagqwz654quks8g8agm.nsite.lol/

I'm going to work on getting the app to a point where its "functional" but it would cool to have more features like detailed stats, drag and drop, or maybe file editing... so if your interested please look over the repo and maybe open a PR

The github repo is here

https://github.com/hzrd149/nsite-manager

Reply to this note

Please Login to reply.

Discussion

Question, what's an Nsite?

Static websites for every npub

The idea is you upload the html / js / css etc files to blossom servers, then create a bunch of events that map a path to the blob hash

e.g.

/index.html -> 186ea5fd14e88fd1ac49351759e7ab906fa94892002b60bf7f5a428f28ca1c99

Then an nsite host server can look for those events, and serve them as static files under a domain for each pubkey ( for example .nsite.lol )

NIPs PR here https://github.com/nostr-protocol/nips/pull/1538

Oh, that's fucking cool.

👀

Has nostr entered its Geocities era?

Almost I think, I was not around for geocities so I cant really tell you.

But this will allow anyone to easily publish a static html website 😁

You have indeed confirmed that nostr is in its geocities era. It’s where/when I learned html. Bullish.

Will take a look at this when I’m back from vacation 🤙

awesome, I've heard geocities was an awesome era so I'm excited to relive it

Today you don't even need to learn html. There are great projects to create static websites:

- Jekyll https://jekyllrb.com/

- 11ty https://www.11ty.dev/

- Hugo https://gohugo.io/

- Gatsby https://www.gatsbyjs.com/

We can levarage all of them with nsite.

based

This could help me to revive profiles from an old Dutch social network Hyves from the 00’s (there were more than 10 millions profiles). I made a backup application which gave the user mostly static files (stored locally) of their profile and content. Opening the index.html still works to view your content. Many have used it so those backups are still around somewhere held by users.

My plan is to bring that back online with a Nostr client using Blossom and nSite as utilities in the back. /cc nostr:npub1tef4nks9rrfcvkxlwts9eu4zluhfs025nrr3ldkm8ssuqv7m46ksf7nskn

Interesting!

The folders aren't events.

no, each nsite file is a single replaceable event with its "d" tag set to its absolute path. the nsite-manager just groups the files into folder to make it easier for humans to navigate

Yeah, it's pretty cool. 🤙

I'll tag you for a review on our filesystem. Probably a technique you'd at least be interested in.

Could we use 30040s to index blossom files? I don't see why not.

Any event is already allowed for. If they're not events, we would just need some other UID to reference them.

Sick! So we can store blossom objects, and structure them however we like using NIP-62 (and extensions) events.

Yes, you could use events to create folders of blossom objects or git objects, or whatnot. We just have to define this.

What kind of filesystem are you working on? is it something using nostr events?

Yes. We're using 30040 indexes as folders and creating a scaffold for them, to gain full UNIX functionality, with drives and tracebacks and symlinks.

Every dir is just a file, after all.

Sound heavy, but if your able to get it to work that would be cool

nsite omits the folder because they are not necessary, the nsite events are focusted on showing the latest version of the site. So keeping history would make things slower and break more

Michael has been working on making trees more performant, and we actually need the folder-hierarchy view for #Alexandria, as an alternative for card-view, so it should be interesting.

We'll see, how it works, but a couple of other devs have been tinkering with the same concept, so the use case is there.

Yes, it handles uploading new files and removing old files from the nsite

If you run into any issues with it I'm hoping this tool can help debug the issues