new stuff
This commit is contained in:
1
org/designdocs/artserver.org
Normal file
1
org/designdocs/artserver.org
Normal file
@@ -0,0 +1 @@
|
||||
#+title: Art Server
|
1
org/designdocs/imageboard.org
Normal file
1
org/designdocs/imageboard.org
Normal file
@@ -0,0 +1 @@
|
||||
#+title: Imageboard Software
|
33
org/designdocs/tenma.org
Normal file
33
org/designdocs/tenma.org
Normal file
@@ -0,0 +1,33 @@
|
||||
#+title: Tenma
|
||||
* Opening tenma up to friends
|
||||
Our server/intranet Tenma is currently underutilized, and it would be nice/fun/useful to open it up to select other people. This would only be available to friends, not a public service.
|
||||
|
||||
** Tenma Specs
|
||||
- Storage: 2×12TB in RAID 1
|
||||
- CPU: Ryzen 7 3700X (16 threads @ 3.6GHz)
|
||||
- Memory: 64GB
|
||||
- Network: Gigabit ethernet (Hetzner server in Finland)
|
||||
** Things that Tenma can provide
|
||||
*** Storage
|
||||
As of 23-06-2025, 4.6TB free space. Could start by reserving 1TB, which would provide enough storage for 20×50GB for guests users, which would be plenty for a long time. Tenma also hosts a [[https://github.com/9001/copyparty][copyparty]] instance that could be opened to the public to some extent or another.
|
||||
*** Bandwidth/hosting
|
||||
Tenma has full web hosting infrastructure set up (hosting this blog among other things), so that would be easy to extend to other people as well.
|
||||
*** VPS
|
||||
In line with the previous 2 points; compute resources are currently underutilized.
|
||||
*** Intranet
|
||||
Tenma runs a Wireguard VPN network. You can use this to, for instance, access services between two connected devices without having to open them up to the wider internet.
|
||||
*** DNS Server
|
||||
Tenma runs a fully resolving DNS server, with some local entries for devices on the VPN network. This should probably be automated in some way, and the service should be augmented with DNSSEC before opening.
|
||||
*** Git
|
||||
Tenma has a [[https://git.nakadashi.lol/][Gitea instance]]
|
||||
*** Livestreaming
|
||||
Tenma has infrastructure proven capable of restreaming 1080p video and high quality audio to at least ~100 people although this is CPU intensive and requires activating a high bandwidth restreaming VPS that is usually kept disabled to save costs.
|
||||
*** Other things
|
||||
Some other services that currently run on Tenma or have run there before:
|
||||
- [[https://github.com/dani-garcia/vaultwarden][Vaultwarden]] Bitwarden-compatible password manager server
|
||||
- [[https://soju.im/][Soju]] IRC bouncer
|
||||
- [[https://syncplay.pl/][Syncplay]] server
|
||||
- Video game servers (think Minecraft, Terraria, ...)
|
||||
** Considerations
|
||||
- This would require Tenma's internal documentation to be updated, adapted and publicized.
|
||||
- Security :teto:
|
36
org/designdocs/website.org
Normal file
36
org/designdocs/website.org
Normal file
@@ -0,0 +1,36 @@
|
||||
#+title: nakadashi.lol website
|
||||
* akko.nakadashi.lol Design Document
|
||||
** Hackerman Shit
|
||||
*** TODO Source Exposure
|
||||
Every page should have a button that takes you to the org-mode source for that page, using the beautifully named ~org-org-export-to-org~. This should interact properly with [[*Access Control]].
|
||||
** TODO Access Control
|
||||
The blog should have a form of access control. For instance, some things might be public, but other things I might only want to show to select people, or might contain other people's semi-confidential information that needs protection. Also, some people might want to opt out/not care about certain types of content, or I might want to present a certain "view" of the content myself.
|
||||
|
||||
As such, we need:
|
||||
|
||||
*** TODO System for marking content
|
||||
With one or more categories. This should definitely work at least on the section level. The most viable candidate feature seems to be [[https://orgmode.org/manual/Tags.html][org-mode tags]].
|
||||
*** TODO A way to export the correct selection of sections for every possible "view"
|
||||
Best place to start would be looking at [[https://orgmode.org/manual/Export-Settings.html][~EXCLUDE_TAGS~]]. Should export to org file first and from there to HTML, in order to enable [[*Source Exposure]].
|
||||
*** TODO A way of encoding which view corresponds to which html file.
|
||||
*** TODO A way of encoding which view should be given, for a given URL.
|
||||
i.e., the actual permission system. I definitely want to at least be able to:
|
||||
- Generate a direct link to a specific view;
|
||||
- Have a concept of a person having certain permissions, maybe through a cookie;
|
||||
- Be able to revoke permissions;
|
||||
- NOT have an "account system";
|
||||
- Of course, have security on this.
|
||||
** Style
|
||||
*** TODO different theme
|
||||
*** TODO theme selection
|
||||
** Social
|
||||
*** TODO Followable feed
|
||||
*** TODO Comment section
|
||||
Maybe powered by bluesky? I've heard that's a thing people do.
|
||||
** Meme features
|
||||
*** TODO teto face
|
||||
** Open Issues
|
||||
*** TODO Running the publish command in Emacs doesn't remove orphan HTML files.
|
||||
*** TODO Port [[../static/esquemadorg.js][esquemadorg.js]] to modern JS and get rid of jquery dependency.
|
||||
Good use case for AI
|
||||
*** TODO "Last Modified" implementation is a bit janky and I don't remember exactly how it works
|
1
org/designdocs/witch-princess-lyrica.org
Normal file
1
org/designdocs/witch-princess-lyrica.org
Normal file
@@ -0,0 +1 @@
|
||||
#+title: Witch Princess Lyrica
|
Reference in New Issue
Block a user