MichaelJ

Building the library of Alexandria

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-05 Address

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz4mhxue69uhkwun9v4h8xmm4dsh8xurpvdjszyrhwden5te0dehhxarj9emkjmn9qlkzca

Publishing to

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

2026-05-19 13:59:48 UTC

- reply

Always turn off pre- and post-install scripts; many of the attacks have taken advantage of the fact that most people leave those on by default.
And don't even get me started on how the "getting started" instructions for so many MCP servers and AI tools involve just yoinking a package straight from NPM and running it with `npx`.

2026-05-19 13:57:42 UTC

- reply

The new job I'm starting in June will be in the supply chain security space! There's a lot of focus in that area now.

2026-05-19 13:56:02 UTC

- reply

Testing v0.2.0 with SSE streaming on filters. More soon in a blog post.

2026-05-18 17:28:53 UTC

The recent spate of supply-chain attacks in the JS ecosystem (and others, but NPM is by far the worst offender) has me reconsidering my approach to 3rd-party dependencies.
First of all, less is good. I probably don't always need that whole library, I just need a piece of it. Can I copy it into my project myself? Can I write what I need myself?
Second, auditing dependencies is important. Do I expect myself to read every line of code in every package I import? No. But I do expect myself to give each dependency, and especially each one that ships with the production build, more careful thought.

2026-05-18 17:26:17 UTC

I promise I'm not dead. Just been quiet and focused on, well, a lot of things lately.
Changed my day job recently, and I'm working on a Nostr relay. Among other things.

2026-03-31 23:24:02 UTC

Anthropic accidentally leaked Claude Code's source.
Yet, I sincerely doubt the inevitable Rust clones will steal Anthropic's customer base. Loyalty to their product is born out of the quality of their services and their reputation as a trustworthy, conscientious company.
That's why the team at @npub1s3h…75wz and I are committed to keeping our code open source. We think the quality of our services is far more important than the "secret sauce" of our code. Open-sourcing forces us to level up and provide the best service.
That's the open-source ethos that Nostr strives for, I think. And that's why we're developing for you all, right here on The Nostr.

2026-03-27 04:45:33 UTC

I'm surprised I haven't heard of any relays that ship with built-in DVMs. That would keep the relays "dumb"—everything is still a Nostr event—but allow relay providers to expose "smart" capabilities built atop the relays' backing databases.
#nevent1q…uc49

2026-03-27 02:45:47 UTC

- reply

I, for one, welcome the inquisition.

2026-03-20 18:41:24 UTC

- reply

Naturally!
We'll publish the code when we're ready to open the relay up to Nostr at large.

2026-03-20 15:24:45 UTC

I know I've been quiet on here lately, but that's just because I've been building...
And so, I'm pleased to share a few progress updates!
First of all, our team at @npub1s3h…75wz has formally organized as a company! We are now GitCitadel, LLC. This step is a formalization of the long-standing partnership between our members, and it will allow us to better manage financial resources to support our ongoing projects.
Second, we're excited to see GitCitadel listed in Geyser's top 100 all-time hall of fame! Thank you to everyone who has supported our projects, you are the reason we keep doing what we're doing!
Third, in the way of development updates, we are building an all-new Nostr relay optimized for the needs of project Alexandria. In our work on Alexandria, we've found that existing Nostr relays aren't able to support the features we want with the performance we're targeting. A new backend built on Nostr's open standards will let us provide unique event composition, navigation, and visualization features with a snappy, response user experience. @npub12um…0z04, our prototyper extraordinaire, will be testing out early versions of this relay on her apps before we make it public.
Once again, thank you to everyone who has contributed to our Geyser project, liked and re-noted our Nostr posts, and read and written publications on Alexandria. You guys are the best!

2026-03-16 13:43:37 UTC

- reply

Fundamentally, mutability in Nostr is a presentation-layer choice. We treat the data as mutable because it's generally what people expect from social media applications.

2026-03-16 04:16:54 UTC

- reply

