<unnamed>

Public Key

npub1u7m9n4h9d4xxjt6xcweyy470355dsrlgeag86pm38e2wgxvmxekqyzakzy

Profile Code

nprofile1qqsw0dje6mjk6nrf9arv8vjz2l8c62xcpl5v75raqacnu48yrxdnvmqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsma64xr

Publishing to

relay.damus.io

nos.lol

Last Notes

2026-09-06 04:15:51 CEST

- reply

I think that’s correct. The larger the group size the more it becomes theater. I worked on Pixie’s recently and realized that all the reference implementations I found were all just sharing the same encryption key. And you know what they say about secrets. The more people who know, the less of a secret it becomes.

2026-09-05 18:55:32 CEST

- reply

Thanks for posting this. I used it to double check against Pixie’s implementation. Found and fixed a bunch of issues.

2026-09-05 18:34:42 CEST

- reply

Looking forward to hearing about what you’ve learned!

2026-09-05 18:30:23 CEST

- reply

Copied off that other site from (at)DisgracedProp. Explanation made sense to me although I didn’t follow the case closely.
——————-
Clancy Update! Massachusetts has unique insanity law, which it looks like this is all coming down to.
So the new reporting is that there's one holdout, and the defense is trying to get that one juror removed on the basis of him (or her) not understanding the concept of reasonable doubt.
In most states, "reasonable doubt" doesn't come into the calculus for an insanity defense, because its up to the defense to prove with a preponderance of evidence (easier burden to meet than beyond a reasonable doubt) that the person was insane.
However, in Massachusetts, the burden to overcome an insanity defense remains on the prosecution. The prosecutor must prove beyond a reasonable doubt that the defendant did not suffer from a mental disorder, or that if they did suffer from one, that they had the substantial capacity to differentiate right from wrong and control their behavior. In fact, in Massachusetts the defense isn't even called "insanity" it's called "lack of criminal responsibility."
So what's most likely happening is that one juror is stubbornly saying that the prosecution has met its burden of proof to show that Clancy, while diagnosed with mental illness and prescribed drugs, still knew right from wrong. All the other jurors are now probably saying that the prosecution has not shown beyond a reasonable doubt that Clancy knew the difference between right and wrong, because she was obviously mentally ill and on medications.
So this entire situation is very much turning into female OJ. Basically the jury has been convinced that there is some reasonable doubt about whether Clancy knew right from wrong, while there's probably one guy who, looking at the situation rationally, understands that if there's reasonable doubt about whether Clancy understood right from wrong, then none of the entire 21% of the female population on psych meds, nor the 15% of mothers who are diagnosed with post partum depression, know right and wrong. And voila, 40 million Americans can now suddenly get away with murder. Because according to psychiatry, isn't every single one of them mentally ill, and thus isn't there SOME REASONABLE DOUBT that they know right from wrong? What else does mental illness mean if not this?
And thus, quite obviously, there cannot be reasonable doubt in such a case, at least if you want to maintain a functioning society. It simply cannot be that 40 million women now have the right to commit murder. And of course the defense is saying it's not about all the possible women, it's about this woman. But this is simply unreasonable--there is no way for human beings to reasonably extrapolate and evaluate whether there's a chance that one "mentally ill" and medicated woman knows right from wrong while another doesn't. It's a matter of degrees that's too abstract to reasonably evaluate, and that is why there cannot be reasonable doubt. It is unreasonable to have doubt in such a situation. That's what reasonable means.
It really is a matter of loyalty to functioning of civilization versus loyalty to the cohesion of society, as I said in my prior post. A case like this basically destroys the system in the name of avoiding harm to a single individual.

2026-09-05 18:20:30 CEST

- reply

Welcome! Love to see new creators and builders joining.

2026-09-05 18:15:31 CEST

- reply

I’m building it into PixieOS, but as a follow-first feed. A key cohort is kids building games and I want to make it easy for them to share and have controlled social networks with their friends.
https://primal.net/e/nevent1qqsff7gmpkzl399fef95wmjrcz7ecz98g3a66vnxy6hqhpxrw7n568cgj7jk5

2026-09-04 19:45:55 CEST

Thinking about the next release. Our North Star should be to make it as easy as possible to build a new app, and to invite others and share it.
Since this is an OS, we should be able to do all app development from within the OS. You shouldn’t need to download and install anything. Launch Pixie, open the PixieCode app (add an API key) and instruct your agent to create an app and starting editing. Unfortunately I don’t see how we can avoid the API key friction. 🤔
I think we should be able to create, edit, build and share an app all from within the OS.

