Biendeo on Nostr: Just as you mentioned that, I was getting the same errors on my instance. Nitter logs ...
Just as you mentioned that, I was getting the same errors on my instance. Nitter logs started spitting out a lot of timeout logs, and a few OSError, msg: Invalid argument logs. There’s an underlying api.twitter.com URL that was also returning a HTTP 500, so my hunch is Twitter just broke something on their end rather than something weird with our setups.
https://f.biendeo.com/s/dpm7l4bp.txtPublished at
2023-04-20 23:28:14Event JSON
{
"id": "ffcd3f3f78684b853a66baa86791a898c0d6bb65317e2ea1e0ff7bcc9a169f10",
"pubkey": "fad6d602564f2acf9afb254ffc210e3c5a32040f9f189c01ec88b627e57c533c",
"created_at": 1682033294,
"kind": 1,
"tags": [
[
"p",
"79c4b3e2b1e7d8d74fa652cdc1dee37f9cd08fefdc13a79f8d1146c0b69fd1fb",
"wss://relay.mostr.pub"
],
[
"e",
"dfc5718641b1787c35e206aff7d5c628de51b4d6ea4ed81287478cdeb107f8c9",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://m.biendeo.com/objects/20b22ad3-dec2-41b8-b78b-1e9ea83f0ca8"
]
],
"content": "Just as you mentioned that, I was getting the same errors on my instance. Nitter logs started spitting out a lot of timeout logs, and a few OSError, msg: Invalid argument logs. There’s an underlying api.twitter.com URL that was also returning a HTTP 500, so my hunch is Twitter just broke something on their end rather than something weird with our setups. https://f.biendeo.com/s/dpm7l4bp.txt",
"sig": "427a0972cbffdd29ede39ba7a16559535ffa997269541738c0ef340b369492dbb5121161a77d14fcdac27864258eb5f53cd6adb1d5bf5d7f2f437a246adfe4e4"
}
