Hey, you, who's reading this in the future: you can find out who I am today at https://rarf.zone/about/. 💙


E-mail me at:
info@rarf.zone
Mastodon/Fediverse
yiff.life/@katja

staff
@staff

happy wednesday / february!

financial update will be a bit late this month; we’re 99% done with this funding round, but want to be 100% before we publish the new numbers. also jae has been largely out sick all week and they’re the one who writes those.

here’s what’s new:

  • changed tag search behavior somewhat
    • we’re now searching the middle of the tag name as well, as opposed to just starting from the beginning.
    • this impacts the search page as well as tag autocomplete in the post editor
  • changed how we’re organizing our pending work internally
    • especially after twitter started imploding, we fell into some bad ad-hoc work habits while we were in putting-out-fires mode. we’re breaking out of them so that our 100%-ADHD-having company can remember what the fuck we’re doing from day to day.
  • fixed a bug where we weren’t escaping SQL wildcard characters in tag and user search
    • “un-escaped SQL” sounds scary, but in this case there were only performance implications, no security concerns.
  • fixed a bug where the notifications page could occasionally fail to load if a deleted page would have been in a grouped notification.
  • fixed a bug where we couldn’t delete accounts that had been banned or put in time-out

coming up, we’re still working on mostly the same things — colin and aidan are starting to work on the two-factor authentication UI, and jess is finishing up cleaning up our relationships1 API that had to be done before working on silencing posts proper — but here’s some bonus items:

  • jae’s working on performance improvements for how we display posts
    • they finally caught their performance white whale: render caching
    • a fun side-effect is that, once we’ve launched out public API, this will provide a more consistent way for third-party developers to display posts

that’s all for this week, thanks for using cohost! :eggbug:


  1. follows, silences, likes, and “being an editor of a project” are all routed through this; it’s complicated, important to not mess up, and truly ancient by the standards of our code, so it took a while.


You must log in to comment.

in reply to @staff's post:

when will community guidelines be updated? there are a lot of nsfw artists who are unsure of whether or not they will be able to share their art on this site and for those who do if their art will be taken down. it does not look good for a lot of us that the only changes made came from pressure by the community especially when they were as hostile about it as they were.

i understand this is a big undertaking and while i appreciate what you all have done for the nsfw art community as a whole, the fact that this has not been mentioned in two months does not make cohost feel like a safe space for a lot of users who are being squeezed out of the same internet spaces everyone else is. we would appreciate it if you made this a priority.

Interesting!

At the very least, I think communication should at least be properly established. There's the bug tracker but besides that, idk. Keeping in mind that assc is a 4 person team now, I'm sure they have a lot on their plate. They might get to this soon, they might not.

I hope that when they do, it is with research and well-rounded opinions. I hope the nsfw community gets the safe spaces they deserve (the good apples tho), good community guidelines are established, and most people are happy.

as a web developer, community guidelines should always be a priority when designing a social media platform, both for moderation purposes but also so the users know how to use the site. i understand that they are short staffed but to be perfectly honest this should have been handled long before someone pointed out it's been two months since it was last mentioned.