> In the most common case you'll be using systemd to set up a daemon to run the server.

Such assumptions by the IBM anti-unix fanboys can push plenty people away from taking such efforts seriously.

If someone is so ignorant as to start a nginx or other server in a system and needs specific commands to do so, should this indicate a security issue in itself? By the way, a few years ago when Distrowatch did a poll on favorite init systems systemd was 3rd, with OpenRC, Runit, s6, sysV receiving twice the voting.

Linux itself 8 months ago decided to comply with US state dept. instructions on who to have on board or not to, with the threat indirectly being the US based corporations funding Linux Foun. therefore the millionaires developing it. Do you have any doubts on those other "Foss" projects funded by similar blackmailers (such as Rust or Go) that it is all NoSuchAgency compliant software?

Then there is https://github.com/skarnet/tipidee https://skarnet.org/software/tipidee/

Using the crap is one thing, advocating for nearly 100% US based distros and software companies is another. You are not salespeople and should avoid that role.

#epicyon #omn #4opens

https://unite.openworlds.info/indymedia/epicyon/src/branch/main/README.md

PS With driving Baikhal out of business now "they" control 100% of the hw/architectures foss is running on.

I'd say such projects should be taking those tendencies under perspective

@hongminhee @thisismissem @PuercoPop

For your information, I recently opened an issue to track current #ActivityPub C2S implementations.

This is the list thus far:

#ActivityPods
#Epicyon
#Onepage.pub
#Pleroma
#RDFPub
#Vocata
#FedBOX
#Mitra
#streams
#forte

https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130

Client-side #AndStatus is a well-known attempt to implement it:

https://github.com/andstatus/andstatus/issues/499

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/

So I'm checking out #Epicyon https://libreserver.org/epicyon/ (which I discovered thanks to @atomicpoet), which might be just the kind of AP server I'm looking for. I delved into the code to check how it stores the data and it seems it's going with the “static files” approach over the DB used by basically anything else, and this is pretty much what I was hoping for (I'd be OK with something lightweight like sqlite to cache the metadata for speed, this one seems to use text for that too?)

1/

Since I have a really bad hand with timing my posts, so that the least amount people possible see them, I have to try again :wink:

Anyone out there who knows about hosting Fediverse Applications behind an Apache Reverse Proxy?

To be more specific - I have been trying for days to get Epicyon running on my server. Installation was easy and it is running, just not completely. I cannot follow people or accept follows from others and proxying is the most likely culprit (I'm seeing 400 and 401 errors in Epicyon's logs)

The Installation Manual describes how to set up a nginx Reverse Proxy but I already have Apache and cannot change that. I do run other services using it as a proxy though and these all work as expected.

I'm out of ideas and would appreciate any help translating from nginx config to Apache. Boosts Welcome!

#fedihelp #hosting #apache #epicyon #reverseproxy #selfhosting

Dann hast du Zahnstocher statt Finger und lädst nie Bilder hoch. Also zumindest was Friendica angeht :wink:

Die Mobilvarianten von Peertube und Pixelfed kenne ich nicht. Im Moment spiele ich mich grade in wenig mit #Epicyon herum. Da gibts nur das Webfrontend, das ist aber auch ganz gut aufm Handy.

@jakob

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.

So, the #Epicyon instance on the raspi zero w keeps not responding when I try to make it do things. Not just posts, but stuff like editing the profile, and there seems to be a mild correlation between the HSTS problem and asking it to do stuff that isn't just displaying info.

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

And we've got a login screen!

The test #Epicyon instance is using about 55mb of RAM to serve the login page.

I'm installing this on a Debian host, because configuring a declarative system for this would take a lot longer. Using an imperative host allows me to move more quickly, test things out, and decide whether it's worth the effort to build better infrastructure around it. #libreOps

This system is already running a webserver and mjpeg-streamer, which leaves me with about 200MB of RAM for Epicyon to eat.

Last time I worked on getting #Epicyon set up, not having a proper certificate was a blocker, but this time I'm setting up an actual domain, so apparently I'm more serious about it this time around.

It's gonna be a single user (me) instance, but with multiple accounts.

#libreOps

So in an effort to figure out if #Epicyon can work for me, I'm installing it on one of the raspi zero w systems that I keep around for portable projects.

Pulling the repository down from GitLab while the dependencies install: https://gitlab.com/bashrc2/epicyon

#libreOps

Vielleicht der Zeitpunkt um auf eine Alternative wie z.B. #Epicyon zu wechseln. Das läuft dann auch mit Lynx.

Mehr als 5-10 User kann man damit zwar eher nicht hosten, aber irgendwas ist ja immer :wink:

@thomas

@RL_Dane 500 Characters encourages using #Mastodon for Microblogging, which is what it's for. For actual blogging, a blog ought to be used. That said, it would be nice to mix between them, like #Epicyon can (just a shame when I last used that it was buggy as hell)...