# 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 24
# self = https://watcher.sour.is/conv/7nq3eda
Signal Status
> Signal is experiencing technical difficulties. We are working hard to restore service as quickly as possible.
One _thing_ I'd like to have one day (_and it would be nice if it were integrated into twtxt.net and other pods with a familiar and pleasant user experience on Desktop, Web and Mobile_) is an e2e encrypted messaging that is self-hosted and federated that doesn't suck operationally (_so many complicated solutions that exist that are hard to setup even for a Senior DevOps/SRE_)_
Signal Status
> Signal is experiencing technical difficulties. We are working hard to restore service as quickly as possible.
One _thing_ I'd like to have one day (_and it would be nice if it were integrated into twtxt.net and other pods with a familiar and pleasant user experience on Desktop, Web and Mobile_) is an e2e encrypted messaging that is self-hosted and federated that doesn't suck operationally (_so many complicated solutions that exist that are hard to setup even for a Senior DevOps/SRE_)_
The _problem_ of course is that @dbohdan _was_ and is right about something he said to him about building Private Messaging into this platform, it would overtake the project, its complex and getting security/privacy right is hard™.\n\nThe advice given was to find something that we could integrate with so we don't have to do all the _hard word_ -- Problem is I've not really found anything quite suitable...
The _problem_ of course is that @dbohdan _was_ and is right about something he said to him about building Private Messaging into this platform, it would overtake the project, its complex and getting security/privacy right is hard™.\n\nThe advice given was to find something that we could integrate with so we don't have to do all the _hard word_ -- Problem is I've not really found anything quite suitable...
The _problem_ of course is that @dbohdan _was_ and is right about something he said to him about building Private Messaging into this platform, it would overtake the project, its complex and getting security/privacy right is hard™.
The advice given was to find something that we could integrate with so we don't have to do all the _hard word_ -- Problem is I've not really found anything quite suitable...
The _problem_ of course is that @dbohdan _was_ and is right about something he said to him about building Private Messaging into this platform, it would overtake the project, its complex and getting security/privacy right is hard™.
The advice given was to find something that we could integrate with so we don't have to do all the _hard word_ -- Problem is I've not really found anything quite suitable...
It's hard to describe in words, but it basically quite simple:\n\n> If you follow a project's README or software's Documentation and cannot get it up and running within a few mins (_with a little tiny perseverance, because we're all human and make small mistakes_), then the project or software is basically quite garbage at that point "operationally". It _might_ be a fantastic piece of software or project, but if its that hard to "operationalize" you may as well forget it.\n\nThat's how I feel about a lot of software and project. A lot you come across just suck. cc @markwylde
It's hard to describe in words, but it basically quite simple:
> If you follow a project's README or software's Documentation and cannot get it up and running within a few mins (_with a little tiny perseverance, because we're all human and make small mistakes_), then the project or software is basically quite garbage at that point "operationally". It _might_ be a fantastic piece of software or project, but if its that hard to "operationalize" you may as well forget it.
That's how I feel about a lot of software and project. A lot you come across just suck. cc @markwylde
It's hard to describe in words, but it basically quite simple:
> If you follow a project's README or software's Documentation and cannot get it up and running within a few mins (_with a little tiny perseverance, because we're all human and make small mistakes_), then the project or software is basically quite garbage at that point "operationally". It _might_ be a fantastic piece of software or project, but if its that hard to "operationalize" you may as well forget it.
That's how I feel about a lot of software and project. A lot you come across just suck. cc @markwylde
It's hard to describe in words, but it basically quite simple:\n\n> If you follow a project's README or software's Documentation and cannot get it up and running within a few mins (_with a little tiny perseverance, because we're all human and make small mistakes_), then the project or software is basically quite garbage at that point "operationally". It _might_ be a fantastic piece of software or project, but if its that hard to "operationalize" you may as well forget it.\n\nThat's how I feel about a lot of software and project. A lot you come across just suck. cc @markwylde
@prologic sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah."
I am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?
@prologic sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah."\n\nI am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?
@prologic sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah."
I am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?
@prologic sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah."
I am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?
@prologic sometimes I think it would be nice to have a XMPP instance. then I remember it's all XML and I think "nah."\n\nI am constantly in awe that IRC remains the only realtime chat that isn't unnecessarily complex. name another that can run chatops bot with just nc and sh?
@xuu I can’t! \nbut in so saying I brought this up with @asi Who helped me come up with the final proof of concept implementation of the private messages you see here today. But I do wonder what if instead we actually used the IRC protocol and baked in a built-in IRC server between pods?
@xuu I can’t!
but in so saying I brought this up with @asi Who helped me come up with the final proof of concept implementation of the private messages you see here today. But I do wonder what if instead we actually used the IRC protocol and baked in a built-in IRC server between pods?
@xuu I can’t! \nbut in so saying I brought this up with @asi Who helped me come up with the final proof of concept implementation of the private messages you see here today. But I do wonder what if instead we actually used the IRC protocol and baked in a built-in IRC server between pods?
@xuu I can’t!
but in so saying I brought this up with @asi Who helped me come up with the final proof of concept implementation of the private messages you see here today. But I do wonder what if instead we actually used the IRC protocol and baked in a built-in IRC server between pods?
@prologic that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM. \n\nbut having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.
but having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.
but having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.
but having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM. \n\nbut having a federation of IRC servers would be interesting for realtime twt propagation.