btw, i don't want to mod anything lol. Here's what's the general thought.
In an ideal world
Community members volunteer to moderate whatever, I was going to do a form type thing with LimeSurvey because it's a pretty good tool for an application process. That might be excessive tho, anyone can start a community and if one exists from the bot that was post scraping; make a post/comment in it that you want it and poof we'll get it done.
I want to maintain the infrastructure/script/automate, vape herbs, do dabs, wikifi Wiki things, and figured I'd post vape videos w/the GoPro 11 I picked up for eBike shit for fun too.
*actual eBike stuff I'm keeping separate. However, I am starting what will be a ~400 mile trip on the OTET in 30 days; and the farthest the bike i'm taking has been in a single ride so far was ~30 miles. I will be posting videos of me getting high along the way in here with that DeWalt rig and whatever else I stash in my cargo bike bags.
Authentik helps setup admin delegation with LDAP/SSO, so if someone wants to jump into some backend infra lmk and we'll setup something.
This place is for the community. The more people that help maintain this garden for the general good and the less influence I have over the "social" aspect of this, the better IMO.
My minimal guidelines would be
Be chill, this is a cannabis forum after all.
Post links, pics, vids talking about where your fav vape/bong/glass/pipe was from.
Don't sell anything consumable on here. No sales of herb, extract, carts, pens, edibles, drinks, tintcures, anything that's a consumable product.
DEVICES and ACCESSORIES like a Mighty, Tinymight, some custom glass for a Carta or PuffCo Peak, 510 Mods, log vapes, DIY/One off vapes/pipes/bags/stems/dab tools/Etsy type shit that Etsy bans. That stuff is fine. AT YOUR OWN RISK. And that needs it's own channel/community(communities) if people are interested in an exchange.
Provide citations/sources for posts/comments where needed.
Openly discuss safety of equipment/devices and cannabis products.
Be mindful of what you post on here. The point is to have the whole server indexed by Google and other search providers and keep the space alive/history documented/growing in the future. (AKA Share Knowledge / Share the vibes. / Don't get me arrested plz. )
I was messing with configuring the OAuth plugin for Discourse to open that up before doing redarc or the database server work for the Vaporents archives. The postgresql w/Lemmy and other dockers needs pointed outside of their containers too and it made sense to do as much of that DB work at one time as possible.
In the meantime (until there's moderators) lol, if there's an issue w/something email [email protected] or send myself or one of the couple mods we do have ( @[email protected], @Loki, and @[email protected] ) so far a DM here (or on another subdomain) and we'll help out.
Nah it was always Vaporents - Vaping with Cannabis @lemmy.beyondcombustion.net. Then when PHJ went to change it he made the double lemmy.beyondcombustion.net at first lol
I think a lot of times it doesnt display the @lemmy.beyondcombustion.net for accounts that were created on this server. Like you're just going to the local vaporents community, no need to specify the server. But for people from other servers, we always see the second part displayed so we know we are on another instance.
That's how it works for names at least, like when I'm on SJW I just see my fellow users by their name, but when we see each other on other servers it's [email protected]. Idk
It'll always show A from your view, but other people will only see the A if they are from your server, because otherwise you're not their admin. Likewise, people from your server won't see the @lemmy.beyondcombustion.net, but everybody else will.
Also my moderator status still hasn't updated on my side. Might take another 24 hours to federate/update I suppose, although I haven't had this issue before.
I think there might be some weirdness with the nginx proxy that's in front of the site, I'll see if I can figure that out today.
Since that last update it's been a bit off. Websockets were removed and at least one additional endpoint was added "/inbox".
The instance on this server ended up being behind a dual nginx reverse proxy by the time I got federation going, so it's a bit.... tricky when changes like that happen.