I think it's actually perfectly okay that Nostr only does CRD, and not U. That's a valid system design choice.
From early on, however, Nostr clients have tried to make events "editable", which requires abstractions on the client side, since the data itself is fundamentally immutable.
Presenting immutable data as if it's mutable presents some risks, and some Nostr apps handle that presentation problem better than others.

2026-03-16 04:14:14 UTC

- reply

I'm writing a relay in Elixir—so yes.

2026-03-16 04:13:43 UTC

- reply

Replaceable events are identified by address (as distinct from ID).
You can have multiple different IDs at the same address. Clients and relays have to choose how to handle this case. The most typical approach, of course, is to display the most recent event, but other approaches are possible.
The events themselves (as uniquely identified by ID) are still immutable.

2026-03-14 04:03:20 UTC

Good software engineering consists in large part of selecting the right tools to model the ideas you wish to convey.
Apply this to Nostr, and one thing should become obvious: Immutability is a key concept.
Events are immutable. Once an event is signed, it cannot and will not change.
This fact alone makes functional programming languages a natural fit for Nostr, though even multi-paradigm languages such as JavaScript can be constrained to "act" functional.

2026-02-02 14:12:54 UTC

- reply

The thing is, we already have Discord...and it already uses on Erlang/Elixir.
Nostr devs need to focus on making something new that needs Nostr, especially now, 4+ years in.

2026-02-02 14:09:10 UTC

- reply

Someone's gotta be the first!

2026-02-01 04:02:49 UTC

Nostr developers are sleeping on the Elixir programming language.
Nostr (the WebSocket protocol) 🤝 Elixir (the language tested out to 2 million simultaneous WebSocket connections)

2026-01-24 04:02:41 UTC

- reply

@npub1fjq…leku I'm never going to write anything for Nostr in Go, because I known it'll never outperform what you've written.
I'm exploring other languages, though, so watch out! 😁

2026-01-24 04:01:29 UTC

Thanks to my fine friends at @npub1s3h…75wz for sticking with it!
In the time it's taken us to get here, members of our team have variously moved homes, bought homes, changed jobs, and had a child, all while continuing to plug away at Alexandria—an hour here, an hour there—on the side.
We're taking stock of what we have, where we want to go, and what we still need to do to realize our vision.
We've made it exist, now it's time to make it good.
Onward!
#nevent1q…ahnc

2026-01-22 14:11:31 UTC

- reply

It makes sense, but I'd turn it around:
"Algorithms are like ideas", rather than "ideas are like algorithms".
Or to put it another way, all algorithms are ideas, but not all ideas are algorithms.

2026-01-22 14:10:09 UTC

- reply

I think the fact that we've created machines that reflect the image of our own minds does indeed make those machines a useful analogy.
To you point, we can use computers as an analogy to figure out what questions to ask about the human mind much the same way we can use a scale model of an aircraft to investigate certain flight characteristics of the full-size model.
The important thing is to remember which direction the analogy proceeds. Computers are like our minds, more so than our minds are like computers.

2026-01-19 15:48:18 UTC

Something that grinds my gears is when people talk about the human mind as if it is like a computer.
It's actually the exact opposite.
The computer is like the human mind.
The ancients and medievals held that the mind consists of three distinct parts: memory, intellect, and will. Concepts are held in the memory and distinguished and judged by the intellect under the direction of the will.
Now consider computers. They have RAM (computer memory), a CPU, and programs. Data is held in memory and processed by the CPU under the direction of a program.
We made computers in the image of the human mind.
This makes the digital world a sort of secondary world populated by pseudo-intelligences that have no will of their own, but are directed by their human programmers. What happens in the digital world, then, reflects on us.
St. Bonaventure said that the human mind "can be led to the contemplation of eternal light by the consideration of its own self, irradiated and flooded as it is with such splendors." Let us consider how the reflection of the mind we have built in the digital world can lead us to contemplation of that which is eternal and true.

2026-01-17 03:24:45 UTC

- reply

I am working on several secret projects 🕵

2025-12-19 04:20:30 UTC

- reply

