@nixCraft this ssh -G option can be used to make sure that a site-specific public key is used to avoid inter-site tracking. This is also why http://supertxt.net recommends using the “nobody” user, which can also be checked in this way. Unlike the web, ssh gives the user much more control over their identity.

#supertxt #postweb

The #supertxt team finally released the server implementations (ssh and http) that they use for the http://supertxt.net site. There's more details in the readme for the st-int repo.

``` .sh
git archive --remote=nobody@supertxt.net:git/st-int HEAD README.md | tar -xOf -
```

#postweb #ssh #linux

@kdorse this is why I like that http://supertxt.net only allows conventional comments and they are only visible on demand instead of every page view, kinda like wikipedia. The bottom of each page explains how to do that.

#postweb #supertxt

There's a new #supertxt specification for pathname2, which are the sort of paths that you use with sshla tools like git, scp, and the cats tool.

There's some interesting comparisons with URL's at the bottom. The paths are almost equivalent to hyperlinks, but are only independently sharable with the full command-line. The paths themselves can be re-used to create new command lines referencing a file.

http://supertxt.net/specs/pathname2.s.txt

#postweb #unix #linux

The SSC (site-specific command) provides client-side custom experiences for working with that internet site, which is a bit orthogonal to SSHLA (SSH Layer Application), which is specific to a workflow/action (ie. verb) that you're trying to do that has an opinionated way of working with a site, such as SSH, and the command-protocol on top.

http://supertxt.net/whats-sshla.s.txt

What's interesting about SSC is that it can also bridge the gap by providing the client side logic to fulfill the command when the service doesn't implement SSHLA itself.

Also, there's the fact that with SSC and command-line invocation into any application state, it makes command-lines closer to being on-par with URL's in terms of sharing and repeatability, which is one of the goals of #supertxt to help bring the OS to a level of parity with web technologies.

In a world where we have installed tools to provide rich experiences for internet services, here's an article about how this can work. Also, there's examples about how to integrate with site-independent commands.

http://supertxt.net/intro-to-ssc.s.txt

#supertxt #postweb #unix #linux

There’s been a bunch of exciting new feature development going on at http://supertxt.net I hope to do a new youtube video shortly. Meanwhile, you can give it a try yourself. There’s two git repos, both Go. #supertxt #postweb

``` .sh
git clone nobody@supertxt.net:git/cats && (cd cats; go install ./…)
git clone nobody@supertxt.net:git/st-int && (cd st-int; go install ./…)
```

If your ~/go/bin is on the path then I recommend trying brsh (browsing shell). It has a help command to get you started.

@blinry This is is a really cool tool for browsing json apis. It reminds me of the browsing shell tool for browsing text apis over ssh. https://youtu.be/mL1C1V3c3js #supertxt #postweb

I got up to some more #supertxt adventures and recorded a video about it. This time the focus is on hyperlinks and the way that it works. The command line tool itself participates using “reflection.” The browsing shell doesn’t yet have a stable version, but it’s starting to become more interesting

https://youtu.be/mL1C1V3c3js

#postweb #ssh #unix

I gave the new #supertxt integrations repo a spin yesterday. There's a tool called the "browsing shell" that works great wit the site. It's a fully graphical interface with a familiar bash/zsh feel. The combination of supertxt content, cats command and the supertxt.net site work well together. Here's my quick walk through the tooling.

https://www.youtube.com/watch?v=xEbQ4nd99eI

#postweb #simpletext #www

The http://supertxt.net site now supports http://conventionalcomments.org for constructive feedback. There's examples at the bottom of each page and also a manual for the command.

The manual itself is here:

``` .sh
ssh nobody@supertxt.net man ccmnt
```

I've already added my comments on there.

#supertxt #linux #ssh #postweb #www

@dansinker I think that if we’re going to experiment by burning things down and making new things (ala punk rock) then why not invent a new web replacement while we’re at it. We can bake in user centred auth and visual preferences. Also, make it much easier than 1000s of person years to build a new compliant browser for an OS we’ve never heard of yet.
http://supertxt.net
#supertxt #ssh #postweb #web #gemini

@ariadne @mariusor @filippo I think that we should revisit the concept of URI’s. There’s some ideas about how that could look over here.
http://supertxt.net/hosting.s.txt
http://supertxt.net/browsing.s.txt
#supertxt #www

TIL that a git bare repo, like on a server, can contain other files and directories. Git doesn’t care as long as there is no collision. There’s no reason why there couldn’t be a directory with issues in there. #git #linux #supertxt

The #SuperTXT site has some new usages, including a new "scat" tool that remotely cats a file over ssh.

``` .sh
git clone supertxt.net:git/scat
cd scat
go install ./...
```
After installation scat works as one might expect with any sshla tool, such as git.

``` .sh
scat supertxt.net:browsing.s.txt
```

#text #postweb

After spending a few minutes learning LaTeX basics, I can’t help but feel that this is still a language that is 100% focused on faithfully typesetting age old mathematical notation. It doesn’t seem like something that can be reasoned about directly.

#math #latex #text #supertxt

What's SSHLA?

How does it relate to SSH? How do we make new SSHLA programs? Why can I single sign on with git, scp, and VS Code on the same server?

Here's an article that attempts to explore some of these things. http://supertxt.net/whats-sshla.s.txt

#ssh #postweb #sshla #supertxt #oss #linux