Brie ()

@gavi@bagel.ing there are also two flavors to this the first way is "just" making a big deal out of a relatively tiny issue, like you pointed out and then there's a version where people will start to say borderline (or fully) transphobic things, but justifying it as "they're bad because XYZ so they deserve it". e.g., switching to they/them for all trans people they don't like, people misgendering Caitlyn Jenner

This is actually kinda serious, it's hard to place the sensations exactly And sometimes I'm pushing for a long time and feel like I'm making great progress, but when I check I still have 5 cm to go

Beating the AGP allegations by being a massive nerd

Dilation depth is kinda weird: (at least with my surgery) you get some depth from the surgery itself, which you want to get to when dilating. For my surgery, this is around 14 cm/5.5 in at a minimum You can have pain or potentially even some minor problems if you push too hard However, if you don't dilate enough, you can (and eventually will) permanently lose depth, which is also not desirable I'm not sure if I'm doing things 100% correctly, but they're at least not totally wrong

I'm not super concerned about all of this

Even if I end up at only 13 cm, that seems like plenty. There are two types of objects that I'll potentially be putting in my vagina:

1. Sex toys, where I can just pick whatever size is comfortable
2. Girldick, which is flesh and therefore compresses a bit under pressure (just like the back wall of my vagina, which also has some give to it)

Maybe I missed something, lets look at the flatpak docs again (which aren't as formal as the other ones): https://docs.flatpak.org/en/latest/conventions.htmlAs will be seen below and in future sections, this ID is expected to be used in a number of places. Developers must follow the standard D-Bus naming conventions for bus names when creating their own IDs. This format is already recommended by the Desktop File specification and also the Appstream specification.Yes, cool, flatpaks must follow the dbus bus name conventions. They should also match desktop file names and appstream names.while not required, the application portion is recommended to be in lowercase as welland they should be all lowercase ​:neobot_explode:​ Lets look at examples. That should help. The freedesktop spec was made in large parts by GNOME and KDE, lets check out what they do. This will solve the ambiguity. KDE KColorChooser flatpak manifest "id": "org.kde.kcolorchooser", and this matches their desktop file, org.kde.kcolorchooser.desktop now, GNOME SystemMonitor flatpak manifest "app-id": "org.gnome.SystemMonitor.Devel", this matches their desktop file, org.gnome.SystemMonitor.desktop nice. cool. thank you. glad we're consistent ​:neobot_explode:​

reading the spec about IDs for AppStream, which needs to match the flatpak ID:While hyphens are allowed for legacy compatibility, their usage is strongly discouraged to ensure interoperability of the AppStream ID with other tools such as D-Bus (and thereby making the ID more generic and useful). Okay, sure. You shouldn't use hyphens because you can't use them in dbus/appstream ids, and all of this should match. Makes sense.

One sentence later:Additionally, even though uppercase letters are permitted in a component-ID, it is strongly encouraged to only use lowercase letters for the ID.Sure, it is discouraged. Thank you for the info. All lower case. Let's just check out the other specs (for fun).

starting with the freedesktop specifications for naming .desktop files:For applications, the part of the name of the desktop file before the .desktop extension should be a valid D-Bus well-known name.great. makes sense.The domain name should be followed by the name of the application, which is conventionally written with words run together and initial capital letters (CamelCase). For example, if the owner of example.org writes "Foo Viewer", they might choose the name org.example.FooViewer, resulting in a file named org.example.FooViewer.desktopThat seems like it's saying the exact opposite, but I'm probably missing something.

Lets check out the spec for dbus names to make sure:

We're looking for bus name ("the convention that an application's "main" interface and object path resemble its bus name"), so lets look at that section:Like interface names, well-known bus names should start with the reversed DNS domain name of the author of the interface (in lower-case), and it is conventional for the rest of the well-known bus name to consist of words run together, with initial capital letters.so according to various freedesktop specs:

• AppStream ID, dbus bus names, and .desktop file names should match
• dbus bus names and .desktop files should be camel case
• AppStream ID should be all lowercase

but that doesn't make sense because all of those things are freedesktop specs, which wouldn't contradict each other. right?

this is especially funny with the context that I'm not asexual or aromantic, I'm willing to be horny and non-platonic about this too I have range *: This statement should not be taken as an absolute statement of fact that Brie is entirely alloromantic. Brie may or may not be on the aromantic spectrum, the matter is still under investigation and no conclusions can be drawn until the full report is published.

The ratio of pictures is changing: As I heal more I'm going on longer walks and there's less day to day changes in swelling