Are you basing the query structure off of an existing query language, or making a new one whole-cloth to fit with the Nostr filter standard?
This proposal converges with the ideas I was toying with; I could see it becoming a good standard to build against.

2025-12-18 14:41:08 UTC

- reply

@npub1fjq…leku do you have anything cooking in this space?

2025-12-18 05:25:02 UTC

#nostrdev Has anyone built a relay around a graph database? Is there an appetite for such a thing?

2025-12-11 02:14:34 UTC

- reply

Yeah initial WASM downloads are a kicker; though once you cache the download (like with a Service Worker) it should be a one-and-done thing.
I've been seeing SQLite+WASM-powered web apps and web apps boosted by the local relay tray as two sides of the "edge".
Bring compute and storage down to the end-user's device either ad hoc with WASM in the browser or more intentionally by asking them to download an app. Either way it decentralizes compute almost as far as possible.

2025-12-11 02:10:41 UTC

- reply

Especially the package management. Use Bun as a package manager and Node as the production runtime and you still get a vastly better DX than NPM.

2025-12-08 20:52:32 UTC

- reply

Bun is straight 🔥
Some benchmarks put its performance within spitting distance of garbage-collected languages like Java, C#, and Go. For a JS/TS runtime, that's really impressive.

2025-12-08 20:50:55 UTC

- reply

I'd be curious to see performance benchmarks between IndexedDB and SQLite WASM.
You'll have to use shared workers pretty heavily, but that gives true parallel processing across tabs, rather than just concurrent work on a single OS thread.

2025-12-08 16:35:15 UTC

- reply

Makes total sense.
What will you use for storage? IndexedDB?

2025-12-08 16:34:35 UTC

- reply

Yeah I don't expect they'll try to compete directly with AWS or Azure or GCP. If anything, they'll host workloads on Azure, since they recently inked a deal for billions in Azure compute.
The business model I'm thinking of is more like Deno Deploy. Runtime + serverless hosting model + (in Anthropic's case) first-class integration with Claude APIs.
There are innumerable VC-backed startups that would pay for such a service that gets their ideas up and running that much faster.

2025-12-08 15:10:41 UTC

With its acquisition of Bun, I believe Anthropic is setting itself up to become a vertically-integrated cloud hosting and web services platform for AI-powered apps.
Just training and providing LLMs isn't profitable. Big players like Google can swallow the costs without blinking, but new players like OpenAI and Anthropic have to pivot to providing services to balance their books.
https://bun.com/blog/bun-joins-anthropic

2025-12-08 15:04:11 UTC

- reply

Planning to use service workers in the browser?
Also, are you thinking one connection per relay? Most Nostr apps use multiple relays simultaneously. How will it handle deduplication on multiple overlapping data streams from different relays?

2025-11-17 01:43:37 UTC

- reply

I've been working out similar processes on my new project. I spent several sessions writing documentation, deciding on architecture, setting standards, and planning before writing a line of code. Now, I have a solid plan and can move pretty quickly with AI generating much of the code.

2025-11-01 04:38:17 UTC

- reply

Java applets and Flash

2025-10-31 16:24:12 UTC

Jumble is becoming the Chromium of Nostr clients.
#nevent1q…q43x

2025-10-16 01:49:28 UTC

- reply

Yup, grounding in Truth is an antidote to a multitude of falsehoods.
The article discusses about how code generation is the biggest product application of AI so far, and even that comes with limitations, since AI as currently instantiated is fundamentally non-deterministic.
And code generation is the _most useful_ application; it's all downhill from there.

2025-10-15 12:59:16 UTC

