about summary refs log tree commit diff
path: root/kittybox-rs/companion-lite/index.html
Commit message (Collapse)AuthorAgeFilesLines
* Moved the entire Kittybox tree into the rootVika2023-07-291-127/+0
|
* LibreJS compatibilityVika2022-10-031-2/+52
| | | | | | I don't know how worthwhile that was, given that LibreJS developers themselves don't care to properly declare licenses on the Bazaar frontend they use to host the extension's source code on the Web 🤡
* companion-lite: rewrite to use IndieAuthVika2022-10-021-10/+10
| | | | | This is a naive implementation that doesn't have some security checks. It's ok tho, should work fine... can refine it later
* PoC for modularity and WIP built-in Micropub client reworkVika2022-07-151-0/+77
This is the living, breathing proof that Kittybox can be split into independent components without sacrificing any functionality. Just make sure all neccesary backing storage components are available to the modules that need them. Also the Micropub client was split into several files, because it's about to get much bigger and more full-featured. Yes, I am going to write it in vanilla JavaScript. I don't trust anything from NPM to run on my computer. Not anymore. Not after the node-ipc malware fiasco. And I am definitely not going to spin up a VM or a Docker container (who uses Docker containers as a security measure?) to hack on my own code. Cargo can at least be sandboxed inside Nix, where it can't do much harm. NPM basically requires unrestricted network access to download dependencies, and it runs arbitrary code upon **downloading** them. Cargo and rust-analyzer, on the other hand, can be configured to not trust the source code and its dependencies (for example, Cargo doesn't execute code on fetching dependencies - only on building, and rust-analyzer's proc-macro expansion support can be sacrificed for more security).