Your Domain

# Nami

A decentralized binary package manager

### Why

There are already many package managers, like apt-get, brew, but this is all centralized.
Every time the author updates the software, they need to write complex configuration files and PRs and wait for merge.

Nami is a decentralized binary package manager,
she allows software authors to publish their software anywhere,
without having to request a merge from a software center for each update.

### Install

$ curl -L git.io/getnami | bash && exec -l $SHELL

### Usage

NAME:
nami - A decentralized binary package manager

USAGE:
nami [global options] command [command options] [arguments...]

COMMANDS:
install Install package. $ nami install github.com/txthinking/nami
upgrade Upgrade package. $ nami upgrade github.com/txthinking/nami
remove Remove package. $ nami remove github.com/txthinking/nami
info Print package information. $ nami info github.com/txthinking/nami
list Print installed packages. $ nami list
help, h Shows a list of commands or help for one command

GLOBAL OPTIONS:
--help, -h show help (default: false)

### Example

$ nami install github.com/txthinking/nami

### What Does Nami Do?

All files are stored in `~/.nami`

## Nami for Software Publisher

- Package name such as `yourdomain.com/package`
- Nami will send GET request to `https://yourdomain.com/package/nami.json`, `nami.json`

### Built-in supported…

Real-time systems engineer building insight from signals, sensors, and software.

Location: San Francisco, CA Remote: Yes – hybrid preferred, but fully remote OK Willing to relocate: No

Technologies: Python, TypeScript, Linux, WebSockets, React, Three.js, Blender, Postgres, Redis, RF Systems, Embedded Systems, Multithreading, Automation Frameworks, GLTF, Unity, Serial & Socket I/O

Website: [https://intervolz.com/resume.pdf](https://yourdomain.com/resume.pdf) Resume: [https://intervolz.com/downloads/mvolz_resume.pdf](https://intervolz.com/downloads/mvolz_resume.pdf) Email: maxwellvolz@gmail

---

I'm a senior software engineer with 10+ years of experience building full-stack systems at the intersection of hardware and software. Most recently I led AR/VR automation at Meta, built real-time performance tracing tools with Perfetto, and drove CPU/GPU profiling pipelines for next-gen wearable devices. Before that, I verified phased-array antenna hardware and built full-stack systems for the HAPS project (SoftBank acquisition).

I love turning messy real-world systems into interactive software tools. My skillset spans system design and integration, high-throughput automation, and modern tech stacks. I’m especially into creative 3D UIs, live visualization of physical systems, and tools that empower engineers and artists.

I'm looking for teams solving weird problems that may have physical interfaces, spatial tech, or just need a hacker who figures stuff out and makes it feel…

Sure! :) But I think it's all just about few principles. Elaborated a bit more on them:

1. Tailwind CSS classes extracted with purge-css, all inlined.

2. Favicon inlined, small images (<4kb) inlined. Not sure what’s the best threshold. Here is all https://turboeshop.com/inlinedimages/ is all page in one requests. Meaning two big images that are https://turboeshop.com/fastestpageintheworld/ were inlined - results are way worse. So larger images - definitely excluded.

3. Gzip stuff(as one commenter below commented, not done in turboeshop.com/fastestpageintheworld/).

4. Everything from same domain and subdomain. If you want cloudinary or friends, I guess they are only allow subdomain. This is totally OKeish exemption. Or maybe there is a way to work around that cloudinary serves, Cloudflare caches.

5. JS - inlined. Cash.js maybe if you need jquery replacement, or just vanilla. Little content on vanilla js nowadays :), https://gomakethings.com/articles/ is something interesting. Don’t want to flame here, am not js expert, maybe someone can elaborate.

6. For compex components - svelte web components (or stencils or lithtml) - I’d prefer svelte but am not sure what’s best.

7. Google analytics a) - there is new google analytics (GA4) with measurement protocol2 and new server side google tag manager. Serve side gtm does two things a) serves gtag.js; b) accepts measurement protocol hits and sends to GA. Take a look how it’s done -…

Is it really that obscure these days?

1. Have a computer in your house open exposed to the internet on port 80- port forward on your router.

2. Run an http server on that box. Apache is a reasonable choice but there are probably easier pieces of software out there to set up.

2a. Create an index.html or equivalent default page name and put some html in it even if it's just hello world- it can even be in plain text.

3. Technically you are now self hosted on the internet! Figure out your external IP from your router and point a browser to http://$YOURIP/ and you should see your page.

The next steps are optional but kind of required to have a "real" site.

4. Set up dns. Since you won't have a static IP from your ISP almost certainly, you will need to use a dynamic dns provider. Noip.com is a popular choice. Once this is working you can register a domain name with GoDaddy or whoever and then point that name to your dynamic dns provider. Now you can load up http://www.yourdomain.com (or whatever tld you choose)

5. Set up https. For some reason beyond my comprehension google is forcing everyone to use https if they want to really exist on the internet in any real way even if they are just serving static pages. Let's encrypt can you there for free. Now you can go to https://www.yourdomain.com and your page will show up and Google et al might even consider you to be a real presence on the internet and index you one day.

> Due to recent changes, App Engine no longer supports mapping your app to a naked domain. If your domain registrar supports URL redirects, you can redirect from http://yourdomain.com to e.g http://www.yourdomain.com or http://appid.yourdomain.com.

http://code.google.com/appengine/kb/general.html#naked_domain

http://stackoverflow.com/questions/817809/how-to-use-google-app-engine-with-my-own-domain-not-subdomain

http://blog.notdot.net/2009/12/Naked-domains-on-App-Engine

(For non-commercial use this limitation may be more acceptable, but if you are seriously launching a commercial service, you probably want to freely choose your domain.)

Got the serverless webhook part. Thanks for the tool and explanation, really easy to follow and a great help for future works!

Just one remark, about indexes.js, you write: "Update name to the name of your index that you set up earlier, and url to yourdomain.com/algola.json, replacing yourdomain.com with your site’s domain."

The protocole has to be included (https://yourdomain.com), not only the domain, it makes sense because the key is "url" but the exemple provided (yourdomain.com) and phrasing suggest otherwise.

Thanks again!