Used the provided pricing, yes. I assumed that Nosflare uses the same set of indexes (NFDB supports composite indexes, I do not think Nosflare does) and based it off of Nostr.land’s read amounts.
The CPU time was not too relevant, with a huge chunk of it being D1 read costs.
I won’t get into the fact that D1 is probably one of the buggiest products to come out of CF
semisol
npub122…cgrkj
2025-06-12 07:12:09
in reply to nevent1q…lu43
Author Public Key
npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkjPublished at
2025-06-12 07:12:09Event JSON
{
"id": "e34d2ad24fab8be14441587be497b373fb6c77294af9039ced48d96f69f32053",
"pubkey": "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"created_at": 1749712329,
"kind": 1,
"tags": [
[
"e",
"bb99873016c3741b4e45f3cf36bc6233edde8bf9276c702745018458f29870d5",
"",
"root"
],
[
"e",
"dced76aac53c94e9d9df99132d49f321d02c84f42c2c0b2bcb3f615b4c615a2d",
"",
"reply"
],
[
"p",
"d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df"
]
],
"content": "Used the provided pricing, yes. I assumed that Nosflare uses the same set of indexes (NFDB supports composite indexes, I do not think Nosflare does) and based it off of Nostr.land’s read amounts.\n\nThe CPU time was not too relevant, with a huge chunk of it being D1 read costs.\n\nI won’t get into the fact that D1 is probably one of the buggiest products to come out of CF",
"sig": "3b24c648079c93a49d342d3c0499ecbff6ba757f5027f825aa8efbe97a841cb919c145f5c73e36a994e9136b818fd4940f72d0fe6bb31666f8c92e50617a2d8a"
}