# 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 37
# self = https://watcher.sour.is/conv/cn3kxka
@prologic why? Wouldn't that go against the idea of decentralisation?
@prologic why? Wouldn't that go against the idea of decentralisation?
How so? I mean people that have swung by to "test" and "check" things out, never to be seen again. There are hundreds of accounts on this pod that have never posted a thing. If course OTOH I don't actually know if they ever login and are just idle lurkers/readers...
How so? I mean people that have swung by to "test" and "check" things out, never to be seen again. There are hundreds of accounts on this pod that have never posted a thing. If course OTOH I don't actually know if they ever login and are just idle lurkers/readers...
How so? I mean people that have swung by to "test" and "check" things out, never to be seen again. There are hundreds of accounts on this pod that have never posted a thing. If course OTOH I don't actually know if they ever login and are just idle lurkers/readers...
@prologic It snot a problem now per se, but they do consume key space in memory as the database used for storing things like accounts and who owns what feed and sessions stores its key space in memory.
@prologic It snot a problem now per se, but they do consume key space in memory as the database used for storing things like accounts and who owns what feed and sessions stores its key space in memory.
@prologic It snot a problem now per se, but they do consume key space in memory as the database used for storing things like accounts and who owns what feed and sessions stores its key space in memory.
@prologic I thought the whole point of decentralisation was that there wasn't one single entity controlling things like accounts.
@prologic I thought the whole point of decentralisation was that there wasn't one single entity controlling things like accounts.
@prologic base64 compress inactive twtxt files)
@prologic base64 compress inactive twtxt files)
@prologic that bracket should have been a question mark
@prologic that bracket should have been a question mark
@prologic also, some people might make accounts with the intention of using twtxt as a way of communication but then go on hiatus for different reasons. They might very well come back. I know I did. I made my account after seeing this repo on github and went on hiatus due to exams and school. I know I'd be confused if I came back and found my account deleted.
@prologic also, some people might make accounts with the intention of using twtxt as a way of communication but then go on hiatus for different reasons. They might very well come back. I know I did. I made my account after seeing this repo on github and went on hiatus due to exams and school. I know I'd be confused if I came back and found my account deleted.
You _have_ to identify yourself as an owner of a feed somehow though? I mean sure I get what you're saying, each Pod _has_ accounts. The decentralised parts are the Feeds and Conversations, not so much the "Users". You have to belong to a Pod somewhere, or run your own. At _some_ point I'd like to be able to carry your "identity" around through a network of pods which I _think_ is there things like IndieAuth can help (_PR not merged yet..._).
You _have_ to identify yourself as an owner of a feed somehow though? I mean sure I get what you're saying, each Pod _has_ accounts. The decentralised parts are the Feeds and Conversations, not so much the "Users". You have to belong to a Pod somewhere, or run your own. At _some_ point I'd like to be able to carry your "identity" around through a network of pods which I _think_ is there things like IndieAuth can help (_PR not merged yet..._).
You _have_ to identify yourself as an owner of a feed somehow though? I mean sure I get what you're saying, each Pod _has_ accounts. The decentralised parts are the Feeds and Conversations, not so much the "Users". You have to belong to a Pod somewhere, or run your own. At _some_ point I'd like to be able to carry your "identity" around through a network of pods which I _think_ is there things like IndieAuth can help (_PR not merged yet..._).
Yeap all good points. LIke I said, it doesn't _really_ hurt, it just consumes key space... But that's something I _could_ solve in Bitcask itself as a "technical" level where I evict inactive keys out of the in-memory keyspace and archive them to disk instead only keeping "active" keys in memory for fast lookups.
Yeap all good points. LIke I said, it doesn't _really_ hurt, it just consumes key space... But that's something I _could_ solve in Bitcask itself as a "technical" level where I evict inactive keys out of the in-memory keyspace and archive them to disk instead only keeping "active" keys in memory for fast lookups.
Yeap all good points. LIke I said, it doesn't _really_ hurt, it just consumes key space... But that's something I _could_ solve in Bitcask itself as a "technical" level where I evict inactive keys out of the in-memory keyspace and archive them to disk instead only keeping "active" keys in memory for fast lookups.
This is something I want to do anyway for Bitcask so that it can scale almost indefinitely unless your entire keyspace is hot and active all the time! 🤣
This is something I want to do anyway for Bitcask so that it can scale almost indefinitely unless your entire keyspace is hot and active all the time! 🤣
This is something I want to do anyway for Bitcask so that it can scale almost indefinitely unless your entire keyspace is hot and active all the time! 🤣
@prologic i have to say i'm with @lyxal on this one. I registered here to claim my username, but in doing so i had no idea this feed would take precedence over my self hosted one. And since i'm self hosting (and have been subscribing to "slow" usage of the internet more and more) i don't feel compelled to post all the time, which may or may not be considered a hiatus
@prologic i have to say i'm with @lyxal on this one. I registered here to claim my username, but in doing so i had no idea this feed would take precedence over my self hosted one. And since i'm self hosting (and have been subscribing to "slow" usage of the internet more and more) i don't feel compelled to post all the time, which may or may not be considered a hiatus
@deadguy Agree with @lyxal in regards to having an account but being on "hiatus" or just keeping it as a "claim" / "identity"?
@deadguy Agree with @lyxal in regards to having an account but being on "hiatus" or just keeping it as a "claim" / "identity"?
@deadguy Agree with @lyxal in regards to having an account but being on "hiatus" or just keeping it as a "claim" / "identity"?
@prologic @lyxal admittedly, i claimed it because i have the intention of using it, but i thought maybe my self hosted file would get replicated here. Not that having my "main" file on someone's pod is a bad idea or anything
@prologic @lyxal admittedly, i claimed it because i have the intention of using it, but i thought maybe my self hosted file would get replicated here. Not that having my "main" file on someone's pod is a bad idea or anything
@deadguy Yeah that's "fair enough". I _think_ you've seen my say this in other Twt(s), I _fully_ intend to provide more features to the API and command-line client twt so what you probably _thought_ was possible will* become possible. I'd like it myself anyway (_just becuase_), on the upside, hopefully when we get around to it it'll mean you get the best of both worlds, self-hsoted twtxt.txt file, synced to your "Pod" account, with API and Mobile App access 👌*
@deadguy Yeah that's "fair enough". I _think_ you've seen my say this in other Twt(s), I _fully_ intend to provide more features to the API and command-line client twt so what you probably _thought_ was possible will* become possible. I'd like it myself anyway (_just becuase_), on the upside, hopefully when we get around to it it'll mean you get the best of both worlds, self-hsoted twtxt.txt file, synced to your "Pod" account, with API and Mobile App access 👌*
@deadguy Yeah that's "fair enough". I _think_ you've seen my say this in other Twt(s), I _fully_ intend to provide more features to the API and command-line client twt so what you probably _thought_ was possible will* become possible. I'd like it myself anyway (_just becuase_), on the upside, hopefully when we get around to it it'll mean you get the best of both worlds, self-hsoted twtxt.txt file, synced to your "Pod" account, with API and Mobile App access 👌*
@prologic that would be awesome, looking forward to it
@prologic that would be awesome, looking forward to it