# 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 196277
# self = https://watcher.sour.is?offset=172499
# next = https://watcher.sour.is?offset=172599
# prev = https://watcher.sour.is?offset=172399
> > (#sbmynna) @xuu wrote: > > > "@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected." > > I figure I could also answer *every* single twtxt like this, so that if the original gets edited, or deleted, at least I don't sound foolish without knowing exactly what I replied to. š¤
It Sounds like a good idea! should that be limited to just direct replays or can it be extended to replays to other replays, that way and With just the right amount of chain-replays, we'll be RRrrrrrevolutionizing the way people Mailing Lists like, in no time! xD
P.S: Just a reminder! I've already told you not to mind my twts for the next couple of hours, right!
> > (#sbmynna) @xuu wrote: > > > "@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected." > > I figure I could also answer *every* single twtxt like this, so that if the original gets edited, or deleted, at least I don't sound foolish without knowing exactly what I replied to. š¤
It Sounds like a good idea! should that be limited to just direct replays or can it be extended to replays to other replays, that way and With just the right amount of chain-replays, we'll be RRrrrrrevolutionizing the way people Mailing Lists like, in no time! xD
P.S: Just a reminder! I've already told you not to mind my twts for the next couple of hours, right!
> > (#sbmynna) @xuu wrote: > > > "@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected." > > I figure I could also answer *every* single twtxt like this, so that if the original gets edited, or deleted, at least I don't sound foolish without knowing exactly what I replied to. š¤
It Sounds like a good idea! should that be limited to just direct replays or can it be extended to replays to other replays, that way and With just the right amount of chain-replays, we'll be RRrrrrrevolutionizing the way people Mailing Lists like, in no time! xD
P.S: Just a reminder! I've already told you not to mind my twts for the next couple of hours, right!
> "@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected."
I figure I could also answer *every* single twtxt like this, so that if the original gets edited, or deleted, at least I don't sound foolish without knowing exactly what I replied to. š¤
@bender Well Matt should definitely get better Lawyers/PR people who could slap em' on the wrest and tell "NO!" before he does something childish and effs things up. As for WPE, I believe a billion dollar company should be able to afford investing in their own infrastructure, hosting their resources, deploying their own CDNs and what not instead of leaching on Wordpress ('s infrastructure) for free (as in free coffee) + The Stripe thing they did is so disgusting _given the circumstances_, I don't even want to talk about it.
Things could/should've been handled better, now it's just another sh...rimp show.
@bender Well Matt should definitely get better Lawyers/PR people who could slap em' on the wrest and tell "NO!" before he does something childish and effs things up. As for WPE, I believe a billion dollar company should be able to afford investing in their own infrastructure, hosting their resources, deploying their own CDNs and what not instead of leaching on Wordpress ('s infrastructure) for free (as in free coffee) + The Stripe thing they did is so disgusting _given the circumstances_, I don't even want to talk about it.
Things could/should've been handled better, now it's just another sh...rimp show.
@bender Well Matt should definitely get better Lawyers/PR people who could slap em' on the wrest and tell "NO!" before he does something childish and effs things up. As for WPE, I believe a billion dollar company should be able to afford investing in their own infrastructure, hosting their resources, deploying their own CDNs and what not instead of leaching on Wordpress ('s infrastructure) for free (as in free coffee) + The Stripe thing they did is so disgusting _given the circumstances_, I don't even want to talk about it.
Things could/should've been handled better, now it's just another sh...rimp show.
@prologic How is nick@domain any better than a feed URL? Changing the nick now also breaks threading. That's even worse than the current approach. Also, there might be multiple feeds with same nicks on one domain, e.g. on free hosters.
Phew! I now finally called it a day as well. Our customer wanted me to emergency-start implementing some changes. Got an initial version with unit tests, but the final testing must wait until Monday.
Finally weekend. Time to relax a bit. And today I finally have some time for my computer in my free time. Wish you all a great weekend! Take care of your self and those around you :)
> More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.
> More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.
Like really tbh, it's just a matter of abstracting out the "fetching" part of your client. There are _zero_ issues with fetching Gopher/Gemini hosted feeds. They just lack any mechanisms for Discovery and Caching.
Like really tbh, it's just a matter of abstracting out the "fetching" part of your client. There are _zero_ issues with fetching Gopher/Gemini hosted feeds. They just lack any mechanisms for Discovery and Caching.
@movq I don't think I intend to either tbh for yarnd. If there was any poorly worded "things", it was just merely pointing out lacking capabilities for caching and discovery.
@movq I don't think I intend to either tbh for yarnd. If there was any poorly worded "things", it was just merely pointing out lacking capabilities for caching and discovery.
#catsoftwtxt
/https://baldo.cat/media/photos/IMG_2148.jpeg) #catsoftwtxt