First, I'd like to apologize if my consideration doesn't app...

Troy

npub104zp04wlgddf0w84tj8jul3w75e7ydcuuhsull2etste5040xm2qg285rf

hex

d54b66023dfd5b0961d0f4ae7610fcdc411c237ce53969692436753d58a3a5ef

nevent

nevent1qqsd2jmxqg7l6kcfv8g0ftnkzr7dcsguyd7w2wtfdyjrvafatz36tmcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs863qh6h05xk5hhr64erew0ch02vlzxuwwtcw0l4v4c9u686hnd4qrjjugh

Kind-1 (TextNote)

2026-02-14T15:22:29Z

↳ Reply to 945b9d23... (npub1j3de6gaj70jdr9muf0nq29wwps3wqxdqz3g7e5e67yyquhn6grkscw27tz)

Trying to understand this feedback. Are border rides not working? I haven't really tested intrastate rides yet.

First, I'd like to apologize if my consideration doesn't apply to your software. I haven't used your app, I'm just saying that borders are sometimes a hassle, and sometimes necessary, when it comes to software that involves a geographical area.

Depending on context, sometimes the distance from me (no matter where borders are) is the only important factor. In other instances, jurisdiction of silly rules are the main factor.

In the Oklahoma example I provided, let's pretend I'm using an app to buy a car. I'm willing to drive 75 miles to buy one, but only if it's in my state. Or if I'm job hunting, maybe I'm willing to commute 50 miles, but not if I have to go to Colorado.

This type of logic is missing from nearly every common software that makes use of geography.

Raw JSON

{
  "kind": 1,
  "id": "d54b66023dfd5b0961d0f4ae7610fcdc411c237ce53969692436753d58a3a5ef",
  "pubkey": "7d4417d5df435a97b8f55c8f2e7e2ef533e2371ce5e1cffd595c179a3eaf36d4",
  "created_at": 1771082549,
  "tags": [
    [
      "e",
      "9cfd42c20246d1bd4b1230431368129f123880d46a5bc5e4474bb80fd63d1d54",
      "",
      "root"
    ],
    [
      "e",
      "982fbfa598ae971d71a3dbf227aefd4261d502267f9e7d7d675f923095e37352"
    ],
    [
      "e",
      "92a821cdcad16539a8c4c86dd3893d56b3ad3eeccfb41b8ee30ec42cf6c37863",
      "",
      "reply"
    ],
    [
      "p",
      "945b9d23b2f3e4d1977c4be60515ce0c22e019a01451ecd33af1080e5e7a40ed"
    ],
    [
      "p",
      "7d4417d5df435a97b8f55c8f2e7e2ef533e2371ce5e1cffd595c179a3eaf36d4"
    ]
  ],
  "content": "First, I'd like to apologize if my consideration doesn't apply to your software. I haven't used your app, I'm just saying that borders are sometimes a hassle, and sometimes necessary, when it comes to software that involves a geographical area.\n\nDepending on context, sometimes the distance from me (no matter where borders are) is the only important factor. In other instances, jurisdiction of silly rules are the main factor.\n\nIn the Oklahoma example I provided, let's pretend I'm using an app to buy a car. I'm willing to drive 75 miles to buy one, but only if it's in my state. Or if I'm job hunting, maybe I'm willing to commute 50 miles, but not if I have to go to Colorado.\n\nThis type of logic is missing from nearly every common software that makes use of geography.",
  "sig": "ae3593d92b5a599d88b5f43da6fff6c1221deacdb675a79ca51b9a4866089cbc6cd8f851dfc45d8369853083df9482b200e994071317e95669841bdc133cce07"
}