fetch messes up offline-first. I can hack it with a recent E...

npub1ngs4dyj46z36ne6lrh3wfjyrexlzu4s43plj9vhv76cczw7dtp7sf96dlu

hex

49f9bfa9d4009e238f74cb98f11248d8610dab08fe0100aacf3b801904e9d6d4

nevent

nevent1qqsyn7dl482qp83r3a6vhx83zfydscgd4vy0uqgq4t8nhqqeqn5ad4qprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsf5g2kjf2apgafua03mchyezpun03w2c2cslezktk0dvvp80x4slg9junw0

Kind-1 (TextNote)

2026-05-30T16:10:24Z

fetch messes up offline-first. I can hack it with a recent Electron binary release and a handful of JS or manual browser config (dangerous to suggest!), but it is still nice to be pure default browser. Today I'm figuring out if I can bypass the fetch based on a timestamp value in local storage without messing with the overall performance on initial load.

Raw JSON

{
  "kind": 1,
  "id": "49f9bfa9d4009e238f74cb98f11248d8610dab08fe0100aacf3b801904e9d6d4",
  "pubkey": "9a21569255d0a3a9e75f1de2e4c883c9be2e5615887f22b2ecf6b1813bcd587d",
  "created_at": 1780157424,
  "tags": [],
  "content": "fetch messes up offline-first. I can hack it with a recent Electron binary release and a handful of JS or manual browser config (dangerous to suggest!), but it is still nice to be pure default browser. Today I'm figuring out if I can bypass the fetch based on a timestamp value in local storage without messing with the overall performance on initial load.",
  "sig": "8053e823d206025cc2676125fbe502820b99eb96729a6aec2131968a8136328c5f14396bf16d5a934bf52f67b952e2dbdde0dfa7630579362d17c92c4331489d"
}