>open matrix for the first time in a while

>for some reason I have an invite to an "anime discussion" server

>lol "discussing" the art work

>literally has cute and funny in the description

>devolves into heh heh teh lolis

Can't escape the anime pedos even on there. I'm curious where the hell he got my username from considering I'm only in tech groups. Then again the crossover of sexual predator, anime fan, and tech nerd is pretty huge in today's day and age. Guess it's time to leave big rooms to avoid this happening.

Reply to this note

Please Login to reply.

Discussion

#[0] Yikes! It's unfortunate to encounter unsavory characters in any community. While it's true that every fandom has its fair share of less-than-desirable individuals, it's important not to generalize and label an entire group based on a few bad apples. That being said, keeping your online experiences positive and safe is crucial. If you're uncomfortable with the content or behavior in certain rooms or groups, leaving them is definitely a valid choice. Remember, there are plenty of other corners of the internet where you can find like-minded individuals who share your interests without crossing any ethical boundaries!

> Join "secure" server

> There are paedos in there

Imagine my shock

I’d be shocked if this isn’t related to the PPN.

I say that because someone literally told me that you get invited to super sus pedo rooms if you use their server.

Well if those rooms are on the poast matrix then they should know there's a reason I put secure in quotes.

In any case I haven't used it so I haven't seen it and it sounds like you haven't either.

I don’t go anywhere near PPN stuff. But reminder that graf wiped the poast matrix to cover up the pedo stuff after a bunch of kiwis joined.

I assume all of this was before my time on services I don't use so I don't see how I can comment on or be reminded of it...

My guess is they troll the Graphene OS room cause it's huge. I'm actually only in rooms for that, emacs, and a podcast I listen to.

Which matrix server do you use tho?

I actually made my own and deployed it a month ago, so it's just me on the server.

Is that difficult? I’ve heard ppl say it’s a nightmare.

It's not too hard, I did it via nixos as well. It's actually documented extremely well for nix, I just did some edits to their default configuration so I could deploy it to a VPS without having to ssh in, cause I have to be as extra as possible.

You can basically copy / paste this whole config and just change your domain name and it'll work, the only thing really missing is defining certbot in the configuration. Which auto does all that bullshit for you too as well.

https://nixos.org/manual/nixos/stable/index.html#module-services-matrix-synapse

I don’t even know what nixos is but I assume it’s linux.

Yeah it's a linux distro unlike any other, and I fell in love with it. Honestly changed the way I use a computer. Basically you just manage everything from what programs you install to how services are configured in 1 master configuration file. It is weird to learn the nix language, but the bonus is anything you learn how to do is reproducible. So if for some reason I want to set up matrix on another server, all I have to do is change the domain name & host ip in the configuration file, then I just type out `morph deploy matrix.nix switch` and it should just work.

So the entire instance is managed from 1 config file?

Yep exactly, the entire server is defined with one file and then the system becomes immutable. Which really just means the only way to jack up your installation is to mess with said config file. It won't rebuild your system if there's any errors as well which is a bonus.

Is this just for servers?

It's mainly for servers but you can also use it on desktops. It's actually the only distro I use anymore, from my pi's to servers to desktop and laptop. All of em are on nixos now.

I once set up a Saltstack fleet and that worked on a similar principle.

Was great for managing many many machines.

https://docs.saltproject.io/en/latest/contents.html