Werefox

A collection of self-hosted services and software

Quick note before we get started – these “weekly updates” are just going to be titled as blog posts/news headlines. Monthly updates will be titled with their respective month. This is to keep me from feeling like I’m committing to posting these every week, and to keep from doing some kind of unnecessary numbering scheme.

System Updates Account

I’m happy to announce that there’s a system updates account that can be followed on the fediverse which will be posting whenever Werefox Software updates their services or has to go down for maintenance, or any other system admin related updates that may be important. @system@masto.werefox.dev will now be a default followed account for all new users, since it’s a filtered way for any new users to get important updates.

Gitea Update Script

I’ve also taken the time to write out a nifty script to update Gitea when new versions are released. This should both save time and help maintain security as when new updates are released, the script will be run daily to check and replace the current binary. Additionally, I’ve written a follow-up script to run once it has successfully grabbed an updated Gitea binary to post using the previously mentioned @system@masto.werefox.dev account.

Repo link: https://gitea.werefox.dev/shadow8t4/gitea-update

Future Work

In order for the update script to post to Mastodon, I wrote a simple Python script using Mastodon.py. I’m hoping to incorporate this script into future automation regarding system updates and announcements. Once I’ve made enough progress developing this, I’ll gladly make a new repository to host it. On a related note, I do currently have a working project I’ve been meaning to make more development progress on... But I’m not quite ready to formally announce it just yet.

Logo Change

I officially have a new logo for Werefox Software, which I’m pretty excited to reveal!

New logo for Werefox Software. Credit: https://meow.social/@owenthecat

Credit: @owenthecat@meow.social

It’s quite a bit simplified than the previous logo, and retains the color scheme from before. Most, if not all, services should have the logo changed at this point.

Other Updates

I’m still looking for a solid email-blacklist to implement on the Mastodon instance. In the meantime, I have implemented a suspend list and will be working on a way to dynamically update a public-facing list of which instances we’re suspending/muting/etc. in the near future. I don’t want anyone to join the instance without being aware of what instances I’m blocking.

Future Updates

glitch-soc and client-side matrix are still in the works. Didn’t get around to it this week, sorry.

That’s really all for this week. Really glad I’m doing these “smaller updates” because the monthly one would just be absurd if I tried to put this much in it.

I’ve finally gotten around to getting the mautrix-telegram bridge bot back up and running, so you can now join the general chat at this link on Telegram once again.

Other updates

I’ve set up daily backups for Gitea, GitLab, Mastodon, and Matrix now. Keep in mind that I in no way wish to “archive” any data, it’s simply in order to ensure I can get things back up and running in the case of a failure (yes, I meant to make that jab in light of recent events).

After thinking it over some more, I’m a little hesitant on running PeerTube and Pleroma instances. I have been really strapped for time lately, and since it’s really only me managing all these services, with my own funds as well, I don’t really want to expand too fast or at a rate that causes me to feel burned out.

Future Updates

I’m now shifting my attention to focusing on improving the services I currently host. I’m looking into “upgrading” the Mastodon instance to use “glitch-soc” and I’m looking into hosting a client for Matrix, that way potential community members can have a way to try out Matrix and communicate as a guest if needed on our own domain rather than being forced to register at Matrix.org or having to mess with client settings in order to register on Werefox Software.

That’s all for now. I’m hoping to provide more more quick updates in the future in order to make the monthly ones less packed.

I've finally managed to migrate the mastodon and matrix instances. They should both be up and running and open for registration.

Discord & Telegram

However, I'm sad to report a couple casualties. Currently, the Discord bridge bot doesn't seem to be working. I've tried all day to get it up and running properly again and have decided to ditch the bot altogether, as no one seems to be using it (including myself), and it's way too much trouble getting it to work. Additionally, the Telegram bridge bot is down for the time being. I'm interested in getting this back up, however, as I use it regularly to read and respond to my Telegram messages.

As a result of the Discord bot no longer being supported here, I've taken down the Discord server. It's possible I'll create another one for a more gaming-centric purpose in the future, but I'm pretty done with getting that bot to work.

