# 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 75
# self = https://watcher.sour.is/conv/cbruy4q
Many many years ago, I _used_ to run a free shell service (_Linux of course_). What if I started offering this again? π€
Many many years ago, I _used_ to run a free shell service (_Linux of course_). What if I started offering this again? π€
@adi I _believe_ it used to ba Debian back then.
If I were to do it again, I would run a beefy-ish uLinux VM as the core of this "free" shell service. It would be very niche and if you want additional software on the system, it has to be capable of being built without the use of GCC/GLIBC π€£
@adi I _believe_ it used to ba Debian back then.\n\nIf I were to do it again, I would run a beefy-ish uLinux VM as the core of this "free" shell service. It would be very niche and if you want additional software on the system, it has to be capable of being built without the use of GCC/GLIBC π€£
@adi I _believe_ it used to ba Debian back then.
If I were to do it again, I would run a beefy-ish uLinux VM as the core of this "free" shell service. It would be very niche and if you want additional software on the system, it has to be capable of being built without the use of GCC/GLIBC π€£
@adi I _believe_ it used to ba Debian back then.\n\nIf I were to do it again, I would run a beefy-ish uLinux VM as the core of this "free" shell service. It would be very niche and if you want additional software on the system, it has to be capable of being built without the use of GCC/GLIBC π€£
I have no _favourite_ GNU Distro! π€£ The only distro I like that I didn't build/design/implement myself is CRUX π
I have no _favourite_ GNU Distro! π€£ The only distro I like that I didn't build/design/implement myself is CRUX π
I have no _favourite_ GNU Distro! π€£ The only distro I like that I didn't build/design/implement myself is CRUX π
IHMO All Deb(ians) and RHEL(s) suck π
IHMO All Deb(ians) and RHEL(s) suck π
IHMO All Deb(ians) and RHEL(s) suck π
@prologic There's a high change you'll fall in β€οΈ with it if you install it.
@prologic There's a high change you'll fall in β€οΈ with it if you install it.
@prologic There's a high change you'll fall in β€οΈ with it if you install it.
@adi Why would I fall in love with OpenBSD? π€
@adi Why would I fall in love with OpenBSD? π€
@adi Why would I fall in love with OpenBSD? π€
@prologic Simple,** no bloat, "less" but powerful features.
@prologic Simple,** no bloat, "less" but powerful features.
@prologic Simple,** no bloat, "less" but powerful features.
@adi That's precisely what ulinux is to me π€£ So what precisely does OpenBSD bring to the table? Besides a whole range of software I _probably_ won't really need π uLinux is pretty much Linux + Busybox userland + a few things I wrote and not much else. The init system, service management and package manager are all POSIX Shell scripts. It boots in like ~3s flat on modest hardware / virtual hardware and is really simple to use π~
@adi That's precisely what ulinux is to me π€£ So what precisely does OpenBSD bring to the table? Besides a whole range of software I _probably_ won't really need π uLinux is pretty much Linux + Busybox userland + a few things I wrote and not much else. The init system, service management and package manager are all POSIX Shell scripts. It boots in like ~3s flat on modest hardware / virtual hardware and is really simple to use π~
@adi That's precisely what ulinux is to me π€£ So what precisely does OpenBSD bring to the table? Besides a whole range of software I _probably_ won't really need π uLinux is pretty much Linux + Busybox userland + a few things I wrote and not much else. The init system, service management and package manager are all POSIX Shell scripts. It boots in like ~3s flat on modest hardware / virtual hardware and is really simple to use π~
@prologic "Consider using Alpine for a more feature rich system or any other βheavierβ / βfull featuredβ distro." π
I guess it's a more "feature rich" system compared to ulinux. I run X on OpenBSD and cwm as a simple, clean desktop. I also use their webserver https://man.openbsd.org/httpd.8.
@prologic "Consider using Alpine for a more feature rich system or any other βheavierβ / βfull featuredβ distro." π
I guess it's a more "feature rich" system compared to ulinux. I run X on OpenBSD and cwm as a simple, clean desktop. I also use their webserver https://man.openbsd.org/httpd.8.
@prologic "Consider using Alpine for a more feature rich system or any other βheavierβ / βfull featuredβ distro." π
I guess it's a more "feature rich" system compared to ulinux. I run X on OpenBSD and cwm as a simple, clean desktop. I also use their webserver https://man.openbsd.org/httpd.8.
@prologic That would be interesting. What type of permissions users would have on their shell accounts?
@prologic That would be interesting. What type of permissions users would have on their shell accounts?
@adi Utah uLinux is not designed to be an everyday OS or Desktop system β Althougj with some effort it _could be_
@adi Utah uLinux is not designed to be an everyday OS or Desktop system β Althougj with some effort it _could be_
@adi Utah uLinux is not designed to be an everyday OS or Desktop system β Althougj with some effort it _could be_
@antonio I would give full root access to your own persistent sandbox where you can do whatever you want under resource constraints controlled by the host
@antonio I would give full root access to your own persistent sandbox where you can do whatever you want under resource constraints controlled by the host
@antonio I would give full root access to your own persistent sandbox where you can do whatever you want under resource constraints controlled by the host
@prologic that would be super cool. This might be very similar to what the tilde community has own their hosted server (from what I understand). I am thinking this kind of service are great for ppl that don't know or don't have the resources to run their own linux/unix distro but want to learn how the system works. When you did that in the past, who were using it?
@prologic that would be super cool. This might be very similar to what the tilde community has own their hosted server (from what I understand). I am thinking this kind of service are great for ppl that don't know or don't have the resources to run their own linux/unix distro but want to learn how the system works. When you did that in the past, who were using it?
@antonio When I did this in the past it was either a Hetnzer dedicated server or a Codero one. Can't recall which, probably both at one time π Happy to do it again, but I'd want to invest some time to harden what I have in mind first... Do you want to be an alpha tester? π€
@antonio When I did this in the past it was either a Hetnzer dedicated server or a Codero one. Can't recall which, probably both at one time π Happy to do it again, but I'd want to invest some time to harden what I have in mind first... Do you want to be an alpha tester? π€
@antonio When I did this in the past it was either a Hetnzer dedicated server or a Codero one. Can't recall which, probably both at one time π Happy to do it again, but I'd want to invest some time to harden what I have in mind first... Do you want to be an alpha tester? π€
@prologic yeah I would like to be an alpha tester. π I also would like to learn how to setup something like that myself too.
@prologic yeah I would like to be an alpha tester. π I also would like to learn how to setup something like that myself too.
@antonio Cool! I'll let you know when it's ready for a "test drive" π€£
@antonio Cool! I'll let you know when it's ready for a "test drive" π€£
@antonio Cool! I'll let you know when it's ready for a "test drive" π€£
@prologic cool. You make it sound really simple. Is it just a Linux install where you create accounts that are not root and give the accounts credentials to the users? Or is there more to that?
@prologic cool. You make it sound really simple. Is it just a Linux install where you create accounts that are not root and give the accounts credentials to the users? Or is there more to that?
@antonio It's actually not really simple at all! π€£ The idea I have in mind is to have an instance of sshbox running on a uLinux VM. The tricky part is to work out how to persist the sandbox that you effectively end up with when you SSH in. You can _try_ this right now if you like by using your Github username, for example: ssh -p 2222 prologic@150.101.179.238
@antonio It's actually not really simple at all! π€£ The idea I have in mind is to have an instance of sshbox running on a uLinux VM. The tricky part is to work out how to persist the sandbox that you effectively end up with when you SSH in. You can _try_ this right now if you like by using your Github username, for example: ssh -p 2222 prologic@150.101.179.238
@antonio It's actually not really simple at all! π€£ The idea I have in mind is to have an instance of sshbox running on a uLinux VM. The tricky part is to work out how to persist the sandbox that you effectively end up with when you SSH in. You can _try_ this right now if you like by using your Github username, for example: ssh -p 2222 prologic@150.101.179.238
@prologic oh! cool! it works!!!! what can I do with it?
@prologic oh! cool! it works!!!! what can I do with it?
@antonio Pretty much anything you want at this stage. It's basically a full root Alpine shell (_sandboxed of course_). The only catch is that it isn't persistent (_yet_), that'll be the next thing I work on, is how to persist "sessions" if you will. What sshbox is is basically a small SSH server written in Go that invokes box another tool written in Go that sandboxes the inbound session/shell session into a container.
@antonio Pretty much anything you want at this stage. It's basically a full root Alpine shell (_sandboxed of course_). The only catch is that it isn't persistent (_yet_), that'll be the next thing I work on, is how to persist "sessions" if you will. What sshbox is is basically a small SSH server written in Go that invokes box another tool written in Go that sandboxes the inbound session/shell session into a container.
@antonio Pretty much anything you want at this stage. It's basically a full root Alpine shell (_sandboxed of course_). The only catch is that it isn't persistent (_yet_), that'll be the next thing I work on, is how to persist "sessions" if you will. What sshbox is is basically a small SSH server written in Go that invokes box another tool written in Go that sandboxes the inbound session/shell session into a container.