ChocoSune

Furry Fetish Artist & Streamer

(NSFW/πŸ”ž) Confectioner of Kinks. Art is at @AvecLeChocolat. Freelance furry artist.
I make fetish art and love engaging with others.
I post my art [ just about everywhere. ]

Be Horny, and do Kinks.

Above all, fuck fascists; but not in the fun way.


πŸ™Œ Support Me & My Work
support.the.choco.one/
🌐 Homepage & Other Sites
the.choco.one/
🎨 Art Account
cohost.org/AvecLeChocolat

kaara
@kaara

There's been a lot of discussion over the last day about dark mode, but those discussions led to discussions about feedback in general and cohost's relationship to feedback. Given that this is my job, I figure now is a reasonable time to clarify a few things.

Where does feedback go?

The best place to give us feedback is on our forum, located here. We use it as a repository and it is the first place we look when we are looking for something new to work on. If you post here, we'll see it.

That being said, feedback, by it's nature, can come from anywhere. Feedback does not need to come from the feedback region of Italy, that's just a marketing scam and urban myth. I've seen (vagueposting! woah!) some people say that if you're not posting in the feedback forum, you're doing it wrong. This is not necessarily true. If you post a about a feature request or bug on Cohost there's a chance we won't see it, especially if it's untagged. Just because we might not see it doesn't mean you can't still post about the things you want to see on Cohost! We have a good shot of seeing it too (tag it!)

Your page is your own. Post as you wish, and yearn for whatever weird type of eggbug you desire.

How to give feedback, aka, tone and tone policing

Ultimately, discussion over the last day turned into discourse about feedback and tone and I feel the need to squarely address it here. We deeply appreciate feedback that is kind and thoughtful. Not all feedback will be and that's okay.

You do not need to defend us. We appreciate it, but you really don't. This job is frustrating, but we're not going to fall over dead just because some people delivered their feedback in a mean way. It sucks and is pretty unproductive, but we'll get over it.

I'm not going to "take a side" here. You're more than welcome to have a discussion about us, defend us, be miffed at us, whatever. Not my place to say much more. But, please be cool with us and we'll be cool with you. If someone isn't cool to us you can let us worry about it. (Unless it rises to a point of breaking our rules, in which case, report it)

A significant amount of discussion over the last day came from a few users getting upset at us1 and other people getting mad at said people getting upset at us. It's a doom loop and is frankly pointless. I'd much rather have a few people upset at us (regardless of the "validity" of said upsetness) over an all out doom loop of vaguemetaposting and bizarrely placed pity.2

Getting in contact

