jkap

CEO of posting

butch jewish dyke
part of @staff, cohost user #1
married to @kadybat

This user can say it
osu stats


🐘 mastodon
xoxo.zone/@jkap
🖼️ icon credit
twitter.com/osmoru
🐦 twitter
not anymore lol

staff
@staff

happy thursday! we’ve been shaky on patch notes lately but hey better late than never.

unfortunately the ongoing Issues that have afflicted the team (of the health variety) persist, so some things are still in progress. we’re still plugging away on some things we think y’all are gonna like.

here’s what’s new:

  • You can now paste images directly into posts!
    • This was the top requested feature on the support forums.
    • We hadn’t done this yet because, in the past, operating systems and browsers would frequently re-encode images, creating muuuuch larger than necessary files that were almost always over our limits.
    • This happens less frequently now but still can occur. If you get a file size error when pasting in an image, you should re-encode it to something smaller. We like Squoosh for this sort of thing.
  • First part of a new eggbug emoji set designed by @dzuk!
    • :eggbug:
    • New Eggbug now lives at :eggbug:, old eggbug is at :eggbug-classic:
    • the rest of the set will be available to cohost plus! subscribers soon!
  • Numbers™️
    • you know ‘em, you love ‘em
    • we also open sourced the Algorithm if you want to learn more about how it worked
  • Added support for iMessage’s new and improved OpenGraph previews

  • Fixed a bug where adding content to a share that didn’t previously have any would create an Invisible Post
    • This was caused by a limitation of how we store shares for performance.
    • We fixed this by fixing a different bug that allowed you to edit those posts (you weren’t ever supposed to be able to! whoops!)
    • If you want to add content to a share, share it again. We know this isn’t ideal and we may revisit in the future.
  • Fixed (we think) some issues where certain page loads would take unreasonably long
    • This appeared to be a weird issue around how Fastly handles connection pooling, which we’ve resolved by fucking with settings.
    • Requests were taking a normal amount of time to resolve on our end, but were taking a long time to even get to us.
    • We’re pretty sure this is fixed but it’s hard to know for sure; all we know is that we haven’t seen it in a while.

2fa should be landing tomorrow or monday. The actual product work is Done, but there’s a lot of testing to wrap up with it. We’ll post once it’s live for everyone to use!

That’s all for this week! Thanks, as always, for using cohost! :eggbug:


You must log in to comment.

in reply to @staff's post:

thanks for making cohost!!! :eggbug: i definitely noticed some connection issues since the fastly switch but i could not say if they've continued lately! so maybe that's another satisfied customer! :yeah: (i am satisfied either way tbh)

We hadn’t done this yet because, in the past, operating systems and browsers would frequently re-encode images, creating muuuuch larger than necessary files that were almost always over our limits.

Does this mean that Cohost explicitly doesn't recompress or encode images we upload? I'm assuming EXIF metadata is stripped?

They used to not do this, but now they make low-quality previews until you actually click on the post. To be honest, I'm not a big fan of that change myself (as someone with a HiDPI screen) and would have appreciated a setting to turn it off, but we get what we get I suppose.

yes, we strip EXIF metadata, but there is an implicit contract that we otherwise don't fuck with images to avoid some of the worst/most annoying aspects of uploading art to twitter, mastodon, tumblr, etc.

You can now paste images directly into posts!

awesome! does this mean the "save a draft with an image(s) attached and then link it from the actual published post" workaround is no longer needed? and if so does that mean i can delete the drafts that only exist to hold images in older posts?