mmzeeman

True. When I mentioned this on an FP Discord, people actively shared tips about content blockers.

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!

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.

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

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

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

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.

Yes, the website is old and about to be retired.

We are about to release 1.0. The new site is not entirely ready. This is a preview. https://test.zotonic.com.

That is an non-standardised DIY pub/sub protocol over a websocket.

There is no efficient pub/sub functionality in HTTP.

MQTT is a proven protocol. It's design started started more than 20 years ago. The protocol was designed to be easy to implement. It is simple to implement if you want. There are multiple brokers, and client libraries available. So why invent a new protocol, when an open, standardised protocol already exists.

Open pages in a browser are not that different from IoT devices.

An example proof of concept application: https://github.com/mmzeeman/zotonic_mod_doom_fire/

Very interesting. I've implemented something similar. It evolved out of the co-browsing solution I developed for the company I work for.

The solution uses mqtt. Clients subscribe to a topic on the server, and the server publishes patches to update the view. Patches can be incremental (patch against the last frame), cumulative (patch agains the last keyframe) or a new keyframe. It allows for server side rendered views. Multiple clients can subscribe to the same view and keep in sync. See: https://github.com/mmzeeman/zotonic_mod_teleview

The best way to do pub/sub on the web with a standard protocol is MQTT (https://mqtt.org). It supports websockets, it scales, supports authentication, can handle unreliable networks.

We use it exclusively for the soon to be released 1.0 version of Zotonic. See: https://test.zotonic.com (running on a 4.99 euro Hetzner vps).

We developed an independent support javascript library called Cotonic (https://cotonic.org) to handle pub/sub via MQTT. This library can also connect to other compliant MQTT brokers. Because MQTT is fairly simple protocol, it is fairly easy to integrate in existing frameworks. Here is an example chat application (https://cotonic.org/examples/chat) which uses the open Eclipse broker.

Did research on SSE a short while ago. Found out that the mimetype "text/event-stream" was blocked by a couple of anti-virus products. So that was a no-go for us.

Back in the day there was also a huge security hole which could be exploited with the xwd command. If you knew the dns name of a terminal you could get a screendump from it. It was not secured at all.

xroach ftw!

We have build a nice support library for it. https://github.com/cotonic/cotonic. It helps that our backend is Erlang. https://github.com/zotonic/zotonic.

You don’t have to design a new protocol. There is an open protocol which works nice for this use case. It can handle dropping connections, has a nice routing mechanism, it scales pretty well, has different QoS levels, pub/sub, request/response. That protocol is... MQTT v5!

Personally I’m surprised it is not used more often by web devs.

Tagging for Windows seems to be more complete. It is fully integrated into the windows explorer.

https://tagging.connectpaste.com/home

It is more like a web-framework with a built in CMS.