2026-09-04 19:34:40 CEST

- reply

Looking forward to learning more.

2026-09-04 19:33:35 CEST

- reply

Definitely like, but what you get out of an LLM seems to depend on your domain and skill level.

2026-09-04 13:27:06 CEST

GM! Nothing better than a morning with several quiet hours ahead to build. Working through the cleanups for 0.1.9. Thinking ahead about priorities for 0.2.0.

2026-09-03 23:58:54 CEST

This is one of the powerful benefits of building AI agent tools directly into PixieOS. When you’re debugging, the agents can see what you’re seeing and analyze the code directly. In this case, I told the agent to inspect the window the raccoon is looking at.
@nprofile…xq50 thank you for the bug report. Found and fixed.
https://blossom.primal.net/515108bf6e8dd17dd1a59ab815ef9f0e2fbf3e28023e6a07f8bea0fdffc9681c.png

2026-09-03 23:19:35 CEST

- reply

https://primal.net/e/nevent1qqswmqg8hypwnjqrlulkl7len9hv5htzzkfv2f298a02gc6j6qnrvgqymye6u

2026-09-03 23:18:32 CEST

- reply

This was one of the reasons we built our new feedsync relay. The relays shouldn’t need to store all the content and pay all the bandwidth. The clients can store and send it to each other. The relays just need to be directories knowing which clients have what. Also relays should know what’s on other relays so that they can manage their own inventory efficiently. Hoping this eventually cuts down the cost of running a relay. For anyone interested in helping, please reach out.
https://codeberg.org/PixieOS/feedsync-server

2026-09-03 22:47:03 CEST

- reply

You need to go directly to dev.pixieos.io so that you can see all the apps including Messages.

2026-09-03 22:44:01 CEST

- reply

I see it here. It’s a problem in the game. I’ll fix. Also, I noticed the sound in the game doesn’t play unless you close and reopen the game app. Another bug.
Here’s my testing pixie code if you want to create a channel in messages. P7Q-EBZ-S48 Copy paste or fast type into invitations box. (I need to make that UI clearer)

2026-09-03 22:03:34 CEST

The new staging build for 0.1.9 is up. I would appreciate any help with testing. Link below.
1) open the dev link in separate browsers
2) try generating a Pixie code on one browser, in the other browser create a message channel. Message back and forth. Send apps to each other.
3) when you receive a message when the app is closed, you should see notifications
4) Change your profile in one account (Settings | Profile), and watch it update on the other account. Should update in Contacts and Messages.
5) end apps with links. Right click or long press on the app from the desktop.
- should work on mobile, desktop, tablets.
If you see bugs or if something doesn’t make sense, please let me know. Thank you!🙏
https://dev.pixieos.io/PixieOS.html

2026-09-03 21:52:13 CEST

- reply

Oh I see, you’re in Brave. Any other details on your steps would be helpful.

2026-09-03 21:51:05 CEST

- reply

Awesome, thanks for letting me know. Could you please share with me your device and how you got to the page? Specifically im wondering if you’re in a regular browser or a web window from one of the nostr clients. Need to try and do exactly what you did to reproduce here.

2026-09-03 21:23:02 CEST

Here it is! This is a shared game on staging. Hopefully it works when you click the app to play. If you see any weird stuff, please let me know.
https://dev.pixieos.io/PixieOS.html#/a/3020cd02a63d646d90d7691dde8934383f04b080ba25484261651a25676ce9bd

2026-09-03 20:29:36 CEST

I would love to bring something like this to Pixie. Pixie instances already use key pairs as ID. I’m wondering if we could add this as another connection service like how we do with Nostr, Feedsync and Blossom. We could make it easy for apps to connect with each other. If anyone can help with this, please reach out!
#FIPS
https://fips.network/

2026-09-03 17:54:46 CEST

- reply

Nostr isn’t dead. A great community of builders. Just the place I’d rather be.

2026-09-03 17:30:28 CEST

- reply

Hey, dev team, just wanted to bring pixie’s feedsync server to your attention. It might be useful for all three implementations. We created a new type of nostr relay where the server acts as a hot cache but the clients hold inventory and can directly deliver P2P to each other via WebRTC. Hoping this opens up lower latency applications like messaging and gaming. We use it already for Pixie’s messaging. We built it because traditional nostr relays were ill suited for encrypted messaging (clients don’t know if they’re missing a message). The repo is here. If anyone has questions don’t hesitate to reach out. https://codeberg.org/PixieOS/feedsync-server