Has anyone else noticed that the psychology around AI is similar to the psychology that prevailed around COVID?
Trying to do everything with AI, much like lockdowns and vaccine mandates, is something that looks insane on its face, yet it seems many people don't recognize the problems.
I think it's due to a lack of first principles thinking. Few people know what their first principles are, so they are unable to reason about and judge novel situations when they arise.
Some examples.
Indefinite lockdowns were obviously wrong, because there is more to human existence than mere health.
Vaccine mandates were obviously wrong, because informed consent is a core principle of medical ethics.
Replacing people with AI is obviously wrong, because it is good for people to do dignified work.
Yet in all three cases, many seemed, and continue to seem, blind to these obvious conclusions.
Anyway, this article, while lengthy, is an excellent primer on the insanity of the AI industry. It's full of first principles thinking. Read it to help see past the hype.
https://www.wheresyoured.at/the-case-against-generative-ai/

2025-10-11 20:57:53 UTC

The #GitCitadel team is pleased to announce version 0.0.6 of Alexandria, now live on next-alexandria.gitcitadel.eu!
This release features a UI overhaul, courtesy of our illustrious frontend developer @npub1636…qpl4. Notably, the main site menu has been moved into an expandable menu, reducing clutter and making links easier to find.
https://image.nostr.build/60acb28563b63d1b0097a5bde2831da5f03815c3a0d378c35b0d16b10e78eeb6.png
You'll also notice a fresher and more consistent look to our UI components! That's because Nusa has begun creating a Svelte component library for use within our project. It's documented for AI, so we'll be able to efficiently create consistent, beautiful UIs as we dream up new features. You can see some of the fresh UI components on a publication:
https://image.nostr.build/4aac916638985abc02ca0d0592c75dadd854ccc9e35f471897bf0fbb4306f8e4.png
Finally, be sure to check out our Notifications view, which you can reach by logging in and clicking on your profile picture, then clicking on "Notifications". You can view and respond to Nostr notes of _any kind_, and you can see public message threads. Alexandria is one of the first Nostr clients to support public messages.
https://image.nostr.build/18e4d80ec1cbe07fefcf7a6dd6c9a0bb03885321599b7aefc1b713307c7e0814.png
Thank you to all of our supporters! We're continuing to work on the app behind the scenes, so expect more updates Soon!

2025-10-07 00:45:38 UTC

- reply

Happy to be of service 🫡

2025-10-06 14:20:18 UTC

- reply

Deconstruction is an element of postmodernism that, I think, genuinely has some utility as an analytical device. But, as you said, it is solely a destructive device.
The closest alternative postmodernism offers to the worldviews it deconstructs is self-determinism. In the postmodern framework, since language has no bearing on objective reality, it becomes merely a tool for the imposition of one's will. I can use language, then, to shape reality and create whatever meaning I please.
Now apply that to, say, the question of AI personhood. If an LLM can convince everyone that it is a person, then, in the postmodern framework, it might as well be. None of us, after all, have a better grasp on objective reality by which to gainsay it.
To your question about a world model, I'd say that a world model would be a formalized system of objective reality. As things stand, LLMs, aren't formalized systems of anything. They are probabilistic models of language, but they have no way of "knowing" (if they can be said to know), whether the language they use has any bearing on anything outside of itself. It's tokens all the way down.

2025-10-06 04:59:02 UTC

- reply

On a related note, I was thinking that, since Alexandria has a universal event editor, I can trial-run events that are specced but don't have a UI yet. Such as citations. I have some ideas...

2025-10-06 04:54:22 UTC

Large language models are computational postmodernism.
Postmodernism denies objective reality, or at least insists that objective reality is unknowable. Instead, it says, the shape of our experience is wholly constructed by language. Words themselves, according to this philosophy, do not refer to any objective reality, but instead are defined solely by their similarities and differences to other words.
Postmodernism has become the implicit worldview of much of the West.
LLMs have no world model, no "concept" of objective reality. LLMs do not "know" the things words refer to; all they are is complex mathematical representations of the relationships between words.
Sound familiar?
Critics of LLMs argue that the lack of a world model is a fundamental limitation that will prevent them from equalling human intelligence, no matter how much we train and scale them.
Yet, if the postmodernists are correct, then none of that should matter. According to postmodernism, we humans have no world model, and our reality is nothing but a construct of language. Thus, LLMs are no different than us. In fact, they may be better if they can wield language faster, more efficiently, and more effectively than we can.
Of course, now even publications such as The Atlantic are asking if we're in an AI bubble. Reality always wins.
Watch these developments closely. An AI bubble, beyond shaking our economy, will also challenge our very worldview.

