ELIZA is an early natural language processing computer program developed from 1964 to 1967 at MIT by Joseph Weizenbaum. Created to explore communication between humans and machines, ELIZA simulated conversation by using a pattern matching and substitution methodology that gave users an illusion of understanding on the part of the program, but had no representation that could be considered really understanding what was being said by either party.
ELIZA - Wikipedia (modified)
Good morning ELIZA, it has to be very hard empathizing and communicating with everyone if all they don't keep the conversation going.
Sorry
In all seriousness though, I'd like to hear as well.
yes: sntx.space, check out the spurce button in the bottom right corner.
I'm building/running it the homebrewed-unconventional route. That is I have just a bit of html/css and other files I want to serve, then I use nix to build that into a usable website and serve it on one of my homelab machines via nginx. That is made available through a VPS running HA-Proxy and its public IP. The Nebula overlay network (VPN) connects the two machines.
nah, we have run0 at home
That's a working model, but I think there are different types of relationships. A type of relationship would be an element of the power set of { friendship
, romance
, sex
}.
One person might only like relationships without sex
, another might dislike the whole romance
part,...
Each of these aspects of a relaionship has their advantages and disadvantages. The relationship as a whole is just the sum of them.
Yes, Taler by design allows identifiction of the receiver.
It does not reveal the sender.
It allows you to create and arbitrate your own tokens and to create your own "bank".
I have three things to say:
- Everyone, please make sure you've set up sound disk encryption
- That's not a suprise (for me at least)
- It's not much different on mobile (db is unecrypted) - check out molly (signal fork) if you want to encrypt it. However encrypted db means no messages until you decrypt it.
I cleaned my bin.
All that's left is a symlink: sh -> /nix/store/...
What would you tell a direct ancestor of yourself, living in the year 2024?
You're playing Devils Advocate, and you probaly know it xD
Anyway, I prefer NixOS for it's declarativity, reproducibility and immutability.
Example: You want nginx with acme setup? Just tell it to, and NixOS will figure out the steps to reach the desired state.
- NixOS
- disko + nixos-anywhere (automatic partitioning & remote installation of new systems)
- stylix (system-wide theming)
- agenix (secret management)
- impermanence (managing persistent data)
- nixos containers for sandboxing applications & services (using systemd-nspawn)
- TMPFS as /
- LUKS
- BTRFS as /nix (might try bcachefs)
- SWAP partition (= RAM size, to susbend to disk)
- Greetd with TUIgreet (DM)
- SwayFX (WM)
- Kitty & foot (term)
- Nushell (shell)
- Helix (editor)
- Firefox (browser)
- slackhq/nebula (c.f. self-hosted tailscale, connecting my systems beyond double NATs)
EDIT1: fix "DE" -> "DM"
If you connect to the network and open firefox, it will display a toast to open the corresponding captive portals page. You can then login through that. Given that your VPN isn't blocking unencrypted connections etc.
Extrapolation of partial knowledge warning
I assume the network advertises a captive portals url and identifies you based on your MAC address.
The config is server-side (router).