perma web

    _  _   ____                         _ 
  _| || |_/ ___|  ___ _ __  _ __   ___ | |
 |_  ..  _\___ \ / _ \ '_ \| '_ \ / _ \| |
 |_      _|___) |  __/ |_) | |_) | (_) |_|
   |_||_| |____/ \___| .__/| .__/ \___/(_)
                     |_|   |_|            

Personal Social Media

The internet — much like real life — isn't all friendly participants. Written text is prone to misunderstandings. All you say can and will be used against you. You have the right to remain silent.

That being settled, let's begin:

#Seppo! is built for welcoming onboarding and responsible, joyful and decades-long operation by you! To begin, put a single file on your webspace and visit it with your browser. That immediately unpacks the complete web application, generates a random initial password and off you go. Do posting and housekeeping via a convenient yet basic web-interface. Everything is in files you can inspect, once you are curious or modify, if you're bold. While neither being mandatory, however. There is no database, no server-side scripting nor obligatory javascript. You can backup the files and restore in case. There are no dependencies to install nor tend.

🍳 Mise en Place / Preparation

To have things your way and not being subject to third party terms & conditions, you have to own your grounds. “If you're not paying for the product, you are the product.”

An easy way is to rent commodity webspace + SSL + domain name. There are numerous vendors offering such, e.g. variomedia for EUR 30,- per year (which is how this website comes to you).

📐 Installation

1. download seppo.cgi,
2. ftp upload or copy it to your webspace,
3. name it 'seppo.cgi' and set it's file permissions to 'executable + readonly' for all user groups (octal/chmod 555),
4. visit https://example.com/seppo.cgi with a browser.

⛑ Support

When #Seppo! runs into a problem, it hints what you can do about it and tells a code. They are explained at Messages by Code.

Also the community mailing list archive may be helpful.

🆘 security.txt

In case of security incidents, consult /.well-known/security.txt

Software development happens at /sourcecode.