JackDotJS

3D Artist | Programmer


 

✨ welcome to my loser lounge ✨

 

im jack, and sometimes i say words (very unfortunate). i also make stuff that isn't words, like 3d art or other creative projects. you can check that out with this super duper epic and cool tag:

 

#stuff i made

 

thanks for visiting :)

 


 

find me elsewhere! https://jackdotjs.github.io/

 



i've been thinking about content safety on cohost lately. it's really great that we have 18+ warnings, CWs and a full tag system, all completely free to use all at once in each and every post we make here. but for it to become truly effective, i think there's a number of things that could be added to make everyone's lives hell of a lot easier.

post content filters

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000183717

let's face it: people are gonna be lazy or ignorant and just post stuff without thinking once about CWs or tags. as good as these existing filter systems are, they only work if the author (and only the author) has the decency to go out of their way to mark up their posts. this is where content filters come in: the last barrier of defense.

the idea is simple: it just checks to see if the word or phrase in your content filters list matches anything in a given post. if it does, muffle/silence accordingly.

obviously words aren't great for filtering since they can often be taken completely out of context, which is why this should really be a last resort option. i might suggest allowing regex as opposed to plain ol strings to help things a bit in this area, in addition to encouraging users to use muffling instead of outright silencing for this type of filter.

CW word/phrase suggestions

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000185802

when adding a content warning, these already function similarly to tags with one exception: there are no suggestions provided, which is honestly really strange since it already brings up an empty suggestion dialog. giving people suggestions in this area would help a lot with CW filtering, because otherwise there is bound to be 40+ variations of the same word you have to whitelist/blacklist.

that said, tags have a similar issue (albiet to a lesser extent), which is why i'd also love to see...

crowdsourced tag/CW aliases

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000183564

this is a pretty big one, but hear me out. i truly believe tag aliases are one of the biggest things that will drastically improve content safety on this website. not only could it make tagging posts much easier (not having to worry about duplicate/variant tags), but filtering will also become far less of a hassle at the same time.

furthermore, we could include related tags, which could also be suggested when tagging a post. for instance, say i add "#tardis" to a post. not only would i no longer have to worry about variants of what is basically the same tag (such as "#the tardis"), i could also be shown suggestions for things like "#doctor who" or "#science fiction".

personal tag/CW templates

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000183481

unfortunately, copying/pasting multiple tags just doesn't work at all. this is either a bug or a simple design flaw in the current version of cohost's tag editor, but alas. i'd propose allowing multiple tags to be pasted, which would absolutely be a welcome change, but i might have an even better idea to go alongside that.

i'm suggesting a built-in tag template system, which simply saves a list of bundled tags which you can reuse as many times as desired for any post you make or edit. you can create and edit tag bundles at any time, and even name them for easier searching later. most of all, these could be tied to your account (or better yet, per-page). all of which would help save tons of time for people making multiple posts about the same topic, or even pages dedicated to a specific type of content.

per-page CW/tag/content filters

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000185803

having filters apply account-wide is alright (and perfectly valid for 99% of situations), but having additional filters that only apply per-page would be a tremendous improvement imo, especially for those with separate SFW and NSFW pages. keyword being "additional", because obviously account-wide filters really should not be replaced.

per-page 18+ toggle

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000183090

this is already a fairly popular request, but it fits with the theme of this post, and personally, i believe it's one of the big things stopping cohost from being the absolute best place for adult content creators.

option to disable 18+ click-through on text-only posts

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000183965

in the same vein of "improving adult content on cohost", i think having the option to disable the 18+ warning on text posts would be a very welcome change. i personally do not care at all if i come across some smut fanfic while scrolling, it's really just the images i worry about.

automatically remove leading hashtag in tags

suggestion forum post: https://help.antisoftware.club/support/discussions/topics/62000185103

small nitpick, but this is something i see fairly often and it's borderline infuriating to see. not only is this somewhat invalidating tag filters, but it also means that particular post can't get visibility from people searching for the correct tag. in theory, this is something that can be fixed with the crowdsourced aliasing idea from earlier, but why not also fix these types of issues at the source?

i realize this idea could break very specific tags, so at the very least it should just warn the user.

that's about it i guess

still love this website compared to the other options, but it can be even better. hoping some of these changes can come around one day. lmk what you guys think C:


You must log in to comment.