Sharks are cool and comfortable!


Elden Thing | Back & Body Hurts Platinugggggh Rewards Member


Profile pic and banner credits: sharkaeopteryx art by @superkiak! eggbug by eggbug! Mash-up by me!
[Alt-text for pfp: a cute sharkaeopteryx sat on the ground with legs out, wings down, jaw ajar, and hed empty, looking at eggbug and eggbug's enigmatic smile.]
[Alt-text for banner: a Spirit Halloween banner with eggbug and the sharkaeopteryx that Superkiak drew for me looking at it with inscrutable expressions]


I'm a Vietnamese cis woman born and currently living in the U.S. You may know me from Sandwich, from Twitter or Mastodon (same username), or on Twitch as Sharkaeopteryx. I do not have a Discord or Bluesky account.

Ask me about language learning/teaching, cooking/eating food, late diagnosis ADHD, and volunteer small business mentoring. Or don't, I'm not the boss of you.


I think people deserve to be young, make mistakes, and grow without being held to standards they don't know about yet and are still learning. So, if you are under 22, please don't try to strike up a friendship or get involved in discussions on my posts.


Please don't automatically assume I follow/know/co-sign someone just because I reposted something from them—sometimes I do, sometimes I don't. Also, if you think being removed as a follower when we're not mutuals is a cardinal sin, please do not follow me.


🐘Mastodon
search for @sharksonaplane@mastodon.sandwich.net and hit follow if you want
Hang out with me on the Auldnoir forum! (you can DM there!)
discourse.auldnoir.org/
Follow me on Twitch
twitch.tv/sharkaeopteryx
Add my RSS feed (not working yet but I'll get to it!)
sharkaeopteryx.neocities.org/rss.xml

staff
@staff

hi there! we appreciate the candid feedback several folks have provided about the need for a darker dark mode, and we wanted to post sooner rather than later to tell everyone that we’re prioritizing some improvements on this front.

some details:

  • we don’t have an ETA for this yet, but expect a time frame of days rather than weeks.
  • rather than restyling the entire site for everyone, we’re adding an option to set a default color scheme specifically for posts and comments, as well as controls for individual posts so you can swap them between dark-on-light and light-on-dark if they were designed with a particular background in mind.
    • most of staff uses the existing dark mode, and for at least one of us, simply making a “darker dark mode” would make the site substantially harder to use; making posts dark-on-light in the first place was an intentional decision on our part.

we’ll post again once it’s live for everyone. until then, thanks as always for using cohost :eggbug:


kaara
@kaara

relatedly, i generally don't want to get in to discussions about disagreements people have about The Web Site, but i will briefly say two things!

  • no one really needs to defend staff
  • it does take us about a day or two to get all our ducks in a row when big waves of feedback come in. patience is appreciated!

You must log in to comment.

in reply to @staff's post:

i'll sure appreciate no longer having a discolored streak down the center of my display from the current dark mode causing ghosting on my panel, aha! thanks for sayin' something about it, for sure!

Oh, hey, that's a really cool implementation of it, seriously.

Also! You're really doing a good job at… …all of this, especially given the pressure of managing the PR end of things amidst also having limited coding labour to split up between your various longer-term projects with the site. You're doing a fantastic job, and I hope you can keep it up into the future. Not everyone could handle the kind of pressure you're having to contend with. ,,,

This seems cool. I think a very important thing that people were forgetting talking about it the last few days is how forcibly changing user-formatted styles in posts would like, mess with and even completely break a ton of creative stuff people are doing. I don't think that a dark mode should override all custom formatting anymore than I think light mode should. It's not just a matter of black or white text on black or white backgrounds.

That being said, at least 99% of posts would be simple enough to reformat for dark mode, so being able to swap it on individual posts is good for when it causes problems. I like formatting posts with light text on dark background (when I can be bothered to open up prechoster) and I would be 100% in favour of a button to cancel out all my formatting if it's an issue for somebody.

I guess I'm still worried that having to click a button to always fix a post could make custom post styles seem annoying? But that's like, largely a user and site culture issue.

I guess I think it would be cool if it was like

  1. dark/light mode only changes the default and if a user has done custom styling it won't override that
    1a) Perhaps an aggressive dark mode option to override that anyways, but that would be more moving parts

  2. An option on posts when you make them that's like "dark mode intended" or "light mode intended". That way if I write posts with like, navy-blue font and a default background, it won't just disappear in dark mode.

  3. A way to completely remove font colour and background colour AND background image formatting, which overrides #2. I can already think of ways that would break things though, like you'd probably also have to remove any text-shadow or things could get weird...

dark/light mode only changes the default and if a user has done custom styling it won't override that

this is actually a good point that we forgot to mention; if you're doing custom styling on your posts by specifically setting the color of an element (or applying a background image, or similar), that will be completely unaffected. this is specifically for the post header and footer, the read more link, the post background, and the default styles of text which isn't otherwise styled.

speaking as someome on mobile, dark mode doesnt really feel like dark mode. though with things like CSS crimes, i also figured it wouldnt be so simple to implement. simple or not though, it aint killing me, yall take it easy :eggbug:

Y'all know this and we are only retreading things that have already been said plenty of times before. but, i don't know. i want to put our feelings out there.

A few months ago we were going to write a post about all of the accessibility issues that have been (from the perspective of the users) ignored. We never got around to it because, we sincerely do understand how much work running the website is, developing it, communicating, dealing with life and disabilities. We didn't feel adding pressure would have contributed (we know y'all are constantly working to improve this place), especially with the very inflamed feelings we had at the time.

But, like. Ahm. We know the survival of the website is important. It's why getting tipping going is one of the top priorities. But accessibility really should be first and foremost, above all else. Like, ugh, we know there will always be a fire to put out. There will always be a bug, an issue that is causing trouble for a great deal of beings, a missing feature, some reputational fire to put out. And cohost is a project that's being built live. But. Uhm. We're not software developers, and we don't have any idea what cohost looks from the inside. But we feel it is super important to always develop with accessibility in mind, because it either becomes too hard later on or gets pushed away. And failing that, communicating better about it.

We don't know if this is bad business planning, because cohost is a business at the end of the day. It has to pay people's rents. But we rather a website that is buggy and doesn't grow, but at least is, like, physically accessible to everyone.

in reply to @kaara's post:

yeah, the way things went where it seemed like folks were pouring fluorinated gasoline on a fire in the name of defending y'alls honor was... possibly the most maddening thing about the past two days

i think that's a reasonable way to say that?

  1. thank you!
  2. I think a lot of frustration coming from people defending the dev perspective (or any side of it, really) is that this kind of intra-platform quasi-personal conflict around feature development is not a new thing or unique to this site and so it's not Just About This Thing. TBH lots of people just have bad experiences on one side of this or another so it makes it more likely that everybody has a bug up their butt about it (eggbug, get outta there..). one hopes cooler heads shall prevail and this is a step towards that!

Thank you for adding this! I do appreciate the work y'all do and I am glad to see that y'all're acknowledging the other issues that caused this to flare up.

It's a good sign that y'all are trying to do the right thing and it's one of the things that give me legitimate hope for this site even with the rough patches.