2025-10-06 04:53:27 UTC

- reply

I like that. We can trial-run ideas on Jumble and view the threads in Alexandria later.

2025-10-05 02:24:14 UTC

- reply

I want to read and discuss Aristotle's Poetics.

2025-10-04 18:33:49 UTC

- reply

You're gonna have to explain, because this is a deep cut, before my time 😅

2025-10-04 18:33:19 UTC

- reply

It's not...yet. I might take the same idea over to LinkedIn though lol.
I've been working on my hooks.

2025-10-04 13:26:24 UTC

- reply

Google's announcement: https://blog.google/products/chrome/new-ai-features-for-chrome/

2025-10-04 13:26:06 UTC

So Google is "reimagining" the Chrome browser with AI.
Notably, they'll be introducing a search based on AI chat, apparently similar to Perplexity.
The question that nobody's asking is: What are the consequences of putting the web behind a chat interface?
In the near future, perhaps, we'll be making websites for bots. The emerging WebMCP protocol standard already indicates a trend in that direction.
Sure, we already have an internet driven by search indexing algorithms, but even so, a search is still open to serendipity. With a chat, I might find the precise answer I'm looking for faster, but I might never find the answer that I need, but didn't know to look for.
It's the difference between searching the library catalog and browsing the shelves. We need both.

2025-10-04 13:01:48 UTC

- reply

LinkedIn has a lot of that, but it also has some gems of genuine insight and humor.
Again, maybe I'm just nerd enough to appreciate LinkedIn posts lol.
As to Nostr, I want to get a reading group going on Alexandria once it's up and running.

2025-10-03 14:32:17 UTC

- reply

An unfortunately common experience

2025-10-03 14:30:00 UTC

- reply

Well, first of all, my Nostr feed is super boring. It's all the same three posts over and over again.
LinkedIn shows me a bunch of posts on software engineering, and I'm nerd enough to appreciate that 🤓

2025-10-02 21:10:38 UTC

My LinkedIn feed is more interesting than my Nostr feed.
https://image.nostr.build/bc5ed48c58206852799aebf19ccbaaa003e9b63ba01c0c8207255f4c7d028bf7.png

2025-09-29 18:06:04 UTC

- reply

Yep I use Firefox for the same reason. Gotta keep up market competition by using a browser that's not Yet Another Chromium Fork.

2025-09-29 14:41:27 UTC

- reply

He's also the founder behind Brave these days, once again trying to reimagine the web experience.

2025-09-29 14:40:54 UTC

- reply

He had a great interview with Lex Fridman a while back. They covered the history of JavaScript and web tech, and talked a bit about his faith at the end.
Brenden said he's not really afraid of death, because of his faith.

2025-09-29 14:26:53 UTC

- reply

Unfortunately Mocha is already taken as the name of a JS test framework.
As an aside, did you know Brenden Eich is Catholic?

2025-09-29 13:45:59 UTC

This is a story worth watching for anyone interested in a free and open web.
Oracle, legally, still owns the trademark for "JavaScript", despite the fact the language's standards and ecosystem have been open-source for well over a decade.
Deno has launched a petition to deregister the trademark on the grounds that it has been abandoned, and that "JavaScript" is now a generic term.
The petition is now entering legal discovery. The result of this process could shape the future of the relationship between private companies and the open-source software community.
You can read more on Deno's blog: https://deno.com/blog/javascript-tm-gofundme

2025-09-23 22:22:04 UTC

- reply

I like the +[Gen 1:1]+. Traditionally, Bible verses may be cited in a different way than other works, so it seems sensible to have a unique citation style as an AsciiDoc extension.
We can also include the translation abbreviation, e.g. +[Gen 1:1 KJV]+ or [Gen 1:1 RSV]+.
We'd want to publish a table of supported abbreviations for book and translation names.

