# 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 11
# self = https://watcher.sour.is/conv/2rzhvuq
ocdtrekkie
twtxt.net
View Thread
@prologic To be fair, that both predates Sandstorm (circa 2014), and considering you've tried it recently and still spun up your own corporate infrastructure, demonstrates it's not ready to meet your needs even today.

I would probably love your top bullet points on what Sandstorm would've needed to have or do to meet your business infra needs.
prologic
twtxt.net
View Thread
@ocdtrekkie I don't need any bullet points really. It's easy. Aside from all the things we already agree upon, like the backend being written in C++, the UI/UX is a bit well umm you know πŸ˜… (even my wife had something to say about it πŸ˜‚) -- Bottom line though?

> Sandstorm's model is opposite of what I want/need.

An ideal version of Sandstorm would by one in which I can choose to operate an instance ine one of two models (multi-user or free-for-all or even single-user?). But the way Sandstorm is modelled today, its basically a C++ Web App with a poor UI that lets anyone basically run whatever they want and install whatever they want with (I admit) strong security based on Capability.

Problem is I _really_ don't need this kind of security, or at least if I do, I want to chose whether I need this level of security or not.

People (I mean ordinary) folk already find security inconvenience and hard enough as it is. They just don't get Capability based Security, neither did I at first πŸ™„
prologic
twtxt.net
View Thread
@ocdtrekkie I don't need any bullet points really. It's easy. Aside from all the things we already agree upon, like the backend being written in C++, the UI/UX is a bit well umm you know πŸ˜… (even my wife had something to say about it πŸ˜‚) -- Bottom line though?

> Sandstorm's model is opposite of what I want/need.

An ideal version of Sandstorm would by one in which I can choose to operate an instance ine one of two models (multi-user or free-for-all or even single-user?). But the way Sandstorm is modelled today, its basically a C++ Web App with a poor UI that lets anyone basically run whatever they want and install whatever they want with (I admit) strong security based on Capability.

Problem is I _really_ don't need this kind of security, or at least if I do, I want to chose whether I need this level of security or not.

People (I mean ordinary) folk already find security inconvenience and hard enough as it is. They just don't get Capability based Security, neither did I at first πŸ™„
prologic
twtxt.net
View Thread
Also an an aside, I ended up packaging three things today and standing them all up in a day. Part of that is my vast experience with Docker Swarm and Docker, but I _doubt_ I'd even have finished if I tried to achieve the same goals with Sandstorm sadly. The packaging (despite all your efforts) is quite a bit obtuse with the use of Cap 'n Proto (sorry) -- But I really wouldn't have picked a format like Cap 'n Proto whose primary benefit is a "insanely fast data interchange format and capability-based RPC system" as a way to define packages (Uggh) πŸ˜…
prologic
twtxt.net
View Thread
Also an an aside, I ended up packaging three things today and standing them all up in a day. Part of that is my vast experience with Docker Swarm and Docker, but I _doubt_ I'd even have finished if I tried to achieve the same goals with Sandstorm sadly. The packaging (despite all your efforts) is quite a bit obtuse with the use of Cap 'n Proto (sorry) -- But I really wouldn't have picked a format like Cap 'n Proto whose primary benefit is a "insanely fast data interchange format and capability-based RPC system" as a way to define packages (Uggh) πŸ˜…
ocdtrekkie
twtxt.net
View Thread
@prologic I mean I wrote https://github.com/sandstorm-io/sandstorm-error-collector in an evening, but I'm pretty well-versed in working within vagrant-spk at this point, and I knew where to pull most examples of what I was building quickly. (Also with PHP I don't have to write my own web server...)
prologic
twtxt.net
View Thread
@ocdtrekkie Bahahaha

> Also with PHP I don’t have to write my own web server

That was a job at Go right? 🀣 To be fair, you don't actually write your own web server in Go, you just run one that's part of the standard library. There are also numerous elaborate "Web Frameworks' you _can_ use, all of which I really hate because I detest the use of "frameworks' almost as much as I detest the use of 3rd-party (random) Cloud/SaaS services or Database Systems 🀣
prologic
twtxt.net
View Thread
@ocdtrekkie Bahahaha

> Also with PHP I don’t have to write my own web server

That was a job at Go right? 🀣 To be fair, you don't actually write your own web server in Go, you just run one that's part of the standard library. There are also numerous elaborate "Web Frameworks' you _can_ use, all of which I really hate because I detest the use of "frameworks' almost as much as I detest the use of 3rd-party (random) Cloud/SaaS services or Database Systems 🀣
ocdtrekkie
twtxt.net
View Thread
@prologic Absolutely a jab at Golang. Though I still want to try
building a web app with it.
prologic
twtxt.net
View Thread
@ocdtrekkie Haha 🀣 I knew it! And good o πŸ‘Œ I still owe you too! πŸ€¦β€β™‚οΈ
prologic
twtxt.net
View Thread
@ocdtrekkie Haha 🀣 I knew it! And good o πŸ‘Œ I still owe you too! πŸ€¦β€β™‚οΈ