2026-09-03 17:16:00 CEST

- reply

Very cool. My kids were just asking about that topic the other day. Games are tough to build on traditional nostr relays so for the pixie project we created a new type of relay called feedsync. The idea is to allow relays to be hot caches but move the inventory to clients so that the server doesn’t need to hold all the data. Get clients to send updates directly to each other P2P. The plan is to then use that system to enable low latency multiplayer gaming as well as the traditional nostr files and updates. If you’re curious, you can find the server code in our PixieOS repo (linked from pixieos.io). My focus is on helping nostr builders so if I can help in any way, or just be a beta tester just let me know.

2026-09-03 14:42:30 CEST

- reply

Avg price of tokens are rapidly depreciating right now. I think we’re at $1 per million and falling fast.

2026-09-03 14:40:46 CEST

- reply

I really want to figure out OS integration for in-app payments using ecash or something similar. Initial use cases could be gaming and podcasts. It’s unclear to me what payments for software look like because if the price is too high, you can just create your own. Creates a niche market maybe.

2026-09-03 14:13:24 CEST

Good morning! Big mug of tea and just sitting down to start a big rip out and rewrite. In the old system, users connected with their friends by generating one unique code for each friend.
To simplify the UX, now each user will have one code (like a phone number) that they can give out to all their friends.
These codes represent nostr npub mailboxes that help users find each other and connect. Once connected they can use Messages and share apps E2E encrypted.

2026-09-03 14:07:38 CEST

- reply

Yes, agree and React is slower than raw too. React was amazing for when humans were writing the code. Amazing how things have changed in the last year!

2026-09-03 13:34:17 CEST

- reply

It doesn’t seem like the social side is growing right now, but that doesn’t bother me. The people who are here are a unique bunch of builders and bitcoiners. I’m focused on Pixie because I believe it takes an easy to use app discovery ecosystem to lure new people into building and freedom tech. Our biggest cohort of users right now are kids building games. I want to give them the tools they need to share games and introduce their friends. They will undoubtedly start building their own social networks later. What are you building?

2026-09-03 04:16:45 CEST

- reply

I made a lot of progress with simplifying the devkit. It now ships without the rust components that caused the original complexity. If devs want to build WASM apps, they can easily get the full repo with git and handle setting up rust. For everyone else there are agent instructions (on pixieos.io) with a single script tested on windows and mac. Maybe give the devkit another try and have the ol clanker tour around. Remind the clanker to use the built in agent tools. It would be helpful to see where the latest frictions are so I can fix them. The UI layers might be heavily customizable if we can separate them cleanly. The core APIs would need to stay consistent so that apps can run and talk with each other. The OS is already pretty customizable if you work within the existing app extension system. You can build apps that, when installed, bring their own OS-like services that, even when closed, they can provide to other apps. I’m looking for ways to make it all more customizable and extensible.

2026-09-03 03:35:01 CEST

Between other projects, I’ve also been working on a new nostr app for pixie.
I find that, by having no algo, the main nostr feed disadvantages people who post less frequently, pushing their posts far down. This client organizes posts by your follows so that you never miss a post from your favorites. Still work in progress. You can play around with it in the devkit.
https://blossom.primal.net/6c03adf77aba03fb7b539773dfb14d2f53b63b1899c5e5f472d49cc0ecd34da8.jpg

2026-09-03 03:03:26 CEST

- reply

Yep. I pulled out light mode from pixie because I couldn’t stand to look at it anymore when testing.

2026-09-03 02:51:59 CEST

- reply

I’ve been learning about this too. I’ve been experimenting with some Meshy.ai models which have animations. I also used glm5.3 flash to build my own 3D fish model just to see what was invoked. The fish and the animated warlord from meshy are in the game lab app in the next pixie release. I took the warlord from 40MB to 50kb (to see how to get it as small as possible). I put a game engine into pixie to make it easier for kids to build and share games with their friends.

2026-09-03 02:35:31 CEST

- reply

I use cursor and opencode. I prefer cursor because I like looking at the code and doing selective rollbacks. Cursor gives generous allocations to grok (very good) and composer (which is cheap and decent if properly instructed). I use GLM 5.3 Flash on opencode which is very good and cheap. What do you want to build?

2026-09-03 02:24:48 CEST

- reply

