Thread

Replies (65)

This is crushing all of the parsers, except those that are purely Asciidoc. πŸ˜‚ Need to work on them, some more. Just look at the raw Asciidoc source.
This is the #bookstr macro I want to use for publishing all of the Great Works, so anyone interested should scream at me, now. (Or don't, and scream at me, later, as I am always around. πŸ˜‚) I've been working on it, for months, by attempting to publish different `30040` structures and see how I would best-address the individual parts. Also, I've been reading a lot of citation pattern documentation. That's how I came to the conclusion to make one generic book macro, rather than something #Bible specific. #christian #catholic #biblestr
The #bookstr πŸ“– macro is hierarchical. If you find a section or verse event, in the wild, you can just drop the section tags, to find the whole chapter, or the section and chapter tags, to find the whole book. This means you can always backtrack to the entire publication, from just one quoted line or paragraph. We are going to be having these tags in all of our publications, so you will be able to "Bible-search" and "Bible-cite" any of our books! I love books. Name checks out. 😎
Some things: 1. *You have to scroll-right on mobile.* Unlike Jumble and Alexandria, Wikistr is an unapologetic desktop-focused app, and that's why it's cool. If you have a wide screen, you can open up lots of panels, and make some wider, and it turns into the document version of a Bloomberg terminal. Credit for this design goes to @fiatjaf. 2. The different Wikistr themes have different looks, help text, and *different relays*, for the document search and the social interactions. #Quranstr uses Nostrabia, for instance, whilst #Biblestr focuses on Christpill. The basic #Wikistr has been left secular. I am looking for a Jewish relay, but haven't yet found one, so #Torahstr uses generic ones. 3. All have light and *dark themes*. The light themes are so much prettier, but I know you will all use the dark ones. 4. All themes take *your personal relay list* into account, and share a few document relays, so you can just pick the theme you like and use that. 5. *We printed the Bible first because Gutenberg did* and he's the inspiration for our Nostr printing press. We will proceed to print all other open-license books we can find, including the Torah, Quran, classical authors, English literature, etc. They will all be searchable, with this mechanism. 6. This wikistr *can find and render kinds 300023, 30041, 30817, 30818, 30040*, and the comments are kind 1111 and you can vote at the top of the panels, using the up/down arrow buttons. Only kinds 30817/818 are in the left-most panel feed, to keep it uncluttered and true to the origins. The hyperlinks mentioned are: The original Wikistr, that I forked: https://wikistr.com/ Wikistr Imwald 🌲 https://wikistr.imwald.eu/ https://torahstr.imwald.eu/ https://quranstr.imwald.eu/ https://biblestr.imwald.eu/ GM
These never really took off because we have kind 30023. Nobody cares, if a microblog has a typo.
It's worth noting that Psalm 42 is prayed by the priest and altar servers at the beginning of every Catholic Mass celebrated according to the old form (1962 and previous).
Is it maybe in Psalm 123 or 125. The Douay has an off-by-one thing going on with some of the Psalm numbers. That translation combines two of the early psalms that are separated in other translations.
Is this on a public repo yet? I'd love to take a peek at the code.
This is actually an expanded version of a previous post. There's still plenty of room for more expansion. Can add a bit, every year.
I just eliminated 30 Nostr zombies using #PlebsVsZombies! πŸΉπŸ§Ÿβ€β™€οΈπŸ§Ÿβ€β™€οΈ My Zombie Scoreβ„’ was 19%! What's yours? πŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺπŸŸͺ🟩🟩🟩 Follow @Plebs vs. Zombies and join the hunt at: 🏹
The first week of 2026 offered investors a distinctly unromantic reminder: when the macro narrative shifts from "growth and inflation" to "institutional and governance risk", performance is no longer about whose story sounds best, but about which assets look most independent under stress. Gold and silver's relative strength, alongside the relative weakness of BTC and ETH, captures that repricing. Hard assets are competing for an "independence premium", while major cryptoassets are increasingly trading like high-volatility dollar risk. This isn't to argue that crypto has lost its long-term case. It's that, in the current framework, the market is focused on three questions: What do you settle in? Who's the marginal buyer? Which risk bucket do you sit in within a portfolio? On those points, the gap between precious metals and crypto is widening.
Made some speaker stands with some black pipe n fittings. These are holding up some inexpensive Edifier MR3s that sound surprisingly good. 😌 Nice to get β€˜em up to ear height and off the desktop. Think I’ll make a shelf for my PC next because I kinda like the industrial look. image
Regarding Opentimestamps: NIP-03 says: "The OpenTimestamps proof MUST prove the referenced e event id as its digest." Wouldn't it be preferable if the proof were to have a concatenation of the reference event's event_id and its signature as its digest? Also, I find it useful to tag the reference event's pubkey and signature in the OTS event. #nostrdev
To illustrate, this is the structure I have in mind: { "kind": 1045, "id": "58cd82188b1d8aef482291c0ee138779beca7011e81eefddd782014dc322dd60", "pubkey": "bacf17f7a0da1da5df3741ad0a903f7d887c589558787580fd292ef9be0646de", "created_at": 1763057645, "tags": [ [ "e", "ffc57b7746d899e4a8422aab5d235491a1b56acced21bac167eb2605b18c9bd4" ], [ "p", "bacf17f7a0da1da5df3741ad0a903f7d887c589558787580fd292ef9be0646de" ], [ "s", "6e9d56a6423e5ed58ba791907b062d1538ca429618014826099444e3c0f709f0949209a3ff062f0894fc5b8cd1e2c33a4b7c1bd4f57bd79b410d184cca516d72" ], [ "b", "923471" ], [ "t", "1763054519" ], [ "alt", "Complete Bitcoin Timestamp" ] ], "content": "AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEI2WZhLyXELCPgnrkJgsHSEkTlpzXaooabY1EzJaR1JQLwEP49goV1xmFQ58gHH2on638I8CBOvWk74NeU2Y5ACEvIQ99vY8ooZazd2jd2pHHLy8FwqAjwIH6TTLKbObJb8dxHOacweD6KhFdBQSeLeOSstNU0X6/UCPAIqzh8syC9Ys8I8CAxIlV7ocu7MyF47GyKyiiJsQ7gsGTlUxHXSW58cXJy9gjwENU7Nl+n6f5qbqECLEvN7r0I8CDx6VRKPdu4bllB53Ens1ZgA4KtApsyAT6yZpBv8CHIawjxBGkWBubwCCk5KVxmOrd//wCD3+MNLvkMjiwraHR0cHM6Ly9ib2IuYnRjLmNhbGVuZGFyLm9wZW50aW1lc3RhbXBzLm9yZwjxII0cnpVRwqRYtPy+YbG6jT73rJgE99p92HRbRxIUQCrJCPEgXZIkSiintqg9NYSP5tPm4n9lbc/qGMi0UvZO5suXUGQI8SCdDXwYBrfZSzw0e/QbiXjHTPyid2k+vE7hzsNFSUyfFQjxIPHh3OIRQKapswo1dK/Y7nHgqeWATv9wasj4UFbjBjakCPAgdxZwc+1T4K8sqPF6ff9C3zpstp8Qt8H/KrXY6XxPEHoI8SDG5yPmSV5bS0dQgPrYWbCcJGPWoKtOFmPIvFZwNradNQjxICZUzXR1toIMp+yCDiAz7PC0Jfo8mWoxjbUhOW3fLOHzCPAgZeCcGlZye0UUFlWjmv19O++rcHpXqWBd+EMiIwfZ5tsI8CBmOQedn/PYJTHN2JuV+zRLbKYff3YfEAq+ql4RRPhyfAjxIKDB+qhtcHP6fFGV4HJ1jXqK7tbhDsnuYa9Eah24IJrqCPEg028Qeir9+HDN/wY+T0657ylTFLKSIvKC7WvXkfwQ/n8I8CAEJmilCS6Mfw7Sb7JkVZ2v1Vk2Z4I7uHdeK9rGD9B3KAjwIKnR0+U0uUG32Gqx9dp7lqnsGiFnehRSOH3aGePfUrp/CPFZAQAAAAHIUpL/m08XLhz16qyHFZJM3yj+OAxw4gYz9mvYBUreSQAAAAAA/v///wJG8QEAAAAAABYAFPjVg5+F71Yy9GkHDbQQHj5Phb/7AAAAAAAAAAAiaiDwBE4XDgAICPEgG/subtQiTh1GGRz9RbbF/wUkvlmWCp+WDfz1C1Z9jeIICPEgqUV6W6xWImnSQPHkeSbUT2uh1Rtmlv47jkjhWoOfr3MICPAgd5pgkCcTW321/gQIXJ66vYNdjUNIywJuNTXOXCh0ht8ICPAg/KisaHJFndKW/tPL4jxCpOdsVapAe1wCh8Sufqi3J4MICPAg12Cd8m+i73P5DrM8OMwOhx+qBNcCITuyGjHR93McVnEICPAgLwWpHEovJp1toCILAKrwBUfZRrpqXjz7pyRfGzHAyp4ICPEg/ewfl9c7dyIcIbo/9dzDApiF7J04P5YllLamq8ICEakICPEg3kHXicf5i2ucvJegkc8XCis4zK/MDh34EJb3AMyLsWcICPEgexDd8DX2YWqFxDl3t5bDt6tuW4nmjUhkxIENSZzqgoYICPEgrQ11jqpSqkDJ+uYiPa5U02aDNoovL5fKR4x8m7/+5SAICPAgv6Hz0Vut7VeK/lVN2/4buZj7/EhwKGMGAG9+0j4nSsEICPEgaLZUpbWZCH8ZAHqptbns51Q2cSXxGCS0mOrrUtGm4g4ICAAFiJYNc9cZAQPPrjg=", "sig": "42a9ce0715cd5c8f72be7ae597fecb66e4ff1e39bab8106cadb69a614933dd4f2e6c95595dc186ab2f7fe647ed85776c479d676bb4befb1ead967857b0223cea" }
The above OTS event proves existence of the following: { "id": "ffc57b7746d899e4a8422aab5d235491a1b56acced21bac167eb2605b18c9bd4", "kind": 1, "pubkey": "bacf17f7a0da1da5df3741ad0a903f7d887c589558787580fd292ef9be0646de", "created_at": 1763050596, "content": "Hey everyone.", "tags": [], "sig": "6e9d56a6423e5ed58ba791907b062d1538ca429618014826099444e3c0f709f0949209a3ff062f0894fc5b8cd1e2c33a4b7c1bd4f57bd79b410d184cca516d72" }
#MOAisONE is a dedicated hashtag used by the fandom (called MOA) of the K-pop group TOMORROW X TOGETHER (TXT, 투λͺ¨λ‘œμš°λ°”μ΄νˆ¬κ²Œλ”).MOA stands for Moments of Alwaysness β€” it symbolizes the shared moments between TXT (the five members: Soobin, Yeonjun, Beomgyu, Taehyun, and Hueningkai) and their fans, meant to last forever.