# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196323
# self = https://watcher.sour.is?offset=152258
# next = https://watcher.sour.is?offset=152358
# prev = https://watcher.sour.is?offset=152158
Have a bit of a conundrum I need your thoughts on... I have stuck up early conversations with the developer of a nice little Document database in Go called clover. He has kindly offered to collaborate with me on a v2 rewrite (_or improvements_) to my Bitcask. He very rightfully points out that the project (Bitcask) would benefit greatly from the community (Github in this case) and potential growth from the exposure there. I retorted with Microsoft's recent blatant theft of millions of open source projects to train their CoPilot models without so much as attributing the works they used to drive what is now a sellable product.
What do I do? We're at a bit of a "sticking point" here and I'm not really willing to compromise. Microsoft are basically cheating, stealing assholes and should be sued and the execs who decided it was a good idea to steal content to build their product, thrown in. jail.
Have a bit of a conundrum I need your thoughts on... I have stuck up early conversations with the developer of a nice little Document database in Go called clover. He has kindly offered to collaborate with me on a v2 rewrite (_or improvements_) to my Bitcask. He very rightfully points out that the project (Bitcask) would benefit greatly from the community (Github in this case) and potential growth from the exposure there. I retorted with Microsoft's recent blatant theft of millions of open source projects to train their CoPilot models without so much as attributing the works they used to drive what is now a sellable product.
What do I do? We're at a bit of a "sticking point" here and I'm not really willing to compromise. Microsoft are basically cheating, stealing assholes and should be sued and the execs who decided it was a good idea to steal content to build their product, thrown in. jail.
@movq Indeed, that's terrible! Back in the days when my mate recorded the bike tours, we noticed that sometimes the reception was really poor. Whenever it took about three to five minutes or so until the location was found, we knew, the GPX is not going to be great that day. Sometimes there was a jump of several kilometers right after starting the track when we couldn't be bothered to wait for enough satellite contact. Our top speed was astronomically high. :-D
[47°09′06″S, 126°43′47″W] Sample analyzing complete -- starting transfer
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.
Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:
https://movq.de/v/f95a556bed/sketch0.png
Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.
On a bad day, it would look more like this:
https://movq.de/v/f95a556bed/sketch1.png
Basically useless.
And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.
(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.
Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:
https://movq.de/v/f95a556bed/sketch0.png
Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.
On a bad day, it would look more like this:
https://movq.de/v/f95a556bed/sketch1.png
Basically useless.
And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.
(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
@lyse Depends, sometimes it’s within specs (you can expect something like 3 to 15m accuracy 68% of the time, IIUC), sometimes it’s 200m off (like in my test this morning) and doesn’t get better even if you wait and don’t move. But I admit that was an extreme case that I’ve only seen a couple of times.
Obviously I won’t share my real GPS tracks here. 😅 So I made a couple sketches. On a good day, it would look something like this:
https://movq.de/v/f95a556bed/sketch0.png
Green being a GPS track made with a good tracker. It’s already wobbly, even if you’re walking in straight lines, but it mostly matches your actual path. Red is the bad phone. Maybe I could have lived with this if it had been a cheap phone (which it wasn’t). In fact, my previous phone was *way* cheaper but had much better results, comparable to the green line, so this was quite a bit unexpected and disappointing.
On a bad day, it would look more like this:
https://movq.de/v/f95a556bed/sketch1.png
Basically useless.
And most of the time, it would take several minutes to get a “fix” in the first place. Meaning I was standing in front of my house for 5-10 minutes, waiting. The better phones get a fix within 5-30 seconds.
(I suspect that somehow A-GNSS was broken or partially broken on the bad phone, but no idea, really. The GPS hardware is a blackbox.)
Recovery: 3.00 miles, 00:12:01 average pace, 00:36:02 duration
#running #treadmill
Recovery: 3.00 miles, 00:12:01 average pace, 00:36:02 duration
#running #treadmill
Recovery: 3.00 miles, 00:12:01 average pace, 00:36:02 duration
#running #treadmill
@movq He's not following me (or at least not advertising his feed in the User-Agent header), so he probably doesn't resolve this mystery.
@movq How far off was your GPS location?
[47°09′31″S, 126°43′34″W] Analyzing samples
[47°09′31″S, 126°43′41″W] 3844 days without news from Herve
Pinellas County - 5 mile progression: 5.02 miles, 00:09:42 average pace, 00:48:41 duration
kept it easy since it was the first week. the first couple miles took a bit to keep locked on but the rest were fine.
#running
Pinellas County - 5 mile progression: 5.02 miles, 00:09:42 average pace, 00:48:41 duration
kept it easy since it was the first week. the first couple miles took a bit to keep locked on but the rest were fine.
#running
Pinellas County - 5 mile progression: 5.02 miles, 00:09:42 average pace, 00:48:41 duration
kept it easy since it was the first week. the first couple miles took a bit to keep locked on but the rest were fine.
#running
@mckinley This is a bit worrisome 🤯 Anyone published mitigations to this? 🤔 Be keen to hear if anyone has blocked this at any network level. I certainly would go that far if Apple doesn't fix their shit™ -- But as the author points out, corporations are very fragile to the state's will (_which I assume means any corporation_) 😱
@mckinley This is a bit worrisome 🤯 Anyone published mitigations to this? 🤔 Be keen to hear if anyone has blocked this at any network level. I certainly would go that far if Apple doesn't fix their shit™ -- But as the author points out, corporations are very fragile to the state's will (_which I assume means any corporation_) 😱
@mckinley This is a bit worrisome 🤯 Anyone published mitigations to this? 🤔 Be keen to hear if anyone has blocked this at any network level. I certainly would go that far if Apple doesn't fix their shit™ -- But as the author points out, corporations are very fragile to the state's will (_which I assume means any corporation_) 😱
[47°09′06″S, 126°43′12″W] Reading: 1.35000 PPM
[47°09′41″S, 126°43′28″W] --white noise--
🧮 USERS:1 FEEDS:2 TWTS:766 ARCHIVED:67364 CACHE:2259 FOLLOWERS:14 FOLLOWING:14
Tenho andado alhures, mas amanhã vou estar aqui batidinho pra festejar convosco o primeiro ano da #ciberlandia :ablobcatbongo:
Tenho andado alhures, mas amanhã vou estar aqui batidinho pra festejar convosco o primeiro ano da #ciberlandia :ablobcatbongo:
Dernier jour de vacances à Albufeira :(
Dernier jour de vacances à Albufeira :(
@lyse Curious. 😅 I only know him as hiltjo.
@lyse Curious. 😅 I only know him as hiltjo.
@lyse Curious. 😅 I only know him as hiltjo.
[47°09′22″S, 126°43′42″W] Automatic systems disengaged due to thunderstorm
@movq Yeah, getting things under the keys is very annoying.
I either trashed my Super_L key by using it all the time, or there’s a grain of salt stuck under it. Damn those rubber dome keyboards.
I either trashed my Super_L key by using it all the time, or there’s a grain of salt stuck under it. Damn those rubber dome keyboards.
I either trashed my Super_L key by using it all the time, or there’s a grain of salt stuck under it. Damn those rubber dome keyboards.
@lyse „evil_bob“? Where did you get that nickname? 🤔
@lyse „evil_bob“? Where did you get that nickname? 🤔
@lyse „evil_bob“? Where did you get that nickname? 🤔
Saw a dead fire salamander in the forest. :-(
[47°09′47″S, 126°43′06″W] Weather forecast alert -- storm from SW
[47°09′53″S, 126°43′29″W] Transponder fixed
Pinellas County - Easy: 3.04 miles, 00:10:49 average pace, 00:32:51 duration
nothing really to note here
#running
Pinellas County - Easy: 3.04 miles, 00:10:49 average pace, 00:32:51 duration
nothing really to note here
#running
Pinellas County - Easy: 3.04 miles, 00:10:49 average pace, 00:32:51 duration
nothing really to note here
#running
[47°09′48″S, 126°43′29″W] Transponder still failing
[47°09′59″S, 126°43′37″W] Transponder malfunction
🧮 USERS:1 FEEDS:2 TWTS:765 ARCHIVED:67352 CACHE:2260 FOLLOWERS:14 FOLLOWING:14
I added an atom feed for this chat, just for the hell of it.
[47°09′06″S, 126°43′03″W] Raw reading: 0x653965B1, offset +/-4
7b7c7 here, gotta love CGNAT and ISP-level DHCP. Testing IE6's gopher implementation on a vintage machine.
@mckinley Never used that. i typically just use official debian testing image to install with.
@Soficious@Soficious ei, vi-te no techmeme! 
screenshot do techmeme com um dos toots da Soficious em destaque
@Soficious@Soficious ei, vi-te no techmeme! screenshot do techmeme com um dos toots da Soficious em destaque
[47°09′49″S, 126°43′09″W] 3842 days without news from Herve
Oh. I pulled up the feed and its at eli.li instead of theoatmeal.com
Oh. I pulled up the feed and its at eli.li instead of theoatmeal.com
[47°09′54″S, 126°43′26″W] Not enough data -- sampling finished
Pinellas County - 75': 7.84 miles, 00:09:36 average pace, 01:15:15 duration
bit slow and tight in the first mile or two but was able to eventually find my stride and rhythm. actually felt pretty easy which i hope is a good sign.
#running
Pinellas County - 75': 7.84 miles, 00:09:36 average pace, 01:15:15 duration
bit slow and tight in the first mile or two but was able to eventually find my stride and rhythm. actually felt pretty easy which i hope is a good sign.
#running
Pinellas County - 75': 7.84 miles, 00:09:36 average pace, 01:15:15 duration
bit slow and tight in the first mile or two but was able to eventually find my stride and rhythm. actually felt pretty easy which i hope is a good sign.
#running
[47°09′23″S, 126°43′11″W] Taking samples
[47°09′26″S, 126°43′48″W] Automatic systems disengaged due to heavy rain
@marcorocco That sounds really yummy 😋
@marcorocco That sounds really yummy 😋
@marcorocco That sounds really yummy 😋
@xuu curious in what way?
@xuu curious in what way?
@xuu curious in what way?
@prologic curious that this feed has a image from a 3rd party domain.
@prologic curious that this feed has a image from a 3rd party domain.