One of the things I'll do in 2026 is try a bit more to understand the things I have experienced on psychedelics

If you have not done any yet, you might look at psychedelics like LSD and DMT as just another set of drugs, but just the fact that these chemicals allow your mind to experience things that can't be explained by words should be interesting to you

These things can't possibly make you experience something that's not already inside of your mind, but for some reason hidden from you most of the time

My plan is to try to give acid to LLMs basically, I'll not explain what I mean by that but I think that's possible. I guess we'll know if my intuition is correct after a few months

Which parts are wrong?

nostr:naddr1qqgxvwpsv4nrjdn9vsuxxcenxenrgqgdwaehxw309ahx7uewd3hkcq3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqp65wwvry4y

I use gitworkshop.dev

nostr:nevent1qqspee0rqx0v8wcfnzkk2hzysu7l7en6zeajgp7dkn6pul0vazeecmqevsnpf

Add these as tips to the client itself, like how games give you tips when you first start playing it

The forced them to allow alternative app stores

I need to do more drugs

Interoperable with Hivetalk?

CC: nostr:nprofile1qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qppamhxue69uhkumewwd68ytnrwgqs6amnwvaz7tmwdaejumr0ds7ygzuk

I tried making a comment on my keyboard app using a browser extension to see the event structure, and it seems like your implementation has missing parent item tags from NIP-22

The event generated looks like this:

{

"kind": 1111,

"tags": [

["A", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard"],

["K", "32267"],

["P", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e"],

["d", "1.0.0"]

],

"content": "My comment..."

}

The tags there should look like:

"tags": [

// root scope (uppercase)

["A", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard", ""],

["K", "32267"],

["P", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e", ""],

// parent item (lowercase - same as root for top-level comments)

["a", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard", ""],

["k", "32267"],

["p", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e", ""]

]

I'm not sure about the added d tag, but the parent item tags are required in the NIP

Also, not sure if it was a deliberate choice for some reason, but if not, this is probably a bug

Andrej Karparhy said something interesting in his interview with Dwarkesh. We know that training these models on large amounts of data produces cognitive capabilities, that's why larger models are better at doing things. But we don't exactly know what parts of the model is actually responsible for it. If we can figure it out, then we can make smaller models much more capable even though they'd be much less knowledgeable

If that's the direction it takes, then eventually I expect to have some standard smallish models that can be fed huge datasets according to your needs, and companies will use these to create knowledge specific models that can run on your regular devices. Or models that can learn stuff on demand on your own system nostr:note1n4xw4pha62lt706w0u76xj3gs8qnrallulkwac324a4zm3mp97usmys6ux

I will often open a client and wonder what standard/NIP it uses, and there would be no information about it. Many times I had to clone the repo and ask Claude Code to find the kinds used there and search for any open PRs etc in GitHub to find the actual NIP

Nostr clients should add a link to the NIPs that they implement, maybe also a link to the apps that are interoperable with it. More important for special purpose clients compared to genral ones

By everywhere I mean it has definitely been adopted by companies and developers from many different places, which I didn't expect to happen for a new L2 this fast

They built a great product and SDK, although they should have tried to make an open protocol instead (with a BIPs, NIPs like specification). Also, their biggest marketing point is the stablecoin and token support, and privacy is not a priority yet, even though Ruben Somsen's original statechain design six years ago already came with blind signatures for ecash level privacy

Blitz wallet, Wallet of Satoshi, Breez SDK and things built with it. Spark is everywhere

This is the post, I am not sure if Niel thought about making it interoperable with existing DMs but I liked the design and it was in my mind since then to make an email like interface for NIP-17 DMs

nostr:nevent1qqs0le2nayu8gnetmn0nng356wt7ctaa0wpk9ly7dxesxsqcn4kp33g40e3qm

Found it, it was nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q , now need to find his post

I personally think it's better if we migrate NIP-17 to be for mail like stuff. Day to day DMs are better suited for Marmot (NIP-EE)

Someone had already created a prototype or design for it. He was working on a nostr client of his own or just designing it not sure. Don't remember his name and can't find him in my follows now either

can't it just be the kinds in nip-17 with an extra subject tag or something?

Even YouTube has a 5k items limit on your watch later list, I think a limit like that on follow list entries on nostr would be good. YouTube can easily manage hundreds of thousands of entries and still chose to impose this limit and people are okay with it

I'm interested in new shitcoin designs. So far these three have caught my eyes

Prime: https://github.com/LNP-BP/layer1

9th proof: https://github.com/adambor/The9thProofOfFolding

zkcoins: https://gist.github.com/RobinLinus/d036511015caea5a28514259a1bab119

If humanity moves to another planet it'll be a new chain anyway, even if using the Bitcoin implementation, so it's better to have some new designs ready :D

Only a few hundred million people will be able to use lightning directly self custodially because of how many channel opening txns can fit in a Bitcoin block

Others will be inevitably pushed to use trusted/centralized systems

So many Bitcoiners don't want to acknowledge this fact as if lying to themselves will somehow fix this

Once I am free a bit, I will type out the different experiences I had using it

DigiLocker used to be very shitty. When I started using it (before I found Bitcoin), you could open the app to show your driver's license or Aadhar card etc to the cops, and they could verify the authenticity of it, but the app won't work most of the time, so even they would only accept a physical copy

Now with it's OAuth like flow, it's actually useful for sharing your KYC info with apps that support it, without revealing your actual documents. But now I have no use for it anymore

Using giftwraps?

Also deploy https://github.com/verbiricha/goalz to another subdomain 🙏

heya.fund has been discontinued

Even a chair is made out of electrons and shit. But if someone asks what it is made of, any sane person would say metal or wood etc. I'm being dead serious, you should get yourself checked or talk to your loved ones about it. The way you are thinking right now shows very clear signs of mental illness

Which app is he using?

https://nostr.at/nevent1qqsgee0w8uqamkqjm8fe59pekcrz99zszn9uax8nt38j3nn7ekhzv7spp4mhxue69uhkummn9ekx7mqzyrxg6pewlhxxwm7t4s20dntgyhkux4mw2h4hs632ja0wqd9x5qnvkhrwlep

Oldest kind 1 note I could find

Can't believe chip manufacturing is such a centralized process that the entire world is reliant on Taiwan

The FOSS spirit is pretty much non existent in the semiconductor world

How do you give the reviewer credentials for using the app? Did you just mark the app as login not required, or did you give them some specific nsec to use the app with, or something else?

I got an app passed by adding a hardcoded check in the frontend to hide certain features from the reviewer by checking the phone number of the logged in user

Sci-fi always shows future space suits as either bulky pressure tanks or mech suits

Former NASA Deputy Administrator Dava Newman developed the BioSuit, which uses mechanical (textile-based) counterpressure instead of the traditional gas-pressurized mini-spacecraft approach

Humans live at 1 atm on Earth, but in a pure oxygen environment like a space suit or station, ~0.3 atm is enough. The BioSuit has reached ~0.25 atm in lower body prototypes, close to 0.3 atm in areas like the calves and thighs, although joints are still well below target

We are more likely to see something like this with advanced AR and AI integrated helmets in the future IMO

If Bitchat integrates Reticulum as well for routing then my dreams of nostr over reticulum will be complete

OpenSecret definitely has a good tradeoff of UX/privacy

I look like a Bhojpuri film star

Approach 2 is leaner, but tags don't mean the same thing across event kinds, so using `r` tags might not be a good idea

Some event kinds are always anchored to other things like comments. That's why NIP-22 was created.

Here is an example of a comment on a URL from NIP-22

{

"kind": 1111,

"content": "Nice article!",

"tags": [

// referencing the root url

["I", "https://abc.com/articles/1"],

// the root "kind": for an url, the kind is its domain

["K", "https://abc.com"],

// the parent reference (same as root for top-level comments)

["i", "https://abc.com/articles/1"],

// the parent "kind": for an url, the kind is its domain

["k", "https://abc.com"]

]

// other fields

}

Considering zap requests and receipts are also anchored to other events, maybe you can use the K, E, A, I, k, e, a, i tags with the zap event kinds?