home.social

#ftvt — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ftvt, aggregated by home.social.

  1. And with this version 2.1 of #FTVT has reached the point where all the issues on the roadmap are resolved, except for the last one:

    Clean up Codebase…
    ​:neocat_blush_hide:​

    I’ve definitely learned a lot about Typescript over the last month or so and I’m not promising that 2.1 will have the cleanest code-base ever (or even one that I would accept in my own C++-projects), or even that there haven’t been massive improvements since I started working on version 2.0, but it would still be good to further improve on technical debt.

    The other thing that still needs massive work is documentation. While I’d be delighted to receive pull-requests in any capacity, in-app documentation would most certainly be something that could really make a difference on UX, without any need to do actual programming.

    Otherwise it will have to wait until a future release.
    😉

    Anyways, I hope to get a release candidate out
    very soon (tomorrow?) and take it from there. If you want to see the current dev-version, you can find it on https://dev.ftvt.fiona.onl, but be aware that I WILL break certain things of that before the release. (I want to start with an IndexedDB version-number of 1, which means deleting the old database in an incompatible way!) So don’t rely on it as something that will keep working! It’s a dev-site with severe bugs, significantly broken some of the time, without the usual privacy promises, but you can use it for a sneak-peak. 😉

  2. Looking through the current dev-version of #FTVT with wave.webaim to make sure that I don’t pointlessly leave what little accessibility this category of app can inherently still have on the table.

    One error: Input-field has “Language missing or invalid”.

    (There are further warnings that I’m going to look through, but this is not about them.)

    Well, I’ve been pretty fucking crazy with regards to how much effort I’ve put into assigning all the language-tags correctly, so I already had an idea what the problem was and further digging revealed that I was indeed right:

    There is a dialog in which you can add a custom language, which needs to be assigned a name and a language code.

    For example “Malti” and “mt” for Maltese. The idea here is that you use the name of the language in that language, not the English name, such as “Deutsch” for German, “Nederlands” for Dutch, and so on. As a consequence there is of course no way to set the language-code of that field correctly, because the user is entering the language for which the language-code should be set. Because of this I set the language-code of that input-field to be the empty string, indicating an unknown language.

    And this is what wave now complains about…

    Now, to be fair, I have set the placeholder-text ‘e.g. “Malti”’, which is half English and half Maltese, so there is an implication that it’s English (because of the “e.g.”) but also partially Maltese (because of the “Malti”). Normally I could use span-tags with lang-attributes to set both of them correctly, but this is not possible with placeholder-attributes.

    So should I set the input-tag as a whole to be one of the two, or what is the correct way to deal with that?

    (And I’m not asking what a given piece of (accessibility-) software makes of it, I’m asking what’s the
    correct way.)

    Anyone ideas?


    #accessibility #a11y #webdev #HTML

  3. Based on a feature-request by @[email protected] I’ve now implemented the ability to add custom text to my voice-training app (#FTVT), meaning it will definitely be in the soon-ish to be ready 2.1 release.

    For testing-purposes I created the following text:

    Nya, nya, nya!

    Meow.

    MEOWWW!

    NYAA!

    Nya.
    (Language set to “Catspeak”, language-code to “en_NYA”)

    and had Starlight (
    @[email protected]) read it for me.

    Here is the result:
    😊

    #catgirls

  4. I’m currently working on my voice-training app (#FTVT) and despairing at the communication with the service-worker: I can send a message to it, it can receive it and I can send a response. But no matter what I try the response never arrives with the original content-script…

    (My code is
    here and here)

    Anyone any ideas?

    #serviceWorkers #webdev #typescript

  5. I’ve now set up dev.ftvt.fiona.onl to serve the latest development version of #FTVT, my free voice training software; ftvt.fiona.onl is meant to from now on only serve the latest actual release, making it less likely to be sporadically broken.

    If you want to run a mirror (please feel actively encouraged to do so!), get into contact with me, I’ll gladly explain everything to you. (It’s literally just serving a few small files from a URL, there is literally no server-component, which is largely intentional!)

    #voicetraining #trans

  6. Without claiming that there aren’t obvious things to improve or that it is “finished”, I just decided that the current version of my “Free 🏳️‍⚧️ Voice Training”-software (FTVT) is ready for a 2.0.0 release:

    You can find my instance of it here.

    This version is essentially an improvement over what was there before in just about every way:

    First of all, it actually has a version-number! The reason this is version 2.0.0 and not 1.0.0 is simply that the older version of the software was for so long in actual use that calling it anything less than 1.0 would feel wrong, but there were also significant enough changes to make this a major release. That’s why it is 2.0.

    On the user-facing side the most obvious change is the massively improved design. Just compare the version on the
    flagship-instance with the older version that is for now still available here.

    But that’s not the only thing: There is now explicit support for this to be installed as a progressive web app (PWA), which makes it almost like a normal app on mobile devices. In particular this also means that it is now much easier to use it offline: While it was always intentionally possible to download the files and open the entire thing via
    file:///…, installing a PWA might be a bit easier on mobile, improving the accessibility. (It might also allow to add it to fdroid, I’ll see about that at a later point in time).

    Now, a PWA of course has the issue that it leaves traces in the browser, but it may reduces traces left on the web, and if you don’t religiously clean your browsing history anyways, it’s possible to see where you were if you get access to it, so it’s not too bad of a trade-off.

    Speaking of traces: It’s now possible to store settings in the local storage of the browser. So far this is largely inconsequential, but for a future version I want to add the ability to store the recordings as well! Of course all of that is strictly opt-in. If you don’t do anything the app won’t leave any traces on your browser that your browser doesn’t create anyways.

    That said, there are also significant improvements on the software-side of things: Not only did I improve the quality of the code-base by a lot (still not great though!), I also replaced most of the previous super-sketchy build-system with something slightly less so to the point where others might even be interested in having a look at it: esbuild for bundling, currently run by makefiles. I still refuse to let most other javascript-code near it, but esbuild seems established enough for me to be willing to risk using it.

    So, if you need a voice-recorder that is specifically made for trans voice training and puts a huge focus on user privacy, give it a try, for example on the next
    #TransVoiceFriday! 😊

    #trans #transgender #voicetraining #transvoicetraining #transfem #transmasc #FTVT #FreeTransVoiceTraining

  7. Without claiming that there aren’t obvious things to improve or that it is “finished”, I just decided that the current version of my “Free 🏳️‍⚧️ Voice Training”-software (FTVT) is ready for a 2.0.0 release:

    You can find my instance of it here.

    This version is essentially an improvement over what was there before in just about every way:

    First of all, it actually has a version-number! The reason this is version 2.0.0 and not 1.0.0 is simply that the older version of the software was for so long in actual use that calling it anything less than 1.0 would feel wrong, but there were also significant enough changes to make this a major release. That’s why it is 2.0.

    On the user-facing side the most obvious change is the massively improved design. Just compare the version on the
    flagship-instance with the older version that is for now still available here.

    But that’s not the only thing: There is now explicit support for this to be installed as a progressive web app (PWA), which makes it almost like a normal app on mobile devices. In particular this also means that it is now much easier to use it offline: While it was always intentionally possible to download the files and open the entire thing via
    file:///…, installing a PWA might be a bit easier on mobile, improving the accessibility. (It might also allow to add it to fdroid, I’ll see about that at a later point in time).

    Now, a PWA of course has the issue that it leaves traces in the browser, but it may reduces traces left on the web, and if you don’t religiously clean your browsing history anyways, it’s possible to see where you were if you get access to it, so it’s not too bad of a trade-off.

    Speaking of traces: It’s now possible to store settings in the local storage of the browser. So far this is largely inconsequential, but for a future version I want to add the ability to store the recordings as well! Of course all of that is strictly opt-in. If you don’t do anything the app won’t leave any traces on your browser that your browser doesn’t create anyways.

    That said, there are also significant improvements on the software-side of things: Not only did I improve the quality of the code-base by a lot (still not great though!), I also replaced most of the previous super-sketchy build-system with something slightly less so to the point where others might even be interested in having a look at it: esbuild for bundling, currently run by makefiles. I still refuse to let most other javascript-code near it, but esbuild seems established enough for me to be willing to risk using it.

    So, if you need a voice-recorder that is specifically made for trans voice training and puts a huge focus on user privacy, give it a try, for example on the next
    #TransVoiceFriday! 😊

    #trans #transgender #voicetraining #transvoicetraining #transfem #transmasc #FTVT #FreeTransVoiceTraining

  8. Without claiming that there aren’t obvious things to improve or that it is “finished”, I just decided that the current version of my “Free 🏳️‍⚧️ Voice Training”-software (FTVT) is ready for a 2.0.0 release:

    You can find my instance of it here.

    This version is essentially an improvement over what was there before in just about every way:

    First of all, it actually has a version-number! The reason this is version 2.0.0 and not 1.0.0 is simply that the older version of the software was for so long in actual use that calling it anything less than 1.0 would feel wrong, but there were also significant enough changes to make this a major release. That’s why it is 2.0.

    On the user-facing side the most obvious change is the massively improved design. Just compare the version on the
    flagship-instance with the older version that is for now still available here.

    But that’s not the only thing: There is now explicit support for this to be installed as a progressive web app (PWA), which makes it almost like a normal app on mobile devices. In particular this also means that it is now much easier to use it offline: While it was always intentionally possible to download the files and open the entire thing via
    file:///…, installing a PWA might be a bit easier on mobile, improving the accessibility. (It might also allow to add it to fdroid, I’ll see about that at a later point in time).

    Now, a PWA of course has the issue that it leaves traces in the browser, but it may reduces traces left on the web, and if you don’t religiously clean your browsing history anyways, it’s possible to see where you were if you get access to it, so it’s not too bad of a trade-off.

    Speaking of traces: It’s now possible to store settings in the local storage of the browser. So far this is largely inconsequential, but for a future version I want to add the ability to store the recordings as well! Of course all of that is strictly opt-in. If you don’t do anything the app won’t leave any traces on your browser that your browser doesn’t create anyways.

    That said, there are also significant improvements on the software-side of things: Not only did I improve the quality of the code-base by a lot (still not great though!), I also replaced most of the previous super-sketchy build-system with something slightly less so to the point where others might even be interested in having a look at it: esbuild for bundling, currently run by makefiles. I still refuse to let most other javascript-code near it, but esbuild seems established enough for me to be willing to risk using it.

    So, if you need a voice-recorder that is specifically made for trans voice training and puts a huge focus on user privacy, give it a try, for example on the next
    #TransVoiceFriday! 😊

    #trans #transgender #voicetraining #transvoicetraining #transfem #transmasc #FTVT #FreeTransVoiceTraining

  9. Without claiming that there aren’t obvious things to improve or that it is “finished”, I just decided that the current version of my “Free 🏳️‍⚧️ Voice Training”-software (FTVT) is ready for a 2.0.0 release:

    You can find my instance of it here.

    This version is essentially an improvement over what was there before in just about every way:

    First of all, it actually has a version-number! The reason this is version 2.0.0 and not 1.0.0 is simply that the older version of the software was for so long in actual use that calling it anything less than 1.0 would feel wrong, but there were also significant enough changes to make this a major release. That’s why it is 2.0.

    On the user-facing side the most obvious change is the massively improved design. Just compare the version on the
    flagship-instance with the older version that is for now still available here.

    But that’s not the only thing: There is now explicit support for this to be installed as a progressive web app (PWA), which makes it almost like a normal app on mobile devices. In particular this also means that it is now much easier to use it offline: While it was always intentionally possible to download the files and open the entire thing via
    file:///…, installing a PWA might be a bit easier on mobile, improving the accessibility. (It might also allow to add it to fdroid, I’ll see about that at a later point in time).

    Now, a PWA of course has the issue that it leaves traces in the browser, but it may reduces traces left on the web, and if you don’t religiously clean your browsing history anyways, it’s possible to see where you were if you get access to it, so it’s not too bad of a trade-off.

    Speaking of traces: It’s now possible to store settings in the local storage of the browser. So far this is largely inconsequential, but for a future version I want to add the ability to store the recordings as well! Of course all of that is strictly opt-in. If you don’t do anything the app won’t leave any traces on your browser that your browser doesn’t create anyways.

    That said, there are also significant improvements on the software-side of things: Not only did I improve the quality of the code-base by a lot (still not great though!), I also replaced most of the previous super-sketchy build-system with something slightly less so to the point where others might even be interested in having a look at it: esbuild for bundling, currently run by makefiles. I still refuse to let most other javascript-code near it, but esbuild seems established enough for me to be willing to risk using it.

    So, if you need a voice-recorder that is specifically made for trans voice training and puts a huge focus on user privacy, give it a try, for example on the next
    #TransVoiceFriday! 😊

    #trans #transgender #voicetraining #transvoicetraining #transfem #transmasc #FTVT #FreeTransVoiceTraining

  10. Without claiming that there aren’t obvious things to improve or that it is “finished”, I just decided that the current version of my “Free 🏳️‍⚧️ Voice Training”-software (FTVT) is ready for a 2.0.0 release:

    You can find my instance of it here.

    This version is essentially an improvement over what was there before in just about every way:

    First of all, it actually has a version-number! The reason this is version 2.0.0 and not 1.0.0 is simply that the older version of the software was for so long in actual use that calling it anything less than 1.0 would feel wrong, but there were also significant enough changes to make this a major release. That’s why it is 2.0.

    On the user-facing side the most obvious change is the massively improved design. Just compare the version on the
    flagship-instance with the older version that is for now still available here.

    But that’s not the only thing: There is now explicit support for this to be installed as a progressive web app (PWA), which makes it almost like a normal app on mobile devices. In particular this also means that it is now much easier to use it offline: While it was always intentionally possible to download the files and open the entire thing via
    file:///…, installing a PWA might be a bit easier on mobile, improving the accessibility. (It might also allow to add it to fdroid, I’ll see about that at a later point in time).

    Now, a PWA of course has the issue that it leaves traces in the browser, but it may reduces traces left on the web, and if you don’t religiously clean your browsing history anyways, it’s possible to see where you were if you get access to it, so it’s not too bad of a trade-off.

    Speaking of traces: It’s now possible to store settings in the local storage of the browser. So far this is largely inconsequential, but for a future version I want to add the ability to store the recordings as well! Of course all of that is strictly opt-in. If you don’t do anything the app won’t leave any traces on your browser that your browser doesn’t create anyways.

    That said, there are also significant improvements on the software-side of things: Not only did I improve the quality of the code-base by a lot (still not great though!), I also replaced most of the previous super-sketchy build-system with something slightly less so to the point where others might even be interested in having a look at it: esbuild for bundling, currently run by makefiles. I still refuse to let most other javascript-code near it, but esbuild seems established enough for me to be willing to risk using it.

    So, if you need a voice-recorder that is specifically made for trans voice training and puts a huge focus on user privacy, give it a try, for example on the next
    #TransVoiceFriday! 😊

    #trans #transgender #voicetraining #transvoicetraining #transfem #transmasc #FTVT #FreeTransVoiceTraining