I was quite into react previously but I’ve found you can use agents now to write smaller and faster code by just using pure JS/TS or native. When I was working on the .pix file format, I wrote the same app in all the major frameworks. React was the worst in terms of size. Ships with a lot of overhead.

2026-09-03 00:14:06 CEST

- reply

Thank you!🙏 It’s been a labor of love for a while. If you’re building anything (or want to) and would like to collaborate, just let me know.

2026-09-02 18:10:27 CEST

- reply

Yes. Did you just finish the DHH interview too? I really enjoyed that part of the discussion about OS customization. The issue right now is how to preserve your customizations. If you download the devkit, you have the entire source code for OS and pixie’s apps. You can modify and have your own customized version of Pixie until you update and rebase the OS on its next release. The OS is rapidly changing right now so older versions will be incompatible with later versions if the APIs change. I would like to figure out a way to preserve these customizations across builds more easily.

2026-09-02 15:27:33 CEST

GM! Been heads down on the 0.1.9 release. Just testing everything now. Nice to see it come together but still lots of nits. Features:
- Share app by link
- Join Message chat with code
- App notifications and banners
- UX updates for Messages and Contacts

2026-09-01 17:42:01 CEST

New community channel. Kids how-to, setting up the dev environment, and making games with Pixie’s built in game engine.
https://www.youtube.com/channel/UCN5b2_y2fQds-ZJjAGwuang

2026-08-30 16:32:29 CEST

I’m loving this new project. https://omarchy.org/
I’m not a personal fan of keyboard driven OS, but I absolutely love the trend of decentralizing and building your own OS. A lot of shared ideas between Pixie and Omarchy. Listen to DHH’s recent podcast on Lex Fridman to learn more.

2026-08-30 16:27:28 CEST

- reply

Thank you. I’m still seeing it here.
Access to fetch at 'https://nostr.build/i/e764f4fb4faabddb33572661bcb3fe340187e437139fb0d43315b30009213a3f.gif' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

2026-08-26 15:30:56 CEST

- reply

Working on it. Thought that having a full nostr integrated operating system would help.

2026-08-26 15:04:54 CEST

- reply

@nprofile…54wh (blossom server)👆

2026-08-26 14:58:09 CEST

@nprofile…450c @nprofile…etgt @nprofile…ffzy @nprofile…39pt
just FYI, I’m seeing a lot of CORS errors because Pixie sends null. Pixie runs as a file because that allows anyone to run it locally without hosting. Please consider using * for CORS.
Eg: Access to fetch at 'https://cdn.nostr.build… from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

2026-08-26 13:43:16 CEST

GM nostr fam. Yesterday I finished the new Notifications system for Contacts and Messages. In the next release, you see an alert when you receive a new message or one of your contacts updates their profile.
Focusing today on:
- making app share more resilient
- share app by link

2026-08-23 22:20:49 CEST

Also made some good progress today on share app with link. I’m really looking forward to this. Hoping it can unlock app sharing and getting feedback on your app via nostr.
https://blossom.primal.net/7397a2647244b3229b09658db2946e66ebd42964c78b9badbb4bb19add9fe23c.jpg

2026-08-23 18:44:57 CEST

New Notifications system coming to life. I’m going to add it first to Messages and Contacts to alert on activity even if the app is closed.
https://blossom.primal.net/faea4ee881aa8a53349b6cd41f333b9e7e0c2921dd769464b656873346482e90.png

2026-08-22 16:02:21 CEST

Starting to plan the next release (0.1.9):
- send an app to someone with a link (eg posted in Nostr) where they can instantly click to open.
- improve the UI for Contacts and Messages
- make it easier to directly connect with new contacts from Messages
- Improve user avatars
Anything else high priority?

2026-08-22 15:51:53 CEST

- reply

Oh, I forgot to mention that you can now add / save to Home Screen on Android to create a PWA of Pixie. It provides a full bleed UI without the browser chrome.

2026-08-22 15:39:02 CEST

- reply

Exploring this…
https://blossom.primal.net/cbed48ca02f6a7d3e29fa02c04883250989695c136dc441b37310f077ca1c501.png
https://blossom.primal.net/04985cf6ed114ab359fef1bc767616e3ae62be62237706f454f237fb1b87fc1b.png

2026-08-22 03:47:33 CEST

- reply

