#meme

ellama works with ollama and emacs

Do you meditate? Why/why not?

#asknostr

Wrote Scott Bessent a letter. Sent it in with my tax payment to the IRS for the 2023 tax payment plan I was slow rolling $50 into monthlt. Turns out you can only use online payment so many times before it stops you. Figured if I'm mailing a check, might as well mail a letter too.

Pretty sure he won't get it but maybe.

Seriously considering putting two RTX 6000 in my upcoming build machine. Puts the price up an order of magnitude, but truly private AI might be a worthwhile investment.

Never played with GPUs before, so informed thoughts welcome?

Is the SRI project good ng to host its own pool?

The reason you are seeing vibe code projects getting abandoned everywhere is because vibe coding is _grueling, never-ending labour_, like all software development. It is not fun. It is work. And the less foundational knowledge and experience you have about software development, testing, systems architecture, symbolic logic, and DevOps, the faster it becomes work, and the faster the project becomes abandoned, or melts down into a buggy mess.

It seems fun.

At the beginning.

Might actually be something nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 that piques your interest. Basically trying to achieve a high availability application environment with minimal moving parts and a smoother learning curve.

that's concerning 😱🙄

I do see a lot of devs self-promotion here but that is not a problem though as long as the app covers non-functional requirements eg security 😬 — it does what it says on the tin too

I have lost all trust in almost everything in the Bitcoin/Nostr space in terms of security.

From hardware wallets including the most popular Bitcoin-only ones, to wallet services, to Nostr apps, to LN wallet software…

AI slop will only make this worse. This entire ecosystem is built like a house of cards.

I'm digging vertical tabs in Brave.

GM. Bitcoin in money.

Probably for the best I signed up again after years away and it’s non stop drama and engagement farming. Still the level of disfunction on knots vs core is front and center there.

I haven't been a huge fan of core for a while now and personally run libbitcoin instead, but the amount of mindless stuff being said by people about core 30 is disturbing because it shows that the bitcoin community is clearly a lot dumber and more easily manipulated than it was a decade ago. Or maybe it's just endless September and these people are all new (post 2017 or 2021).

Welcoming new beginnings 🕉️

Status games make too many decisions in too many places.

lets play a game

guess the usd bitcoin price exactly a month from now

sep 26th 2025 - 0414 UTC

closest guess will be zapped 5555 sats

only guesses made within the next 24 hours qualify

(if i think you are a bot you are disqualified)

Bitcoin

Gm 🌞 ☕️

I successfully avoided caffeine (no teas and coffee) all weekend.

And I can tell you it was rubbish.

Absolutely pants. Zero out of ten.

I would warmly recommend Peter schiff and Christine Lagarde try it.

Anyway. Mild headaches, flat mood and the desire to do very little.

I am an addict.

Is it worth trying to cut out caffeine completely? Do you get any benefits?

#Caffeinestr #Coffeestr #Teastr

From ancient empires to modern democracies, power flows from violence, not consent.

We like to think we can do things in secret, that the Lord will not see, but we are deceiving ourselves. He knows everything we do and every thought we have. No seed phrase is hidden from his sight. We are more transparent to him than the blockchain. Knowing this, strive to be as innocent as doves, as open as a small child. Such are the citizens of the Kingdom of Heaven, God’s citadel

#devotional

#realy #devstr #progressreport

the full text search is theoretically now implemented

it iterates the new fulltext index searching for word matches

then it checks that the rest of the filter criteria match, and eliminating candidates that don't have at least one of the criteria, i.e.:

- eliminates results outside of since<->until,

- that aren't one of the kinds requested,

- that aren't published by one of the specified pubkeys,

- that don't have the requested language tag, and

- that don't have one of the tags in the filter

then it groups the result fulltext index entries by same event into a unit and creates a map of them

then it converts the random iterating map into a straight array

it iterates the array and calculates the distance between the first and last word match in the sequence of the text of the event

then it segments the results by number of words that match in each event, grouping the ones with the same number of word matches into groups

then it calculates the distance between the first and last word matches in the text (the terms can appear multiple times but are sorted by their appearance, this is just an approximation, since words can appear multiple times)

then it gets a list of all the terms in the event by their sequence number in the original search, and with this array it counts how many of those matches are in ascending order matching the search terms

with these two metrics, we can calculate relevance, as the higher the number of items in matching sequence the more relevant, and the closer they are together, the more likely they are to match the search text

then we sort the groups of same-count of words from the search text by distance AND sequence, meaning the top results have the lowest distance and the highest sequence

then with the segments individually sorted, we zip them back together into a list, extract their event id, pubkey and timestamp and return that to the caller (this same result is used by the filter in the HTTP API so it can filter out pubkeys and sort the results by timestamp descending or ascending according to the query parameters).

and finally, then it trims the list down to the number of results requested in the limit *or* the configured max limit (512, generally, but the http endpoint will allow 1000 for unauthed users and 10000 for authed users, as it only returns the event id, so the client can paginate them on their side)

i know that all sounds complicated but it's now all written and this will enable a fairly decent relevance sorted full text search for nostr text events.

the hard part now is going to be testing it, i will probably make two endpoints for this, one will be disabled later, but that one will return the full events in the result, as an array, so i can see them in the api, and squash any bugs or logic errors in the search code... and also see how long it takes for producing the results.