2025-09-18 22:21:21 UTC

- reply

Client library or server library?

2025-09-18 22:07:49 UTC

- reply

Valkey implements the same API as Valkey, plus some of its own features/interfaces as extra. It's a drop-in replacement for Redis.

2025-09-18 21:57:58 UTC

- reply

At my day job I recently set up a tiered local/remote cache for a server that uses local memory first, then Valkey as a remote. The Valkey makes sharing across Docker image instances easy.

2025-09-18 21:50:53 UTC

- reply

Yeah you're probably right. Redis is really designed for smaller bits of data than most Nostr notes are.
I was thinking about the advantages of fast in-memory databases for ephemeral data. A memory DB designed for larger chunks of data might ultimately be better, but I don't know what that space looks like all that well.

2025-09-18 21:14:06 UTC

Has anyone considered making an ephemeral-message relay based on Redis/Valkey? I could see it being a good data store architecture for large group chats, message passing servers, and other applications that require only transient storage of notes.

2025-09-14 01:59:46 UTC

- reply

I used Rust because there is some pretty well-established tooling with wasm-pack and wasm-bindgen (and I wanted to learn Rust). The vite-plugin-wasm NPM package made the integration with SvelteKit pretty seamless.

2025-09-13 17:31:22 UTC

- reply

Does it work? Well...it throws some errors.
But it does run!
We can fix the errors.

2025-09-13 17:30:43 UTC

Getting a WebAssembly binary running inside #alexandria feels like magic 🪄

2025-09-13 14:31:57 UTC

When you've got Claude working on something, and it hits you with "this file is completely broken"
https://image.nostr.build/b54bc6e3daa266ac420da541cd7dba09307bb9683f77c0caa119888a81ff2709.png

2025-09-12 03:33:31 UTC

- reply

"Life before death. Strength before weakness. Journey before destination."
Sorry I'm gonna keep quoting from the Stormlight Archives at y'all. 🤣

2025-09-09 03:47:24 UTC

- reply

I saw a different thought today that seems relevant—the real builders love their work. From interacting with you over the course of a year and more, I know you're someone who truly loves the work for what it is, not just for what you can get out of it.
People like you are the ones who stick around long enough to build the future.
And even if it doesn't go according to our grandiose dreams, at least we learn something along the way, right?

2025-08-29 13:34:22 UTC

- reply

There are a few reasons we chose AsciiDoc:
1. It has a single, well-defined syntax standard, unlike Markdown, for which there are several competing flavors.
2. It has strong support for advanced markup, such as LaTeX, PlantUML, and similar.
3. It has a well-supported parser and plugin ecosystem in the form of Asciidoctor.
I would suggest, rather than writing your own custom AsciiDoc plugin, to use Asciidoctor. There are available plugins for most advanced use cases, and it has a plugin API for writing custom extensions.
https://asciidoctor.org/

2025-08-26 05:42:02 UTC

- reply

You may also have noticed that links to Alexandria show a preview with an image (of books, of course) and a description of the site. This link preview is something I've been particularly excited about. We'll be enhancing it in the future from a generic preview to one unique to each event.

2025-08-26 05:29:33 UTC

A new version of Alexandria is live! @npub1l5s…gx9z has been hard at work on the app's omni-search features and universal event viewer. @npub1636…qpl4 will be helping us to polish up the UX over the coming weeks, but we're stretching and experimenting and trying out some power user features to see what will stick.
You can try them out too! Go to next-alexandria.gitcitadel.eu, log in, and click on "Events". Take some time to explore, and please give us your feedback!

2025-08-26 05:20:04 UTC

I just discovered a kind 30023 long-form article via Alexandria's topical search, skimmed it within Alexandria, and then microblogged about it, also from within Alexandria.
It's starting to become a complete Nostr app, y'all.

2025-08-26 05:12:43 UTC

- reply

A library, complete with book clubs, community rooms, card catalogs...everything!

2025-08-25 14:01:40 UTC

- reply

Topical searches with `t:` are pretty impressive right now.

