I’m stuck at a crossroads between what to do with my own. Not sure if I want to make it more of a documentation/wiki style site for everything I’m interested in or if I want to treat it more like a blog. I’ve got it hooked up to ActivityPub now and I’m intrigued by the possibilities that brings to the table, but I don’t think I’d want it to replace my Mastodon account, which puts it in a weird sort of limbo.

So I want to know, what do you use your own website for?

  • Lucy :3English
    2·
    4 months ago

    The public stuff is mostly self explanatory:
    @: just the badge stating I’m an abuseipdb contributor, which allows me to make more API calls, because I get massive amounts of ssh spam. I could do more tho 2fauth.: self hosted 2fa. Doesn’t work because it fails with Server error 500 and no logs, thanks php
    {api,proxy,}.piped.: Piped. The privacy friendly, alternative YT frontend
    {autoconfig,autodiscover}.: mail autoconfig/discover service
    brauerei.: a little “are you 18+” website for a local brewery
    cloud.: Nextcloud
    element.: Element web client
    git.: Gitlab. Gitea or something when the new management turns out to be shit
    gotify.: Gotify, a message server written in go. Mainly used for status messages (eg. systemd jobs failing)
    jellyfin.: Jellyfin
    jellyseerr.: A torrent/usenet manager for jellyfin, not in use because I’m lazy and just use soap2day etc
    lemmy.: the lemmy server, but as federation is wonky, I prefer this account
    malpaso.: a test wordpress install for a future website
    matrix.: Matrix/Synapse
    status.: uptime-kuma, a status service. Also uses gotify for msgs
    webodm.: Webodm, a service to stitch photos of drones together to a map

    Additionally a mail server.

    With that setup, I can also serve multiple “clients” with web and mail servers