Now that most things are (finally) working, I’m hoping we can pivot back to UX and UI.
There is one feature I really want to do next: as a user, I can share an app by sending a link to anyone. They can visit the link to view and instantly use the app. This will allow devs and others to share apps over Nostr. People can rapidly prototype and share with their followers.
The UX around PixieSync codes is also terrible. Right now, you must create a contact and then connect via PixieSync. It needs to be easier to connect and message. We also have the potential confusion between Nostr DMs and Pixie Messages (E2E multiparty channels with OS integration like sharing apps in Messages)
In the last few months, we got the tablet and mobile experience working. There are now four UI variants: touch and !touch, mobile and !mobile. Each of the four variants have UI differences.
Did you see how it looks on your phone? I’m hearing from Samsung users that their gestures are conflicting with our swipe gestures. Works pretty well on iPhone though.
I’m happy people can now play with it. We need to decide what’s next to work on. What do you think is the next highest priority?

2026-08-22 03:29:58 CEST

- reply

In the Settings app you can customize the OS: Accounts, Profile, Appearance, Language, Memory, Storage, Nostr Relays, Feedsync Servers, and Blossom Servers.
Each account is a Nostr private key.
You can create multiple accounts if two or more people want to share a Pixie (or if you want different personas). I use multiple accounts when I’m testing different features to keep everything separate.
The Nostr npub is the core of your Pixie account identity. Pixie uses Nostr keys for all identity and signing operations: Messages, PixieSync, Feedsync, FileShare, and even app publishing.
We chose Nostr because everyone should own their account identity free of centralized servers. Nostr will also enable some fun future use cases (as a user, I can easily message the developer of any app, etc.)
If you’re a developer, check out Pixie’s API docs at pixieos.io to see what’s included for you. Lots of fun stuff to make it easy to rapidly build and share apps.
Next: System Monitor and the internal runtime.
https://blossom.primal.net/2921bfb64d24ebffea54fa9d138b7470878dfb9a47ca28baae5d38bd1ca97b0a.png
https://blossom.primal.net/f636cff00ee4586f28adc228c8030c8b62848a21216a33917a7b0881b2b1373c.png
https://blossom.primal.net/b2033cd97205da54e8da8060a79a01810d3aa07610258c41916e36ed797be1ce.png
#nevent1q…6ye6

2026-08-22 02:36:11 CEST

- reply

Over the next few days, I’ll take you on a guided tour of PixieOS.
Pixie is like ChromeOS except you don’t need to install it on your computer. Pixie runs on Android, iOS, macOS, Linux and Windows. You just launch Pixie when you need it. Your Pixie apps can run on any computer.
Check it out at pixieos.io. If you want to get it running on your own computer, point your agent to website and ask it to set up the devkit for you.
I’ve attached a screenshot here of my dev iPhone, showing the developer apps (like App Builder). I will review those in later posts.
I wanted to start the tour with Settings (and how we use Nostr for accounts)… /2
https://blossom.primal.net/b607435c719ebc06455b9f5deb5f4eb6942343f2f0e31bab510455cd907e1689.png
#nevent1q…8sjh

2026-08-21 16:00:48 CEST

Good morning Nostr! Excited to introduce PixieOS, a magical new webOS and app platform for open source builders. Hoping it becomes the fastest and easiest way to build and share apps.
What is it?
A powerful OS in a single highly compressed HTML file. No install! It runs as a mobile PWA, as a website, or even offline as a downloaded local file. Runs almost everywhere. Designed for AI accelerated app development with embedded MCP agent tools.
Why create it?
Our own OS! Imagine what we could do. Nostr + bitcoin + JS / WASM. A playground for new open source technologies that big tech will never provide. Shareable apps that can run anywhere. A full ecosystem with extensions and services that apps can provide to each other. App stores for better discoverability. Digital in-app payments? So many possibilities.
Project status?
Pixie is a solid proof of concept with many cool new technologies already integrated and a long list of features to add.
We’ve been working on it for a while, but it’s time to start building in the open now to find bugs, improve security, and refine features.
It’s super early and some key parts are untested and buggy, but we wanted to start getting feedback from you. FYI, no data security yet so be careful with your real nostr keys.
Want to learn more? Follow this account for updates and more details on the key components in progress. Also, point your agent to the repo and ask what it can do.
Next up: How Nostr keys are used as its account identity with the goal that you get iCloud like replication across your desktop and mobile devices.
Check it out! Try coding up your first app and send it to your friends. Point your agent to the devkit at https://pixieos.io/
I’m hoping that we can build this together. I’m excited to share more, get your feedback, and start building this with you.
https://blossom.primal.net/5eccc0f3d9bcc3da38549274387217c761e6d909bb679b9e3a888aa5729494d7.jpg