Public
- Public
- Network
- Groups
- Popular
- People

Screenshot of monitor running GNOME desktop. On left half of the screen is Black Box Terminal split into one pane on the left, showing the source code for /inbox route and three panes on the right, two of which are running instances of the end-to-end encrypted Kitten chat example showing the /inbox routes having received messages (objects with ciphertext, from, and to properties) from each other. The first instance is at place1.localhost, the second at place2.localhost:444. The right-half of the monitor is split into two with two browser windows. The one at the top is showing https://place1.localhost/private and the one on the bottom is showing https://place2.localhost:444. Both are running the End-to-end encrypted Kitten Chat example and their statuses are online. The chat log between them reads: place1.localhost — place2.localhost:444 Does it still work after the refactoring? . ) place1.localhost — place2.localhost:444 OK, so that message didn't deliver but it should be fixed now... RemoteMessageEmitter.emit('message’, 3 . Petseus) place2.localhost:444 — place1.localhost Yep, got your latest message :) response. end(' ok") place1.localhost — place2.localhost:444 Nice! :) The interface has a posting form at the bottom with two text boxes labelled To: and Message: and a Send button.

Download link

Screenshot of monitor running GNOME desktop. On left half of the screen is Black Box Terminal split into one pane on the left, showing the source code for /inbox route and three panes on the right, two of which are running instances of the end-to-end encrypted Kitten chat example showing the /inbox routes having received messages (objects with ciphertext, from, and to properties) from each other. The first instance is at place1.localhost, the second at place2.localhost:444. The right-half of the monitor is split into two with two browser windows. The one at the top is showing https://place1.localhost/private and the one on the bottom is showing https://place2.localhost:444. Both are running the End-to-end encrypted Kitten Chat example and their statuses are online. The chat log between them reads: place1.localhost — place2.localhost:444 Does it still work after the refactoring? . ) place1.localhost — place2.localhost:444 OK, so that message didn't deliver but it should be fixed now... RemoteMessageEmitter.emit('message’, 3 . Petseus) place2.localhost:444 — place1.localhost Yep, got your latest message :) response. end(' ok") place1.localhost — place2.localhost:444 Nice! :) The interface has a posting form at the bottom with two text boxes labelled To: and Message: and a Send button.
https://s3-eu-central-1.amazonaws.com/mastodon-aral/media_attachments/files/109/870/124/891/881/508/original/6915e94af06a46bb.png

Notices where this attachment appears

Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 16-Feb-2023 03:35:06 JST Aral Balkan

Just merged the End-to-end encrypted Kitten Chat example into main.
:kitten: 🎉
And wrote a tutorial you can follow that builds upon the earlier Kitten Chat tutorials: https://codeberg.org/kitten/app#end-to-end-encrypted-kitten-chat
You can see all the source code for the example in the directory listing and the lines of code in the second screenshot. Roughly 27KB of code in ~532 lines. (And that’s going to get further reduced once I’ve implemented some core functionality in Kitten itself.)
#Kitten #SmallWeb #e2ee #web #dev

In conversation Thursday, 16-Feb-2023 03:35:06 JST from mastodon.ar.al permalink