Despite this (a limitation that should be relatively easy to fix/change; there are probably more), I'm now actually considering spinning up an experimental personal #Epicyon instance. I think this is the first piece of #Fediverse software that has made me think it might be time to set up my own plaything. It probably won't be “right now” though, but only because I have way too much stuff in my hands at the moment and the last thing I need is experimenting with a new server software.

3/

Dangit, I wanted #Epicyon to work.

...I really wanted Epicyon to work. The ability to set up skills and roles and match them with need seemed like a fantastic way to build online profile connection discovery and interest groups...

...maybe sometime later I can do something with this, but for now...it's just an inspiration that more can be done.

Chonky server doesn't have the HTTP Strict Transport Security errors (so far), but I still can't figure out how to make a post show up.

I now have three posts according to the file tree, but nothing is showing up on the web application frontend.

Then, I make another account, and two of the posts show up for the original account but not the third and original post. Why are there two buttons for making posts? Why is the logout button only on the account page? Why can't I find accounts by name on my own instance?

These, and other questions, are arising with the #Epicyon project, and I'm concluding that it's not ready for actual use.

Looks like the CPU pegs at 100% when I post an animated GIF.

Time to put on the debuggin' gloves.
#Epicyon #LibreOps

Things that I like so far:

• account registration walks you through whats different from "corporate" social media.
• site design is a bit retro, which feels really chill
• things like the introduction and terms of service are just text files you can edit.

Things I've encountered that seem like a problem:

• The HSTS security feature is working sometimes and not working other times, and showing "domain.tld doesn't match domain.tld" as the error even though they are literally the same domain.
• The HSTS error has cropped up, disappeared, and re-appeared about a half dozen times now, with no indication of what's causing it and no obvious change that triggers it. Sometimes just clicking a link does it, sometimes doing a cache wipe and reload fixes it. This is my least favourite type of error.
• Got a 502 Bad Gateway because the python application crapped itself when I made a post scheduled for the year 0002, which is rude.

There's definitely a resource bottleneck on this hardware, but the site does indeed run. Next I'm going to be setting up several accounts, post an assortment of content, and then attempt to federate with another server on my LAN to see what that looks like.

#Epicyon #LibreOps

For reference, that's about 8.8% of this host's capacity, and it's using 2.5% of the available CPU.

Let's see how those numbers change as I start making it do things.

#Epicyon #libreOps