# 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 61074
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=44891
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=44991
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=44791
@abucci Hmm this is true, sadly. Are you able to file a feature request for this? It's just a missing feature 🙏
@abucci Hmm this is true, sadly. Are you able to file a feature request for this? It's just a missing feature 🙏
@abucci Hmm this is true, sadly. Are you able to file a feature request for this? It's just a missing feature 🙏
@abucci Hmm this is true, sadly. Are you able to file a feature request for this? It's just a missing feature 🙏
Pinch and a punch for the first of the month 👊
Pinch and a punch for the first of te month! 👊
Pinch and a punch for the first of te month! 👊
Pinch and a punch for the first of te month! 👊
Pinch and a punch for the first of te month! 👊
Pinch and a punch for the first of the month 👊
Pinch and a punch for the first of the month 👊
@akoizumi Just stick to Yarn.social 😆 It's better for your health 😅
@akoizumi Just stick to Yarn.social 😆 It's better for your health 😅
@akoizumi Just stick to Yarn.social 😆 It's better for your health 😅
@akoizumi Just stick to Yarn.social 😆 It's better for your health 😅
@bender I think I might actually follow all three of his accounts, so I hear you're actually correct in this case. 😆
also need to talk to you about the other case that you discovered that I promised I will try and fix, which I realized I wasn't completely 100% sure what was going on 🤦♂️
@bender I think I might actually follow all three of his accounts, so I hear you're actually correct in this case. 😆
also need to talk to you about the other case that you discovered that I promised I will try and fix, which I realized I wasn't completely 100% sure what was going on 🤦♂️
@bender I think I might actually follow all three of his accounts, so I hear you're actually correct in this case. 😆
also need to talk to you about the other case that you discovered that I promised I will try and fix, which I realized I wasn't completely 100% sure what was going on 🤦♂️
@bender I think I might actually follow all three of his accounts, so I hear you're actually correct in this case. 😆
also need to talk to you about the other case that you discovered that I promised I will try and fix, which I realized I wasn't completely 100% sure what was going on 🤦♂️
remember my goals for this year? To get the mobile app finally released to production with all bugs and improvements addressed? 🤔
remember my goals for this year? To get the mobile app finally released to production with all bugs and improvements addressed? 🤔
remember my goals for this year? To get the mobile app finally released to production with all bugs and improvements addressed? 🤔
remember my goals for this year? To get the mobile app finally released to production with all bugs and improvements addressed? 🤔
@bender Because the mobile app has a different reply thank you that needs to be fixed. It's a non-problem and documented as a bug. 
@bender Because the mobile app has a different reply thank you that needs to be fixed. It's a non-problem and documented as a bug.
@bender Because the mobile app has a different reply thank you that needs to be fixed. It's a non-problem and documented as a bug.
@bender Because the mobile app has a different reply thank you that needs to be fixed. It's a non-problem and documented as a bug.
@screem Don't know of any myself. e2e IRC encryption is not that common in my experience 😢
@screem Don't know of any myself. e2e IRC encryption is not that common in my experience 😢
@screem Don't know of any myself. e2e IRC encryption is not that common in my experience 😢
@screem Don't know of any myself. e2e IRC encryption is not that common in my experience 😢
Anyway, even if I did, which I'm sure I did, it wasn't intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn't really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it _could_. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦♂️
As a big proponent of self-hosting, I find this an anti-pattern.*
Anyway, even if I did, which I'm sure I did, it wasn't intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn't really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it _could_. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦♂️
As a big proponent of self-hosting, I find this an anti-pattern.*
Anyway, even if I did, which I'm sure I did, it wasn't intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn't really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it _could_. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦♂️
As a big proponent of self-hosting, I find this an anti-pattern.*
Anyway, even if I did, which I'm sure I did, it wasn't intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn't really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it _could_. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦♂️
As a big proponent of self-hosting, I find this an anti-pattern.*
@abucci Where did I hate on SQL databases? 🤔
@abucci Where did I hate on SQL databases? 🤔
@abucci Where did I hate on SQL databases? 🤔
@abucci Where did I hate on SQL databases? 🤔
@abucci Maybe maybe not. Depends on what you're doing I guess. For small things I find simple things are better anyway. KV, flat files, a log, etc.
@abucci Maybe maybe not. Depends on what you're doing I guess. For small things I find simple things are better anyway. KV, flat files, a log, etc.
@abucci Maybe maybe not. Depends on what you're doing I guess. For small things I find simple things are better anyway. KV, flat files, a log, etc.
@abucci Maybe maybe not. Depends on what you're doing I guess. For small things I find simple things are better anyway. KV, flat files, a log, etc.
a large part of this comes from experience, dealing with databases, and SQL many times in the past, and then eventually coming to the realizing that everything is basically key value, stores, bloom filters, trees*, tries and various types of indexes and caches.*
a large part of this comes from experience, dealing with databases, and SQL many times in the past, and then eventually coming to the realizing that everything is basically key value, stores, bloom filters, trees*, tries and various types of indexes and caches.*
a large part of this comes from experience, dealing with databases, and SQL many times in the past, and then eventually coming to the realizing that everything is basically key value, stores, bloom filters, trees*, tries and various types of indexes and caches.*
a large part of this comes from experience, dealing with databases, and SQL many times in the past, and then eventually coming to the realizing that everything is basically key value, stores, bloom filters, trees*, tries and various types of indexes and caches.*
For me personally I find it far easier to reason about the data I'm dealing with, what forms it needs to take and what to do with it.
For me personally I find it far easier to reason about the data I'm dealing with, what forms it needs to take and what to do with it.
For me personally I find it far easier to reason about the data I'm dealing with, what forms it needs to take and what to do with it.
For me personally I find it far easier to reason about the data I'm dealing with, what forms it needs to take and what to do with it.
@marado TIL -- Knew about talk though 😆
@marado TIL -- Knew about talk though 😆
@marado TIL -- Knew about talk though 😆
@marado TIL -- Knew about talk though 😆
@johano sorry we haven't made a new release in a while. Hopefully soon. 🤞
@johano sorry we haven't made a new release in a while. Hopefully soon. 🤞
@johano sorry we haven't made a new release in a while. Hopefully soon. 🤞
@johano sorry we haven't made a new release in a while. Hopefully soon. 🤞
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
I really don't understand why I'm getting such a hard time from y'all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔
I really don't understand why I'm getting such a hard time from y'all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔
I really don't understand why I'm getting such a hard time from y'all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔
I really don't understand why I'm getting such a hard time from y'all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔
@screem Hey hey! 👋 INce to see you again and good to know you're doing okay 👌 -- We should maybe catch-up for a beer or something since we're now geographically close to one another 🙏
@screem Hey hey! 👋 INce to see you again and good to know you're doing okay 👌 -- We should maybe catch-up for a beer or something since we're now geographically close to one another 🙏
@screem Hey hey! 👋 INce to see you again and good to know you're doing okay 👌 -- We should maybe catch-up for a beer or something since we're now geographically close to one another 🙏
@screem Hey hey! 👋 INce to see you again and good to know you're doing okay 👌 -- We should maybe catch-up for a beer or something since we're now geographically close to one another 🙏
@abucci Without Javascript you say? Hmmm? 🤔 How? (unless we're tlaking about the same thing in different ways...)
@abucci Without Javascript you say? Hmmm? 🤔 How? (unless we're tlaking about the same thing in different ways...)
@abucci Aithout JacaSceipt you say? Hmmm? 🤔
@abucci Without Javascript you say? Hmmm? 🤔 How? (unless we're tlaking about the same thing in different ways...)
@abucci Without Javascript you say? Hmmm? 🤔 How? (unless we're tlaking about the same thing in different ways...)
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive 😆
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive 😆
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive 😆
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive 😆
Not gonna happen 😆 But thanks for trying 🤗
Not gonna happen 😆 But thanks for trying 🤗
Not gonna happen 😆 But thanks for trying 🤗
Not gonna happen 😆 But thanks for trying 🤗