home.social

Search

372 results for “casraf”

  1. Still working on a MUD client also btw, Android & macOS work great, might push some alpha version soon :)

  2. Migrating the app away from GetX 😭 🤢 gonna be a pain, but so worth it, can't wait to get rid of this junk

  3. Signing git commits with SSH signatures

  4. Man, this took way longer than I expected... but totally worth it! I have collision detection :) with map chunking and everything...

    And, I also used pointers - intentionally and with understanding, mind you - for the first time. Hooray!

  5. is awesome. Could use some better UI/UX though :) dare I...?

  6. Living in this new house is dope. This is how I spend my break to think about how to solve some coding problems at work. Does it get any better? Entirely silent other than the birds.

  7. Initial pre-release of AutoCurrency for and , runs a cron once a day to update the currency exchange rates in all your Cospend projects.

    github.com/chenasraf/nextcloud

  8. Auto Currency fetcher for Cospend: WIP but POC is working :) now just to get some settings UI up in this bitch...

  9. and users, is anyone familiar with a package that fills your project's currency rate conversions for you daily?
    If not, maybe I'll try making one?

  10. Cospend really needs an automated currency converter. It's really easy to get the current currency rate and use it with the existing currency support inside Cospend without needing to modify the data structure. Just run a cron once a day and fill all projects with all (wanted) currency info.

    Is this already a thing?

  11. @Pino Carafa Well, my problem is not the alt-text.

    I used to limit my alt-texts to 1,500 characters because Mastodon and its forks truncate longer alt-texts at the 1,500-character mark. In the future, I will limit them to 512 characters because Misskey and its forks should truncate them at that mark if they're longer, but instead, they delete them.

    But in addition to my alt-texts, I describe my original images once more (= twice altogether). The other description is what I call the "long description", and it goes directly into the post text (as opposed to the alt-text). I don't have a character limit to worry about (over 16.7 million), so I can do what's outright unimaginable from a Mastodon point of view.

    It's this long description that's causing trouble.

    That is, I wouldn't wonder if the Mastodon HOA were to sanction me for my alt-text not being detailed enough when I limit it to 512 characters. In fact, I wouldn't wonder if they were to sanction me because a 1,500-character alt-text of mine is lacking important elements (descriptions of certain details, transcripts of all text within the borders of the image etc.).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  12. @Pino Carafa Well, my problem is not the alt-text.

    I used to limit my alt-texts to 1,500 characters because Mastodon and its forks truncate longer alt-texts at the 1,500-character mark. In the future, I will limit them to 512 characters because Misskey and its forks should truncate them at that mark if they're longer, but instead, they delete them.

    But in addition to my alt-texts, I describe my original images once more (= twice altogether). The other description is what I call the "long description", and it goes directly into the post text (as opposed to the alt-text). I don't have a character limit to worry about (over 16.7 million), so I can do what's outright unimaginable from a Mastodon point of view.

    It's this long description that's causing trouble.

    That is, I wouldn't wonder if the Mastodon HOA were to sanction me for my alt-text not being detailed enough when I limit it to 512 characters. In fact, I wouldn't wonder if they were to sanction me because a 1,500-character alt-text of mine is lacking important elements (descriptions of certain details, transcripts of all text within the borders of the image etc.).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  13. @Pino Carafa Well, my problem is not the alt-text.

    I used to limit my alt-texts to 1,500 characters because Mastodon and its forks truncate longer alt-texts at the 1,500-character mark. In the future, I will limit them to 512 characters because Misskey and its forks should truncate them at that mark if they're longer, but instead, they delete them.

    But in addition to my alt-texts, I describe my original images once more (= twice altogether). The other description is what I call the "long description", and it goes directly into the post text (as opposed to the alt-text). I don't have a character limit to worry about (over 16.7 million), so I can do what's outright unimaginable from a Mastodon point of view.

    It's this long description that's causing trouble.

    That is, I wouldn't wonder if the Mastodon HOA were to sanction me for my alt-text not being detailed enough when I limit it to 512 characters. In fact, I wouldn't wonder if they were to sanction me because a 1,500-character alt-text of mine is lacking important elements (descriptions of certain details, transcripts of all text within the borders of the image etc.).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  14. @Pino Carafa Well, my problem is not the alt-text.

    I used to limit my alt-texts to 1,500 characters because Mastodon and its forks truncate longer alt-texts at the 1,500-character mark. In the future, I will limit them to 512 characters because Misskey and its forks should truncate them at that mark if they're longer, but instead, they delete them.

    But in addition to my alt-texts, I describe my original images once more (= twice altogether). The other description is what I call the "long description", and it goes directly into the post text (as opposed to the alt-text). I don't have a character limit to worry about (over 16.7 million), so I can do what's outright unimaginable from a Mastodon point of view.

    It's this long description that's causing trouble.

    That is, I wouldn't wonder if the Mastodon HOA were to sanction me for my alt-text not being detailed enough when I limit it to 512 characters. In fact, I wouldn't wonder if they were to sanction me because a 1,500-character alt-text of mine is lacking important elements (descriptions of certain details, transcripts of all text within the borders of the image etc.).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  15. @Pino Carafa An additional advantage of this would be that I could first ask just how detailed a description they need. Like, if they really want me to spend two full days, morning to evening, to write something that'll take their screen reader three hours to read out loud.

    The problem, however, is that the virtual worlds that I frequent change a lot. Everything is built by users. A place that I've shown in an image may change mere days or hours after I've been there, so when I go back to take a closer look for a detailed description, it doesn't look like on the image anymore.

    Or that place may be gone entirely. For example, I could post some images from an in-world event, from places specifically built for this event. Then, two months later, someone asks for a more detailed description. But I can't write a more detailed description because I can't go back to these places, simply because these places were closed and shut down a few days after I had posted the images.

    Lastly, my impression of Mastodon is still that a significant number of users do not want to ask. Whatever information they may need, they expect it all to come with the post immediately. Having to ask for a detail description or for an explanation appears to be about as bad style as having to ask for a description in the first place.

    I've literally seen Mastodon toots in which people say that if they don't understand a post or an image in a post, they want an explanation to come with the post.

    I've also seen a Mastodon toot in which someone said that it isn't sufficient to just say what's in an image, but you also have to describe what it looks like. Right away. And in my case, this is actually absolutely justified.

    It's a catch-22: If I don't describe my images sufficiently, I risk being sanctioned by the Mastodon HOA for not describing my images sufficiently. But if I do, I risk being sanctioned by the Mastodon HOA for exceeding 500 characters in one post.

    Oh, and if I chop my image descriptions into tiny chunks of no more than 500 characters, it's disturbing for my own ilk, the users of Friendica, Hubzilla, (streams) and Forte, who are used to not having any character limits and everything being in one message, no matter how long it is. Besides, how many Mastodon users are willing to read a thread of 120 or more posts and find that more convenient than one post with 60,000 characters?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  16. @Pino Carafa An additional advantage of this would be that I could first ask just how detailed a description they need. Like, if they really want me to spend two full days, morning to evening, to write something that'll take their screen reader three hours to read out loud.

    The problem, however, is that the virtual worlds that I frequent change a lot. Everything is built by users. A place that I've shown in an image may change mere days or hours after I've been there, so when I go back to take a closer look for a detailed description, it doesn't look like on the image anymore.

    Or that place may be gone entirely. For example, I could post some images from an in-world event, from places specifically built for this event. Then, two months later, someone asks for a more detailed description. But I can't write a more detailed description because I can't go back to these places, simply because these places were closed and shut down a few days after I had posted the images.

    Lastly, my impression of Mastodon is still that a significant number of users do not want to ask. Whatever information they may need, they expect it all to come with the post immediately. Having to ask for a detail description or for an explanation appears to be about as bad style as having to ask for a description in the first place.

    I've literally seen Mastodon toots in which people say that if they don't understand a post or an image in a post, they want an explanation to come with the post.

    I've also seen a Mastodon toot in which someone said that it isn't sufficient to just say what's in an image, but you also have to describe what it looks like. Right away. And in my case, this is actually absolutely justified.

    It's a catch-22: If I don't describe my images sufficiently, I risk being sanctioned by the Mastodon HOA for not describing my images sufficiently. But if I do, I risk being sanctioned by the Mastodon HOA for exceeding 500 characters in one post.

    Oh, and if I chop my image descriptions into tiny chunks of no more than 500 characters, it's disturbing for my own ilk, the users of Friendica, Hubzilla, (streams) and Forte, who are used to not having any character limits and everything being in one message, no matter how long it is. Besides, how many Mastodon users are willing to read a thread of 120 or more posts and find that more convenient than one post with 60,000 characters?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  17. @Pino Carafa An additional advantage of this would be that I could first ask just how detailed a description they need. Like, if they really want me to spend two full days, morning to evening, to write something that'll take their screen reader three hours to read out loud.

    The problem, however, is that the virtual worlds that I frequent change a lot. Everything is built by users. A place that I've shown in an image may change mere days or hours after I've been there, so when I go back to take a closer look for a detailed description, it doesn't look like on the image anymore.

    Or that place may be gone entirely. For example, I could post some images from an in-world event, from places specifically built for this event. Then, two months later, someone asks for a more detailed description. But I can't write a more detailed description because I can't go back to these places, simply because these places were closed and shut down a few days after I had posted the images.

    Lastly, my impression of Mastodon is still that a significant number of users do not want to ask. Whatever information they may need, they expect it all to come with the post immediately. Having to ask for a detail description or for an explanation appears to be about as bad style as having to ask for a description in the first place.

    I've literally seen Mastodon toots in which people say that if they don't understand a post or an image in a post, they want an explanation to come with the post.

    I've also seen a Mastodon toot in which someone said that it isn't sufficient to just say what's in an image, but you also have to describe what it looks like. Right away. And in my case, this is actually absolutely justified.

    It's a catch-22: If I don't describe my images sufficiently, I risk being sanctioned by the Mastodon HOA for not describing my images sufficiently. But if I do, I risk being sanctioned by the Mastodon HOA for exceeding 500 characters in one post.

    Oh, and if I chop my image descriptions into tiny chunks of no more than 500 characters, it's disturbing for my own ilk, the users of Friendica, Hubzilla, (streams) and Forte, who are used to not having any character limits and everything being in one message, no matter how long it is. Besides, how many Mastodon users are willing to read a thread of 120 or more posts and find that more convenient than one post with 60,000 characters?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  18. @Pino Carafa An additional advantage of this would be that I could first ask just how detailed a description they need. Like, if they really want me to spend two full days, morning to evening, to write something that'll take their screen reader three hours to read out loud.

    The problem, however, is that the virtual worlds that I frequent change a lot. Everything is built by users. A place that I've shown in an image may change mere days or hours after I've been there, so when I go back to take a closer look for a detailed description, it doesn't look like on the image anymore.

    Or that place may be gone entirely. For example, I could post some images from an in-world event, from places specifically built for this event. Then, two months later, someone asks for a more detailed description. But I can't write a more detailed description because I can't go back to these places, simply because these places were closed and shut down a few days after I had posted the images.

    Lastly, my impression of Mastodon is still that a significant number of users do not want to ask. Whatever information they may need, they expect it all to come with the post immediately. Having to ask for a detail description or for an explanation appears to be about as bad style as having to ask for a description in the first place.

    I've literally seen Mastodon toots in which people say that if they don't understand a post or an image in a post, they want an explanation to come with the post.

    I've also seen a Mastodon toot in which someone said that it isn't sufficient to just say what's in an image, but you also have to describe what it looks like. Right away. And in my case, this is actually absolutely justified.

    It's a catch-22: If I don't describe my images sufficiently, I risk being sanctioned by the Mastodon HOA for not describing my images sufficiently. But if I do, I risk being sanctioned by the Mastodon HOA for exceeding 500 characters in one post.

    Oh, and if I chop my image descriptions into tiny chunks of no more than 500 characters, it's disturbing for my own ilk, the users of Friendica, Hubzilla, (streams) and Forte, who are used to not having any character limits and everything being in one message, no matter how long it is. Besides, how many Mastodon users are willing to read a thread of 120 or more posts and find that more convenient than one post with 60,000 characters?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  19. @Pino Carafa @ᴮᵉⁿ ᴿᵒʸᶜᵉVOTE IN THE PRIMARIES @🅰🅻🅸🅲🅴  (🌈🦄) It does depend on the image, yes.

    Most of the images in the Fediverse that aren't just text are real-life photographs. Real life is something that people know, that people are familiar with. For one, it isn't that exciting, and besides, even blind folks have at least got a rough idea about what stuff looks like.

    When I post memes, my visual descriptions are limited to what's important in the context, and I only write one visual description per image which goes into the alt-text. However, I do add a full explanation in the post text because it appears to me like a sizeable amout of Mastodon users expect explanations for things they don't understand to be delivered to them immediately without them having to ask.

    But my original images aren't real-life photos. They aren't screencaps from anything familiar either. They're renderings from extremely obscure 3-D virtual worlds.

    On the one hand, I can't expect anyone to have an idea of what anything in my images looks like. If anyone sighted doubts this, I ask them to check what an avatar in Meta Horizon looks like, what an avatar in Roblox looks like and what a modern avatar in Second Life looks like (Flickr and Primfeed are good sources for the latter).

    On the other hand, people may be super curious about these worlds beyond what matters in the context of a post, even or especially if they aren't fully sighted. Or the post itself is about the image, as in about the whole image as opposed to something specific in the image.

    This means that I have to describe the entire image with every detail in it. And I don't describe the image by looking at the image with its limited resolution. I describe it by looking at the real thing, in-world, where the resolution is near-infinite.

    My sighted audience sees a little white square with six pixels in a row that are ever so slightly less bright. They may not even notice it. I see a sign with two lines of text on it, I describe it all the way to the typeface, and I transcribe the text verbatim. This is how I sometimes end up with over 20 individual bits of text in one image that need to be transcribed.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
  20. A Cat-Ear's Journal: Konbini Idol Side Stories
    Chapter 85.1 Released

    Belling the Tsundere ツンデレに鈴を付ける勇気

    #Wss366 12/15 #PIXIVCharitySanta

    •───⋅☾Kan-chan POV☽⋅───•

    "Kanpai," Kao said, raising her glass. I could hardly hear her over the boisterous noise in the izakaya. The din still reached us even though we'd arrived before the after-work crowd and gotten a screened-in booth. Maybe I should have picked a less popular place, but they stock my favorite drink, top-shelf Satsuma imojōchū.

    I waved for more shochu—we'd gone through the first carafe quickly, so I'd gotten another. I planned to get plastered.

    "Slow down. They won't run out.”

    I didn't respond, but instead poured myself a drink and took it in one swallow.

    "Why pay for good imojōchū if you're just going to guzzle it?"

    I shrugged and poured another.

    Kao reached out, put his hand on mine, and stopped me. "Okay, tell me what's wrong."

    “Nothing.”

    “Don’t give me that. As your sister and co-wife, I demand that you tell me.

    "No."

    "Okay, as your friend, I’m asking.”

    I looked at Kao, trying to stare her down. It was none of her business, but my vision blurred, and a tear trickled down my cheek. "I haven't heard from Tomo. It's almost Christmas… I wanted… together.”

    She let go of my hand, but the glass stayed where it was. I waited.

    "Yep, you've got it bad, don't you?"

    She poured herself a drink, but left it sitting. Then she resumed, "He’s a tsundere; you’re going to have to ask him.”

    "I can't."

    "You asked Shiro, and she was a stranger."

    Kao topped off our drinks, then proceeded to take out her phone. "He's probably busy fixing that old house they inherited and training to keep their kami happy. You’re going to have to bell the cat, or should I say the tsundere.”

    She dialed his number, handed me the phone, and then knocked back her drink. "Ganbatte!"

    I put the phone to my ear and heard it ring. Then, Tomo’s voice said, "Moshi, moshi."

    I swallowed. "Christmas?" I swallowed again. "Are you free?"

    Tags: #KonbiniIdol #Yuri #Polyamory #LGBTQ #Romance #LGBTQIA #Queer #SappficRomance #SapphicBooks #QueerRomance #Tsundere #NMFic

  21. A Cat-Ear's Journal: Konbini Idol Side Stories
    Chapter 85.1 Released

    Belling the Tsundere ツンデレに鈴を付ける勇気

    #Wss366 12/15 #PIXIVCharitySanta

    •───⋅☾Kan-chan POV☽⋅───•

    "Kanpai," Kao said, raising her glass. I could hardly hear her over the boisterous noise in the izakaya. The din still reached us even though we'd arrived before the after-work crowd and gotten a screened-in booth. Maybe I should have picked a less popular place, but they stock my favorite drink, top-shelf Satsuma imojōchū.

    I waved for more shochu—we'd gone through the first carafe quickly, so I'd gotten another. I planned to get plastered.

    "Slow down. They won't run out.”

    I didn't respond, but instead poured myself a drink and took it in one swallow.

    "Why pay for good imojōchū if you're just going to guzzle it?"

    I shrugged and poured another.

    Kao reached out, put his hand on mine, and stopped me. "Okay, tell me what's wrong."

    “Nothing.”

    “Don’t give me that. As your sister and co-wife, I demand that you tell me.

    "No."

    "Okay, as your friend, I’m asking.”

    I looked at Kao, trying to stare her down. It was none of her business, but my vision blurred, and a tear trickled down my cheek. "I haven't heard from Tomo. It's almost Christmas… I wanted… together.”

    She let go of my hand, but the glass stayed where it was. I waited.

    "Yep, you've got it bad, don't you?"

    She poured herself a drink, but left it sitting. Then she resumed, "He’s a tsundere; you’re going to have to ask him.”

    "I can't."

    "You asked Shiro, and she was a stranger."

    Kao topped off our drinks, then proceeded to take out her phone. "He's probably busy fixing that old house they inherited and training to keep their kami happy. You’re going to have to bell the cat, or should I say the tsundere.”

    She dialed his number, handed me the phone, and then knocked back her drink. "Ganbatte!"

    I put the phone to my ear and heard it ring. Then, Tomo’s voice said, "Moshi, moshi."

    I swallowed. "Christmas?" I swallowed again. "Are you free?"

    Tags: #KonbiniIdol #Yuri #Polyamory #LGBTQ #Romance #LGBTQIA #Queer #SappficRomance #SapphicBooks #QueerRomance #Tsundere #NMFic

  22. A Cat-Ear's Journal: Konbini Idol Side Stories
    Chapter 85.1 Released

    Belling the Tsundere ツンデレに鈴を付ける勇気

    #Wss366 12/15 #PIXIVCharitySanta

    •───⋅☾Kan-chan POV☽⋅───•

    "Kanpai," Kao said, raising her glass. I could hardly hear her over the boisterous noise in the izakaya. The din still reached us even though we'd arrived before the after-work crowd and gotten a screened-in booth. Maybe I should have picked a less popular place, but they stock my favorite drink, top-shelf Satsuma imojōchū.

    I waved for more shochu—we'd gone through the first carafe quickly, so I'd gotten another. I planned to get plastered.

    "Slow down. They won't run out.”

    I didn't respond, but instead poured myself a drink and took it in one swallow.

    "Why pay for good imojōchū if you're just going to guzzle it?"

    I shrugged and poured another.

    Kao reached out, put his hand on mine, and stopped me. "Okay, tell me what's wrong."

    “Nothing.”

    “Don’t give me that. As your sister and co-wife, I demand that you tell me.

    "No."

    "Okay, as your friend, I’m asking.”

    I looked at Kao, trying to stare her down. It was none of her business, but my vision blurred, and a tear trickled down my cheek. "I haven't heard from Tomo. It's almost Christmas… I wanted… together.”

    She let go of my hand, but the glass stayed where it was. I waited.

    "Yep, you've got it bad, don't you?"

    She poured herself a drink, but left it sitting. Then she resumed, "He’s a tsundere; you’re going to have to ask him.”

    "I can't."

    "You asked Shiro, and she was a stranger."

    Kao topped off our drinks, then proceeded to take out her phone. "He's probably busy fixing that old house they inherited and training to keep their kami happy. You’re going to have to bell the cat, or should I say the tsundere.”

    She dialed his number, handed me the phone, and then knocked back her drink. "Ganbatte!"

    I put the phone to my ear and heard it ring. Then, Tomo’s voice said, "Moshi, moshi."

    I swallowed. "Christmas?" I swallowed again. "Are you free?"

    Tags: #KonbiniIdol #Yuri #Polyamory #LGBTQ #Romance #LGBTQIA #Queer #SappficRomance #SapphicBooks #QueerRomance #Tsundere #NMFic

  23. A Cat-Ear's Journal: Konbini Idol Side Stories
    Chapter 85.1 Released

    Belling the Tsundere ツンデレに鈴を付ける勇気

    #Wss366 12/15 #PIXIVCharitySanta

    •───⋅☾Kan-chan POV☽⋅───•

    "Kanpai," Kao said, raising her glass. I could hardly hear her over the boisterous noise in the izakaya. The din still reached us even though we'd arrived before the after-work crowd and gotten a screened-in booth. Maybe I should have picked a less popular place, but they stock my favorite drink, top-shelf Satsuma imojōchū.

    I waved for more shochu—we'd gone through the first carafe quickly, so I'd gotten another. I planned to get plastered.

    "Slow down. They won't run out.”

    I didn't respond, but instead poured myself a drink and took it in one swallow.

    "Why pay for good imojōchū if you're just going to guzzle it?"

    I shrugged and poured another.

    Kao reached out, put his hand on mine, and stopped me. "Okay, tell me what's wrong."

    “Nothing.”

    “Don’t give me that. As your sister and co-wife, I demand that you tell me.

    "No."

    "Okay, as your friend, I’m asking.”

    I looked at Kao, trying to stare her down. It was none of her business, but my vision blurred, and a tear trickled down my cheek. "I haven't heard from Tomo. It's almost Christmas… I wanted… together.”

    She let go of my hand, but the glass stayed where it was. I waited.

    "Yep, you've got it bad, don't you?"

    She poured herself a drink, but left it sitting. Then she resumed, "He’s a tsundere; you’re going to have to ask him.”

    "I can't."

    "You asked Shiro, and she was a stranger."

    Kao topped off our drinks, then proceeded to take out her phone. "He's probably busy fixing that old house they inherited and training to keep their kami happy. You’re going to have to bell the cat, or should I say the tsundere.”

    She dialed his number, handed me the phone, and then knocked back her drink. "Ganbatte!"

    I put the phone to my ear and heard it ring. Then, Tomo’s voice said, "Moshi, moshi."

    I swallowed. "Christmas?" I swallowed again. "Are you free?"

    Tags: #KonbiniIdol #Yuri #Polyamory #LGBTQ #Romance #LGBTQIA #Queer #SappficRomance #SapphicBooks #QueerRomance #Tsundere #NMFic

  24. A Cat-Ear's Journal: Konbini Idol Side Stories
    Chapter 85.1 Released

    Belling the Tsundere ツンデレに鈴を付ける勇気

    #Wss366 12/15 #PIXIVCharitySanta

    •───⋅☾Kan-chan POV☽⋅───•

    "Kanpai," Kao said, raising her glass. I could hardly hear her over the boisterous noise in the izakaya. The din still reached us even though we'd arrived before the after-work crowd and gotten a screened-in booth. Maybe I should have picked a less popular place, but they stock my favorite drink, top-shelf Satsuma imojōchū.

    I waved for more shochu—we'd gone through the first carafe quickly, so I'd gotten another. I planned to get plastered.

    "Slow down. They won't run out.”

    I didn't respond, but instead poured myself a drink and took it in one swallow.

    "Why pay for good imojōchū if you're just going to guzzle it?"

    I shrugged and poured another.

    Kao reached out, put his hand on mine, and stopped me. "Okay, tell me what's wrong."

    “Nothing.”

    “Don’t give me that. As your sister and co-wife, I demand that you tell me.

    "No."

    "Okay, as your friend, I’m asking.”

    I looked at Kao, trying to stare her down. It was none of her business, but my vision blurred, and a tear trickled down my cheek. "I haven't heard from Tomo. It's almost Christmas… I wanted… together.”

    She let go of my hand, but the glass stayed where it was. I waited.

    "Yep, you've got it bad, don't you?"

    She poured herself a drink, but left it sitting. Then she resumed, "He’s a tsundere; you’re going to have to ask him.”

    "I can't."

    "You asked Shiro, and she was a stranger."

    Kao topped off our drinks, then proceeded to take out her phone. "He's probably busy fixing that old house they inherited and training to keep their kami happy. You’re going to have to bell the cat, or should I say the tsundere.”

    She dialed his number, handed me the phone, and then knocked back her drink. "Ganbatte!"

    I put the phone to my ear and heard it ring. Then, Tomo’s voice said, "Moshi, moshi."

    I swallowed. "Christmas?" I swallowed again. "Are you free?"

    Tags: #KonbiniIdol #Yuri #Polyamory #LGBTQ #Romance #LGBTQIA #Queer #SappficRomance #SapphicBooks #QueerRomance #Tsundere #NMFic

  25. PASQUETTA: MENO SCHIUMA HYPE, PIÙ FONDAMENTALI GENUINI! 🍺🇮🇹

    In Italia la Pasquetta è sacra: brace, buon vino e, quest'anno, una caraffa di birra artigianale decentralizzata 🍻

    Scegliere Dash è come scegliere una buona birra artigianale rispetto a una commerciale sbiadita: sai cosa c’è dentro. Niente trucchi, niente intermediari, solo codice e responsabilità.

    Buona Pasquetta di sovranità e brindisi consapevoli alla Dash Community Italiana 🥂🇮🇹

    #CFV -> #DashTo5000 [...]

    x.com/ItaliaDash/status/204105