>Young, virgin fire ant queens have wings (as do male fire ants), but they often cut them off after mating. Although, occasionally a queen will keep its wings after mating and through her first year.
Ants are crazy, man.
You cannot. Public posts only.
I assume we need this first: https://github.com/nostr-protocol/nips/pull/602
nostr:npub1thwgy0aws42kl49t5rnscdw3lwqf94rgagvqq45p8lj2edj2ev0q5jxvkn Hi, did you make a query layer on top of LMDB? I asked ChatGPT and then it hallucinated a link to your GitHub. https://chat.openai.com/share/a61ad372-f5cb-43b6-b037-b0848ab0371d
I learn everything through ChatGPT now. It's just way easier to ask a million questions until I understand it.
This is why Nostr exists, lmao


Thank you, ChatGPT.


Faster than Postgres? That would be surprising, but then again they proved it's faster to read from sqlite than to read from a file... even though sqlite is a file.
The Mostr bridge now has a new way to tag ActivityPub content on Nostr. This has been standardized in NIP-48! ๐ https://github.com/nostr-protocol/nips/pull/693
Previously Mostr events used the ambiguous and proprietary "mostr" tag to indicate people and posts from ActivityPub, eg:
["mostr", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526"]
Now those "mostr" tags are gone, and the same ting would instead be expressed like this:
["proxy", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526", "activitypub"]
Proxy tags can be used to locate the original content on the web. Not just for ActivityPub, but also for RSS, Matrix, Bluesky, and whatever else we decide to bridge.
Clients can use this to indicate messages from other protocols, and may choose to include a link to the source content. It could even be used to deduplicate content between bridges and merge threads.
Shout out to nostr:npub1cdzl6gys3egf4jewk786y7q2a7nmdldqevuf395pw6uk8j2uukcs7rl5s4 for authoring "FEP-fffd: Proxy Objects" and inspiring this NIP.
https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md
(Also, Pleroma fixed the Link bug, so I'll upgrade the bridge to the newest version of this FEP after a little while)
The Mostr bridge now has a new way to tag ActivityPub content on Nostr. This has been standardized in NIP-48! ๐ https://github.com/nostr-protocol/nips/pull/693
Previously Mostr events used the ambiguous and proprietary "mostr" tag to indicate people and posts from ActivityPub, eg:
["mostr", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526"]
Now those "mostr" tags are gone, and the same ting would instead be expressed like this:
["proxy", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526", "activitypub"]
Proxy tags can be used to locate the original content on the web. Not just for ActivityPub, but also for RSS, Matrix, Bluesky, and whatever else we decide to bridge.
Clients can use this to indicate messages from other protocols, and may choose to include a link to the source content. It could even be used to deduplicate content between bridges and merge threads.
ActivityPub has an "outbox" that all software implements because it's part of the standard. It shows a paginated list of all your public posts ever. But if you scrape it "without permission" people get very upset and say you're violating their privacy. Instead we use the inbox exclusively, and only deal with events we receive. Meanwhile Nostr relays are pure outboxes. Seems like a missed opportunity. And why do they leave it in all the software if people cry and scream about invading their privacy so much?
> Kafka is an open-source distributed event streaming platform
Seems like that could be useful to Nostr, which is based entirely on the idea of distributed event streaming.
To enable federation, at least one person on the Fediverse needs to have followed you through Mostr.pub. Then you need to be posting to any of the "write-relays" listed on mostr.pub. Then they should see your posts as long as the admin of their server hasn't explicitly blocked mostr.pub.
This is a cool thing that lets you run SQLite in a web browser because of OPFS, a new thing I just learned about: https://sqlocal.dallashoffman.com/guide/introduction
That's exactly what I was thinking.
We might even be able to let you type just your @ and scrape your followers without needing you to upload the CSV.
Since I don't use my Mastodon anymore and knowing that nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 is considering methods to work with an exported ActivityPub profile, I just manually picked my 10ish follows, routed them via mostr.pub and have them in #Nostr now.
And, once I have my export archive, I am clearing out the instance. Running `tootctl self-destruct` is gonna feel weird. x)
So! Show me all the neat EXPLOSION! gifs that you got :D
I need to automate that process.
I wouldn't use Postgres again after how much of a pain it was in Pleroma. The better question is why not just use LMDB if you're going to go through all this trouble. They're equally hard, but at this rate LMDB would be easier.
You can literally paste errors at ChatGPT and it will know exactly what's going on. https://chat.openai.com/share/5c7e1d2b-6a2b-4064-92f3-d7ee11a4fcd7
The main limitation of SQLite is that it locks up when you try to write too much to it at once. This makes it "not a great use-case for social media". Not even due to your posts, but because of all the likes and emoji reactions you guys do. I still haven't hit any of those limits in my own experience. But writing to multiple database files could help it a lot, I bet.
primal.net is apparently indexing the entirety of Nostr on a cluster of SQLite databases and serving it in microseconds. I'm intrigued by this, so I'm figuring out how to run Julia code to see it for myself. Also brewing some sen-cha. ๐ต