Pleroma and Peertube

As far as Pleroma and Peertube are concerned, I've upgraded the Optiplex with an external 10TB hard drive for storage, and the working plan for part of that is to have Peertube's storage connected to it. However, at the moment its primary purpose is as a storage for the Gitea and GitLab instances, as well as for backups and local shared storage. For Pleroma, I'm looking into the possibility of running a docker image. I don't particularly want to keep dealing with bare metal installations of these services, and a containerized one may help with portability down the line should I ever choose to move devices again.

Closing Notes

I'm thinking of posting at the least a monthly update on the services and progress between work. I may also post a few articles here and there. That's all for this month!

The first major step to migration to the new domain has been completed, thanks to the help of write.as!

Over the course of the next week the servers will be off & on as I continue the migration from werefoxsoftware.com to werefox.dev. The mastodon instance will be essentially formatted and a new one will be started.

I’m currently looking into simultaneously hosting a Pleroma instance alongside to keep up with the development of that service and offer options for any future users, as well as considering the addition of a PeerTube instance to host my own and future users’ videos.

More details on all of this will be posted as they develop.

Mastodon

Mastodon is an online, self-hosted social media, and social networking service. It allows anyone to host their own server node in the network, and its various separately operated user bases are federated across many different servers.

Pinafore

An alternative web client for Mastodon, focused on speed and simplicity.

Halcyon

Halcyon is standard Twitter like client of Mastodon, And you can use it just by login to your instance. Let's Toot like a tweet.

Brutaldon

Brutaldon is a brutalist, Web 1.0 web interface for Mastodon and Pleroma.

PeerTube

PeerTube is a free and open-source, decentralized, federated video platform powered by ActivityPub and WebTorrent, that uses peer-to-peer technology to reduce load on individual servers when viewing videos.

Matrix / Element

Matrix is an open standard and lightweight protocol for real-time communication. It is designed to allow users with accounts at one communications service provider to communicate with users of a different service provider via online chat, voice over IP, and videotelephony.

Element (previously Riot) is an all-in-one secure chat app for teams, friends and organisations. Keeps conversations in your control, safe from data-mining and ads. Talk to everyone through the open global Matrix network, protected by proper end-to-end encryption.

I have a community hosted on my Matrix instance, you can use the link here to join: – Community+werefox-software:matrix.werefox.dev Or you can just join the main chat room: – Main chat#chat:matrix.werefox.dev I also have bridge chats for the following services: – Telegram

Gitea

A painless self-hosted Git service. Gitea is a community managed lightweight code hosting solution written in Go. It is published under the MIT license.

Anyone looking to make use of our services is expected to adhere to the following community guidelines. 1. Treat everyone like a part of the community. a. Do not make threats, violent or otherwise. – Note: Death threats and suicidal threats will be taken seriously at all times. b. No bullying or harassment. c. No unwanted (or continued unwanted) sexual or romantic advances, including sexual harassment, whether public or in private. d. No spamming on any medium. This includes, but is not limited to: emoji, stickers, repeated posts, unwarranted/non-cw’ed long posts. e. No misuse, mistreatment, or unnecessary public use of any bots. f. No pictures, videos, media, or discussion of illegal activities (inside the jurisdiction of the respective region the activity was committed). Please see more specific details of this below. 2. Keep the community safe. a. Respect others’ personal space. b. Keep discussions civil (e.g. no personal insults or threats). c. Report bad or questionable behavior. 3. NSFW Content is defined here as the following: a. In general, things that are considered Not Safe For Work. Anything that would otherwise be deemed inappropriate to view or say in a public, school, or work setting. b. Depictions of sexual organs, implied sexual content, or any implied rule 34 related content. c. Depictions of excessive gore, violence, or profanity. d. Discussion or implied discussion of sexual activities, innuendos, gore, or kink related activity.

Service Specific Guidelines

Here are some rules specific to the services we offer.

Mastodon

