Visual programming has a long history. See Nassi-Shneiderman-Diagram's, which are even a German (Now eu) DIN standard. And you have Drakon from the Russian space program.

Back in the day, XS4ALL, a Dutch internet provider had exactly this feature. They provided ssh access via port 80. It saved me a couple of time while I was traveling and the only way to get internet access was via hotel WiFi, which blocked everything except port 80. If anybody from XS4ALL is reading this... Thanks!

XS4ALL was amazing and it’s a genuine shame that KPN corporate decided to dissolve the brand. But I guess, KPN wouldn’t have been comfortable with XS4ALL’s hacker ethos anyways…

Fellow xs4all user here, it was fantastic, the real spirit of the early internet.

Sort of a redo of the pirate radio ethos of the 60s.

https://en.wikipedia.org/wiki/Pirate_radio_in_Europe

Among the non-standard ports for SSH, 443 is in the top ports used:

https://www.shodan.io/search/facet?query=ssh&facet=port https://www.shodan.io/search/facet.png?query=ssh&facet=port

Port 80 is a lot less common though.

I didn't realize they were a full on ISP! I recall using them back in the day as a newsgroup provider.

XS4ALL sort of lives on in the form of Freedom - https://freedom.nl/en

  had exactly this feature. They provided ssh access via port 80.

OP is describing something different:

- different port (443, not 80)

- different protocol used on that port (https, not ssh)

It seems the same to me: using a port that's open for a commonly used protocol, so http (80) in the 90s, https (443) now. Of course the protocol is different, that's the point!

It's not the same at all. OP's port 443 is not 'open' in the same sense that GGP's port 80 was 'open'.

In the old days, only the port number mattered. Today, DPI means the protocol matters as well.

The SSL negotiation part happens before any other communication. Once the encrypted connection is established, how do you analize the protocol?

Edit: I tested that time ago:

https://news.ycombinator.com/item?id=38753897

And to save roundtrips: I believe it must be possible to analyze encrypted traffic to find out which protocol is used. But I doubt that the hospital admins are so motivated or sophisticated.

> The SSL negotiation part happens before any other communication.

An SSH server and client do not use SSL/TLS to set up the connection. They use the SSH protocol.

As soon as you connect to an SSH server, the server sends an identification string. The identification string always starts with:

  SSH-

It's trivial to detect.

In the old days, corporate firewall rules were based solely on port numbers. So you could connect to an outside SSH server running on port 80, even if port 22 was blocked. Nowadays, an SSH server running on any port (80, 443, or any other) can easily be detected and blocked.

OK, I believe you, but then, does the trick described in the article work?

I ask because if it works, the principle is the same: using a commonly used protocol to circumvent limitations. It used to be easier to do then, it's more involved now.

In other words: is it possible to tunnel anything through https?

> the principle is the same: using a commonly used protocol to circumvent limitations

No it's not. The earlier method used only a commonly used port, and did not require the use of a commonly used protocol.

The purpose of using the TLS layer is to prevent the DPI.

Dpi has been around for a very long time.

Yes, but I'm specifically talking about a time when many corporate networks weren't yet using DPI.

OP describes tunneling SSH within another protocol. In the absence of DPI, this wouldn't be required.

The paradox of KISS is that it makes things simpler... for the designers. Because they don't have to think about the cognitive psychology aspects of their work.

There are some practical obstacles here. To name one. All high schools in the Netherlands use online schedule and agenda software.

Some fountain pens and a notebook. This allows me to quickly write down notes before jumping into my editor. This makes a big difference.

If I may piggyback on this, I would recommend the "Uni Jetstream 4&1 4 Color 0.5 mm Ballpoint Multi Pen + 0.5 mm Pencil". It costs only $10 and is available everywhere. It's one of those pens that has 4 buttons to change colors but this one also has a 0.5 mm pencil built in and a tiny eraser in the cap. Having the option to add color to my notes easily made them a lot easier to read, especially for code.

Currently I use two Jinhao X159s, which cost about $3 on aliexpress. Pretty decent writers. Cheap does not necessarily mean bad.

My work office365 mailbox is unusable. Normal mails ends up in spam or quarantine, or gets delivered with a very large delay.

TBF that might not be MS's fault. My work office365 mailbox is similar, but it was about the same before we moved to office365 due to additional filtering our IT does in the name of security.

Maybe let the AI enter your license plate the next time. ;-)

Zotonic is an Erlang CMS. https://zotonic.com

We have payment gateway solutions (stripe, mollie, buckaroo). See: https://github.com/zotonic/zotonic_mod_payment

It has a full blown MQTT communication bus. Browsers connect as mqtt clients to the cms via a web socket.

It looks incredible. But there is one really big omission. Where are the cyclists? Where they to difficult to model?

Yes indeed. We also have something not more similar to what liveview offers. It is here: https://github.com/mmzeeman/zotonic_mod_teleview. It is based on mqtt, and the views are updated with normal html like templates. This makes it possible for frontenders with html and css knowledge to contribute to a project with a rich SPA like interface.