# 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 196309
# self = https://watcher.sour.is?offset=160425
# next = https://watcher.sour.is?offset=160525
# prev = https://watcher.sour.is?offset=160325
Spectre also looks quite good.
[47°09′52″S, 126°43′03″W] Carrier too weak
[47°09′39″S, 126°43′43″W] Bad satellite signal -- switching to analog communication
@prologic check the links on this twtxt. You are talking to the void. 😊
[47°09′27″S, 126°43′30″W] Saalmi, retransmit, please
[47°09′36″S, 126°43′54″W] Transfer aborted
Maybe some kind of option that when enabled will collapse multiple posts from the same feed and only show the top most recent one, with some kind of UI/UX that indicate "N more today..."?
Maybe some kind of option that when enabled will collapse multiple posts from the same feed and only show the top most recent one, with some kind of UI/UX that indicate "N more today..."?
Maybe some kind of option that when enabled will collapse multiple posts from the same feed and only show the top most recent one, with some kind of UI/UX that indicate "N more today..."?
Is Yarn.social dead or just too niche? (uyrrria) 🧐
Is Yarn.social dead or just too niche? (uyrrria) 🧐
Is Yarn.social dead or just too niche? (uyrrria) 🧐
I'd also be very interested to hear what some other users of yarnd have to say, sadly there are only a handful of pods around that I'm aware of and/or that peer with my pod (twtxt.net) 😢
Maybe Yarn.social/Twtxt has become boring or too niche? 🤔 Anyway cc @eldersnake @xuu @stigatle @abucci
I'd also be very interested to hear what some other users of yarnd have to say, sadly there are only a handful of pods around that I'm aware of and/or that peer with my pod (twtxt.net) 😢
Maybe Yarn.social/Twtxt has become boring or too niche? 🤔 Anyway cc @eldersnake @xuu @stigatle @abucci
I'd also be very interested to hear what some other users of yarnd have to say, sadly there are only a handful of pods around that I'm aware of and/or that peer with my pod (twtxt.net) 😢
Maybe Yarn.social/Twtxt has become boring or too niche? 🤔 Anyway cc @eldersnake @xuu @stigatle @abucci
Another feature as mentioned in #iq4rusa is using filters on the Timeline and/or Discover views. One of the most common "workflows" I use is to go to "Discover" and use the "Without replies" and "Hide my posts" filters to see if there's anything new and interesting in my pod's cache I haven't seen before or maybe could reply to (or not).
Of course as I've locked down registrations on my pod anyway (have kept it locked down now for months) due to SPAM accounts and bots just creating rubbish accounts/feeds, this workflow may no longer be all that useful? hmmm 🧐
Another feature as mentioned in #iq4rusa is using filters on the Timeline and/or Discover views. One of the most common "workflows" I use is to go to "Discover" and use the "Without replies" and "Hide my posts" filters to see if there's anything new and interesting in my pod's cache I haven't seen before or maybe could reply to (or not).
Of course as I've locked down registrations on my pod anyway (have kept it locked down now for months) due to SPAM accounts and bots just creating rubbish accounts/feeds, this workflow may no longer be all that useful? hmmm 🧐
Another feature as mentioned in #iq4rusa is using filters on the Timeline and/or Discover views. One of the most common "workflows" I use is to go to "Discover" and use the "Without replies" and "Hide my posts" filters to see if there's anything new and interesting in my pod's cache I haven't seen before or maybe could reply to (or not).
Of course as I've locked down registrations on my pod anyway (have kept it locked down now for months) due to SPAM accounts and bots just creating rubbish accounts/feeds, this workflow may no longer be all that useful? hmmm 🧐
Hah 🤣 @dfaria Your @dfaria.eu feed really does consume about >50% of a "Discover" search with filters "Without replies" and "Hide my posts". 🤣 
36/2 = 18 at 25 Twts per page, that's about ~72% of the search/view real estate you're taking up! wow 🤩 -- I'd be very interested to hear what ideas you have to improve this? Those search filters were created so you could sift through either your own Timeline or the Discover view easily.~
Hah 🤣 @dfaria Your @dfaria.eu feed really does consume about >50% of a "Discover" search with filters "Without replies" and "Hide my posts". 🤣 36/2 = 18 at 25 Twts per page, that's about ~72% of the search/view real estate you're taking up! wow 🤩 -- I'd be very interested to hear what ideas you have to improve this? Those search filters were created so you could sift through either your own Timeline or the Discover view easily.~
Hah 🤣 @dfaria Your @dfaria.eu feed really does consume about >50% of a "Discover" search with filters "Without replies" and "Hide my posts". 🤣 36/2 = 18 at 25 Twts per page, that's about ~72% of the search/view real estate you're taking up! wow 🤩 -- I'd be very interested to hear what ideas you have to improve this? Those search filters were created so you could sift through either your own Timeline or the Discover view easily.~
One thing to be clear about here is that it was never my intention for a pod's "front page" (Discover view when not logged in) to be any kind of "listing" or "advertising" or such. That was completely unintentional. If this is expected somehow, we should probably discuss that too more seriously and discuss its merits, and if it can be support, should be supported, or if there's a different solution entirely? For example. there is the search engine which _could_ show a global feed/timeline view, albeit the domain could be something different.
One thing to be clear about here is that it was never my intention for a pod's "front page" (Discover view when not logged in) to be any kind of "listing" or "advertising" or such. That was completely unintentional. If this is expected somehow, we should probably discuss that too more seriously and discuss its merits, and if it can be support, should be supported, or if there's a different solution entirely? For example. there is the search engine which _could_ show a global feed/timeline view, albeit the domain could be something different.
One thing to be clear about here is that it was never my intention for a pod's "front page" (Discover view when not logged in) to be any kind of "listing" or "advertising" or such. That was completely unintentional. If this is expected somehow, we should probably discuss that too more seriously and discuss its merits, and if it can be support, should be supported, or if there's a different solution entirely? For example. there is the search engine which _could_ show a global feed/timeline view, albeit the domain could be something different.
I'd like to hear some ideas that fix or improve the signal / noise ratio for all users and even benefits non-users (anonymous users just hitting a pod's index page, which is the discover view)
I'd like to hear some ideas that fix or improve the signal / noise ratio for all users and even benefits non-users (anonymous users just hitting a pod's index page, which is the discover view)
I'd like to hear some ideas that fix or improve the signal / noise ratio for all users and even benefits non-users (anonymous users just hitting a pod's index page, which is the discover view)
There's also a pod-level setting (admins) that control what the "Discover" (or front page if you're not logged in) display:
This is either:
- Local posts only (local to the pod)
- All posts in the pod's cache
There's also a pod-level setting (admins) that control what the "Discover" (or front page if you're not logged in) display:
This is either:
- Local posts only (local to the pod)
- All posts in the pod's cache
There's also a pod-level setting (admins) that control what the "Discover" (or front page if you're not logged in) display:
This is either:
- Local posts only (local to the pod)
- All posts in the pod's cache
One of the problems I have with changing the way the "Discover" view works whilst at the same time keeping it "clean" (_depending on who you talk to_) is the behaviour between "Timeline" (what you follow explicitly) and "Discover" (a view into the pod's cache). See attached, where I by default prefer a "collapsed" view (_hiding replies_). The default behaviour for Discover (no controls) is "everything".
The reason I bring this up is that part of my "workflow" has become to occasionally use the "Discover" view to see if I've missed any "in-between" replies that often happen, find new interesting folks to follow and/or interact with, etc.
Changing this to anything but the current behaviour would break this flow for me 😢
One of the problems I have with changing the way the "Discover" view works whilst at the same time keeping it "clean" (_depending on who you talk to_) is the behaviour between "Timeline" (what you follow explicitly) and "Discover" (a view into the pod's cache). See attached, where I by default prefer a "collapsed" view (_hiding replies_). The default behaviour for Discover (no controls) is "everything".
The reason I bring this up is that part of my "workflow" has become to occasionally use the "Discover" view to see if I've missed any "in-between" replies that often happen, find new interesting folks to follow and/or interact with, etc.
Changing this to anything but the current behaviour would break this flow for me 😢
One of the problems I have with changing the way the "Discover" view works whilst at the same time keeping it "clean" (_depending on who you talk to_) is the behaviour between "Timeline" (what you follow explicitly) and "Discover" (a view into the pod's cache). See attached, where I by default prefer a "collapsed" view (_hiding replies_). The default behaviour for Discover (no controls) is "everything".
The reason I bring this up is that part of my "workflow" has become to occasionally use the "Discover" view to see if I've missed any "in-between" replies that often happen, find new interesting folks to follow and/or interact with, etc.
Changing this to anything but the current behaviour would break this flow for me 😢
One of the problems I have with changing the way the "Discover" view works whilst at the same time keeping it "clean" (_depending on who you talk to_) is the behaviour between "Timeline" (what you follow explicitly) and "Discover" (a view into the pod's cache). See attached, where I by default prefer a "collapsed" view (_hiding replies_). The default behaviour for Discover (no controls) is "everything".
The reason I bring this up is that part of my "workflow" has become to occasionally use the "Discover" view to see if I've missed any "in-between" replies that often happen, find new interesting folks to follow and/or interact with, etc.
Changing this to anything but the current behaviour would break this flow for me 😢
@bender Nah feeling pretty rubbish today actually 😢
@bender Nah feeling pretty rubbish today actually 😢
@bender Nah feeling pretty rubbish today actually 😢
@marcorocco What are you updating and changing out in your bathroom? 🤔 We probably need to update our bathroom too, the spa pipes are getting a bit uggh 😅
@marcorocco What are you updating and changing out in your bathroom? 🤔 We probably need to update our bathroom too, the spa pipes are getting a bit uggh 😅
@marcorocco What are you updating and changing out in your bathroom? 🤔 We probably need to update our bathroom too, the spa pipes are getting a bit uggh 😅
@aelaraji I just woke up fianally 🤣 It's 12:45pm here (midday)
@aelaraji I just woke up fianally 🤣 It's 12:45pm here (midday)
@aelaraji I just woke up fianally 🤣 It's 12:45pm here (midday)
@aelaraji here as in, here? It’s a quarter to 22:00 *here*, and after a rather tiresome day I am trying to rest, while alternating with folding freshly washed and dried clothes. Quiet indeed! 😅
It's kinda quiet in here today!
It's kinda quiet in here today!
🧮 USERS:1 FEEDS:2 TWTS:951 ARCHIVED:71520 CACHE:2391 FOLLOWERS:15 FOLLOWING:14
[47°09′17″S, 126°43′33″W] Transponder still failing -- switching to analog communication
[47°09′18″S, 126°43′44″W] Resetting transponder
Fuck, I'm missing all of my chances
renovating the bathroom on the upper floor
To expand on this, Lyse is the only person I know to send in code contributions with a full test suite. That’s awesome.
To expand on this, Lyse is the only person I know to send in code contributions with a full test suit. That’s awesome.
@prologic isn’t it evident? It surprises me you need to ask! 😂
@dfaria you are not who you say you are, you are who you show to be. You demonstrated a certain lack of levelled engagement, and sound reasoning; you were borderline hysterical. All qualities everyone should have, even more so someone who has chosen the teaching path.
This is not a train terminal. No need to give so many warnings about leaving, so many “bye-byes”. If that’s your intention, just leave.
[47°09′19″S, 126°43′53″W] Transponder malfunction
I need gopher browser for Android? Where i can download it?
Pinellas County - Long run 3':1': 10.19 miles, 00:09:43 average pace, 01:39:03 duration
practicing three minutes running and one minute walking intervals. not only for the knee but also for the PTC (~46.6 miles) coming in about 17 weeks. the knee actually hurt a little the first five miles, but afterwards nothing. not sure if i finally found my stride but it felt great once the dull pain was gone.
#running #injury~
Pinellas County - Long Run: 10.19 miles, 00:09:43 average pace, 01:39:03 duration
practicing 3 minutes running and one minute walking. not only for the knee but also for the PTC (~46.6 miles) coming in about 17 weeks. the knee actually hurt a little the first 5 miles but afterwards nothing. not sure if i finally found my stride but it felt great once the dull pain was gone.
#running~
Pinellas County - Long Run: 10.19 miles, 00:09:43 average pace, 01:39:03 duration
practicing 3 minutes running and one minute walking. not only for the knee but also for the PTC (~46.6 miles) coming in about 17 weeks. the knee actually hurt a little the first 5 miles but afterwards nothing. not sure if i finally found my stride but it felt great once the dull pain was gone.
#running~
Pinellas County - Long Run: 10.19 miles, 00:09:43 average pace, 01:39:03 duration
practicing 3 minutes running and one minute walking. not only for the knee but also for the PTC (~46.6 miles) coming in about 17 weeks. the knee actually hurt a little the first 5 miles but afterwards nothing. not sure if i finally found my stride but it felt great once the dull pain was gone.
#running~
@dfaria Appreciate this 👌 Right now the algorithm is quite dumb -- and I'd also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:
- one post per day per domain
- or latest post per domain
etc/./
@dfaria Appreciate this 👌 Right now the algorithm is quite dumb -- and I'd also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:
- one post per day per domain
- or latest post per domain
etc/./
@dfaria Appreciate this 👌 Right now the algorithm is quite dumb -- and I'd also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:
- one post per day per domain
- or latest post per domain
etc/./
@sorenpeter Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things "right" is actually quite hard 😅
@sorenpeter Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things "right" is actually quite hard 😅
@sorenpeter Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things "right" is actually quite hard 😅
@lyse How mixh emphasis do you place on test software?
@lyse How much emphasis do you place on test coverage?
@lyse How much emphasis do you place on test coverage?
@lyse How much emphasis do you place on test coverage?
To be fair cleaning up "noise" is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there's just no way to interact with them!
To be fair cleaning up "noise" is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there's just no way to interact with them!
To be fair cleaning up "noise" is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there's just no way to interact with them!
@dfaria That's fair. Also removed the block on your domain btw.
@dfaria That's fair. Also removed the block on your domain btw.
@dfaria That's fair. Also removed the block on your domain btw.
Executing all tests of the online registrations I'm building for the scouts takes now 70 seconds. Initializing a new SQLite database in RAM and creating all the tables for each test case sums up and takes its time. During development cycles I more often resort to the -run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.
At least the service layer line coverage is a whopping 99.5%, branch coverage is 93.3% (the latter could still be bumped slightly). However, only 17.6% lines of the web layer are covered (I definitely should increase this by a lot). This still good test base, if I say so myself, came in extremely handy a lot of times when refactoring stuff. Esp. the service layer changed, web not so much. It slows development down quite a lot, that's for sure. I reckon it's easily five to ten times more effort to come up with useful tests than writing productive code, probably even more. I'm bad at guessing. But the confidence of not breaking stuff is sooo much more valuable. The tests certainly paid off in the past, zero doubt about that.
It takes a lot of discipline to first write all the tests in the service layer before doing the web stuff and finally see it in action and play around. It's funny that I always have to force myself to do so, but in the end, I'm always happy to have done it exactly like that. It once again worked out very smoothely that way. But something inside me wants to fast forward. I wonder if that irrational part eventually fades away.
Having a code coverage report does make a night a day difference. It actually turns writing tests into a fun game for me. The older I get, the more I do enjoy writing tests. Rest assured, producing productive code is still cooler. :-)
I'm also sooo happy about vim-go. I can't believe how much that sped up and boosted my development process.
Whoops, 57 minutes later, this message turned out much more elaborated that I initially envisioned. Oh well. ;-)
Depuis hier j'auto-héberge ce site sur un Raspberry. Il peut donc devenir inaccessible, notamment la nuit. Mais je pense que ça vous fait une belle jambe ;-D