Ultimately, communication is the name of the game here. If we don't see something you think we should see or you need a status update on something, please reach out. You can write a ticket to us at help.antisoftware.club and get our take any time. We'd prefer that you not send feature requests directly there (that's what the forum is for), but you're welcome to simply ask us questions. If you want to know if something is planned or not planned we can tell you. Our answers might be brief ("No, this is not planned", "Yes, this is planned but there is currently no ETA"), but we will usually have an answer.

We're an open bunch, don't be afraid to talk to us.

edit - just in case it wasn't abundantly clear: don't be fuckin jerks to us!


  1. a totally reasonable thing to be, albeit at times a personally frustrating experience! No one likes when people are upset at them!

  2. if you think we're getting our ass handed to us in a shitty or bad way, feel free to be nice to us yourself, give us some more money, or post a picture of your cat. Be nice to us as opposed to picking fights or trying to win over hearts and minds



So I finished Mario Wonder so I can watch the playthrough of one of the YTers I currently follow without ruining any of the surprises, and if I was a pro game dev I'd pay next to anything to get a running feed of their thought processes to try and understand how they're exploring the game and learning to play it.

I'm now all but convinced there's genuinely no accounting for game literacy in game design. Certain conveyances in the game that I thought were so obvious as to be literally elementary soared so far over their head they went into fucking orbit. They don't tend to act out to the camera, very scarcely interact with chat, and seemed to be very focused on enjoying the game; so I genuinely don't think it was the "streamer effect" at play.

And I don't mean to make myself sound like I'm saying I'm better than a speedrunner (they used to do that back in the day); there's likely going to be a lot of stuff they'll figure out automatically that I struggled with myself.

While looking up information about Yoshis' and Nabbit's mechanics, I found two articles that concerned me: one that explained the mechanics but failed to do so in any sort of detail I was hoping for, and another that complained about Yoshi not being allowed to pick up powerups and how this "denied them an integral part of the experience" because they weren't made aware of it until several levels in - when the character selection screen has a warning plastered across it that explicitly says as much. The YTer I watch made the exact same mistake, multiple times.

It's just so fascinating and a little frustrating how, at least in practice, nothing can be assumed to be "obvious" in games - even if and when it's written in plain language front and center.



mutant
@mutant

It's been a while since I introduced this project!

Mutant Standard is an emoji set that aims to combine familiar, standardised symbols with completely new non-standard ones, aimed at helping particular groups of people (queers and furries in particular) communicate themselves more authentically.

In a similar way to a language, the standard set of symbols that we think of 'emoji' (the emoji keyboards on our devices) are not universal - it's a particular way of seeing the world. Unlike a language, the standards that set what emoji we see in most situations are made by a particular organisation called the Unicode Consortium.

In order to have an emoji in this system, you have to basically petition Unicode to include it in next year's slate of emoji updates. There are both understandable technical reasons why this system exists, but also cultural downsides, namely - you have to ask this consortium, comprised of billion dollar American tech companies, to consider including your thing.

Mutant Standard emerged in 2017 as a project to make emoji that had things I wanted to express myself, and the more I thought about emoji and why I was doing this, the more I thought it would be cool to try to make things that other people would like too. Things that challenge the norms around what emoji are and how we should see them, and coming up with possible new emoji standards.

Mutant Standard (like emoji itself, really) is a work in progress. There's currently more than 1000 unique designs in the project so far, along with some accompanying technical standards. The emoji set is free to use within the CC BY-NC-SA license. You can check it all out (and see all the symbols so far) at https://mutant.tech.


twilight-sparkle
@twilight-sparkle
This page's posts are visible only to users who are logged in.

ChocoSune
@ChocoSune

This is super cool and I love the fact that they made an Aoyama emoji too



So I've been tinkering with my brand new Nuphy keyboard (Air V2) and while putting the reprogramming feature to use, I ran into some oddities...

You can reprogram it exclusively while on a wired connection which is y'know, fair enough, but it only seems to like it when you connect it to the C port. I should note that it came boxed with an A-C cable.

I did it, got the reprogramming done, seems like no worries there. Went to use the shortcut keys again today and they just didn't work?

What I did was remap my volume keys to F22, F23 and F24, because the way my sound drivers and Windows' default media controls interface interact causes some stupid unwanted behaviour. So I remapped the hotkeys and they worked just fine during testing, but not now.

I switched to Bluetooth and they worked fine. Used C-C and they worked fine.

Turns out that their own proprietary 2.4G receiver drops those specific inputs for some reason. Likely anything in the F13 range and up, but I haven't tested that yet. Not sure what other nonstandard keys it drops yet.

So I decided to email them about it cause neither of these behaviours seem normal to me.

While writing out my message, I figured I'd do some further testing - be a bit more thorough, give as much detail as I can, you know - so I tried using a different A port, on the other side of my laptop, which is adjacent to a hub I use for all my peripherals right? They all suddenly disconnect, and the hub's LED starts flickering.

I pull it out and decide to dust off the voltage tester my dad gifted me years ago.

The damn thing is drawing

5V and 0.6A from the C port. Nbd.

5V and 1A from the A port. Pretty spicy, especially since I figure it isn't going any higher only because my laptop's limiting it.

Charging it off of my desk squid at the same time as using it wirelessly still only ever maxes out at 0.7A.

A friend suggested I try flipping the cable at the C port of the keyboard, and when I tried that the keyboard's backlight LEDs came on, but had no functionality.

And now I'm typing with it hooked up to the C port, so I know the keyboard port isn't completely busted. It might be busted in some voodoo magic sort of way, but it works.

See what I deal with πŸ™‚

See why I get mad πŸ™ƒ


Update: In case SEO brought you here and you're having the same issue: tech support got back to me and rightly suggested that I update the firmware using the guide on their website. It fixed the connectivity issue but not the F keys. After further testing, F13-F20 work fine and probably always did. F21-F24 are off limits for some reason.


Β