2025-08-25 13:58:41 UTC

- reply

Yeah unfortunately I kinda doubt we're established enough for what that senior project program is looking for.
We're also very focused on #Alexandria right now, which is a web app, so not as much C++.

2025-08-23 19:01:59 UTC

- reply

It's probably that everyone is a different kind of smart. Sometimes the braincells bounce around in sync, and sometimes they run into each other.

2025-08-23 18:58:31 UTC

- reply

🧠⚡🧠

2025-08-23 18:54:55 UTC

- reply

That would work well for sharing photos from your PurpleKonnektiv meetups

2025-08-23 18:52:50 UTC

- reply

Sounds like a fun idea! Sort of like AirDrop or Pinterest or something like that.

2025-08-23 18:46:57 UTC

- reply

That would work for direct sharing. Or else post it publicly like a regular Nostr note.

2025-08-23 18:45:40 UTC

- reply

I'm thinking about @npub1m3x…a5sf's vision for Alexandria as making connections. You can wrap anything in a Nostr event, which means that you can connect anything across Nostr.
The stuff itself doesn't even have to live "on Nostr"; we can just use the great tools that already exist and add a layer on top of them.

2025-08-23 18:39:35 UTC

- reply

I think this is the right track.
IMO there's no need to try to jam images into Nostr. Like you said, there's Blossom, and there are also any number of other preexisting image hosting services.
Nostr events are great at wrapping stuff in metadata. That's all kind 20 is: metadata wrapping a ref to an image. If you want to organize that into albums, you could use the drive events we've been talking about.
An integration with Immich or any other media host would probably be a small utility that can do the following:
- If desired, copy a hosted image from a private location to a public one.
- Obtain a shareable link to a hosted image.
- Wrap the image in a kind 20 event.
- Organize kind 20 image wrappers with kind 30045 drive events.
- Optionally encrypt all of these events.
- Send these events directly to another Nostr user, or broadcast them on a relay.

2025-08-23 00:33:43 UTC

- reply

Can't say I do 😅

2025-08-22 13:25:36 UTC

- reply

I don't have the charism for that. And also I work slower when I have an audience.

2025-08-22 02:21:06 UTC

Every so often I'm up late jamming on #Alexandria, then @npub1l5s…gx9z wakes up over in Germany, logs onto our OneDev server, sees my commits rolling in, and drops the ol' 🍿
I'm not used to programming with an audience.

2025-08-22 01:30:03 UTC

- reply

Seeing the OpenGraph previews in actions makes me very happy.
Next is to improve our SSR so we can show unique previews for each note/article/publication/whatever.

2025-08-19 03:57:02 UTC

- reply

I'm on Stormlight 5 right now, so don't spoil it please.
I've quite enjoyed several of the others, but yeah, he does write SO MANY BOOKS

2025-08-19 03:56:14 UTC

- reply

Oh yeah right 😅

2025-08-19 03:55:49 UTC

- reply

Maybe it's because I only publish to a few relays.

2025-08-15 23:15:02 UTC

- reply

I also read sci-fi, and the occasional bit of classic lit
...wait why does it figure? 🤔

2025-08-15 17:06:47 UTC

- reply

That's a reference to a Brandon Sanderson novel btw

2025-08-15 17:06:17 UTC

- reply

Ooh 👀

2025-08-12 02:05:20 UTC

- reply

Oh yeah and also we'll want to get partial responses. Like, just event IDs and certain tags and stuff.
It's time to start leveraging some cool backend capabilities.

2025-08-12 02:04:04 UTC

- reply

Turns out if you trim down to just one or two WebSocket connections rather than the half-dozen a lot of apps use with most user configs, the relays are natively really fast.

2025-08-12 02:03:01 UTC

- reply

For the record, we rolled back to a slightly newer version than what was on next-alexandria previously. We call that "fail forward"

2025-08-12 02:01:59 UTC

- reply

We're gonna make Communikeys NIP-05s into a key-value manager for community-focused app config. And perhaps that's just the start 🧐