We expect new users to at least adhere to the guidelines outlined on the flagship instance's about page, listed here, as well as the basic guidelines outlined on this page, in addition to the following: – Posts should have a content warning attached if they contain the following: – NSFW content, art, or language. – Political discussion, articles, quotes, depictions, etc. – Advertisements, including personal ones. – Content known to be triggering towards other users on the instance.

Homeroom (or any of our official chat rooms)

Something something json

Gitea

Something something lightweight

Administration & Moderation

Everything you should need to know about how we moderate the community. We believe having this publicly available can only help the community, as this way everyone knows what we’re all being held accountable for.

Administrators & Moderators

The primary job of all admins and mods is to moderate discussion, enforce the guidelines, and appropriately and promptly respond to reports and issues raised by the community members and those outside the community. 1. Admins/mods are not dictators and should never: a. Make any user or member of the community feel singled out or belittled. b. Give opinions on a matter or situation as if it were law. c. Carry out unnecessary deletion of comments, kicks, bans, etc. d. Act or present themselves as though they are above or do not need to adhere to the community guidelines. e. Ignore or dismiss legitimate criticism, suggestion, or discussion of how the community is being moderated. 2. Actions an admin/mod may take: a. Step into an active discussion to ask that it be moved to DMs or another forum (this should mostly be done in official chat rooms). b. Warn that a discussion is inappropriate for the current forum or otherwise violates the community guidelines. This may result in the request and/or deletion of the offending posts. c. Ask that the discussion stop and that the current forum move on to another topic (again should mostly be done in official chat rooms).

Reporting

While we acknowledge that reporting others can be a stressful or unpleasant activity, it is necessary for maintaining the safety of the community as a whole. Here are the following ways a user or member of the community can report activity. 1. Contacting an admin/mod directly. Contact information for all admins/mods will be publicly available on all of our services. 2. We will also offer an anonymous form for reporting users in the future.

Enforcement

It should be first stated that since incidences can vary in intensity and variety across platforms, respective consequences are up to the admin’s/mod’s discretion. 1. In general, minor offenses (especially a first one) will be dealt with a warning by an admin/mod and possible removal of the offending content. a. In most cases, the offending community member will be directly asked to remove the content themselves. b. If it is not removed within 30 minutes of the request, an admin/mod has permission to remove it. 2. Continuous violations of the community guidelines and/or respective service’s guidelines will most likely result in a kick or ban. a. In most cases, this will require the agreement of the majority of active admins/mods. b. In extreme cases, admins/mods may kick or ban members without doing so. c. Any action of this kind should be followed up with a public statement on why the action was taken and how it was justified.

Challenging an Administrator or Moderator

If a member of the community has a disagreement on the way a certain situation is handled, they may do the following: 1. Personally message an admin/mod explaining the disagreement with the actions taken and their side on the matter. This won’t guarantee that the enforcement will be lifted or reversed, btu will make the admins/mods aware that there is a disagreement. a. Please include everyone you know has a disagreement in your initial message. They will each be individually contacted for their say on the matter. b. Regardless of whether the enforcement is lifted or reversed, an admin/mod will make a public statement on the disagreement and resulting action. This ensures that everyone knows and acknowledges that there was a disagreement and that/how it was considered by the admins/mods. c. All complaints will remain anonymous unless they have otherwise specified that they wish to have their names public. This ensures the privacy of reports and clarity with members. 2. If you wish to be completely anonymous, we will in the future be offering a report form. The actions listed in the previous bullet will then be carried out. 3. Publicly express your grievances with our decision. It’s not recommended to take this action, as it can cause great stress on the community as a whole. a. An admin/mod will make a public statement acknowledging that there was a disagreement and that/how it is being taken into consideration. b. Member(s) expressing their disagreement will be contacted to allow them to express their full view on the matter (if they feel they need to say anything else). c. Regardless of whether the punishment is reversed or liften, an admin/mod will make a public statement that there was a disagreement and the resulting decision, and will preserve anonymity when possible.

Last updated: 26th of October, 2018