home.social

#relm4 — Public Fediverse posts

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

  1. Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
    But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
    #BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

  2. Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
    But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
    #BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

  3. Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
    But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
    #BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

  4. Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
    But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
    #BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

  5. Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
    But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
    #BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden

  6. My fellow fedizens, i have done it.
    I have applied #BitRitter to nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
    Wish me luck.

    If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.

    @NGIZero

    #LinuxMobile #Relm4 #gtk
    #rbw #BitWarden #Vaultkwarden

  7. My fellow fedizens, i have done it.
    I have applied #BitRitter to nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
    Wish me luck.

    If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.

    @NGIZero

    #LinuxMobile #Relm4 #gtk
    #rbw #BitWarden #Vaultkwarden

  8. My fellow fedizens, i have done it.
    I have applied #BitRitter to nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
    Wish me luck.

    If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.

    @NGIZero

    #LinuxMobile #Relm4 #gtk
    #rbw #BitWarden #Vaultkwarden

  9. My fellow fedizens, i have done it.
    I have applied #BitRitter to nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
    Wish me luck.

    If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.

    @NGIZero

    #LinuxMobile #Relm4 #gtk
    #rbw #BitWarden #Vaultkwarden

  10. My fellow fedizens, i have done it.
    I have applied #BitRitter to nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
    Wish me luck.

    If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.

    @NGIZero

    #LinuxMobile #Relm4 #gtk
    #rbw #BitWarden #Vaultkwarden

  11. My biggest enemy today in #Rust is the fact, that i cannot implement/extend traits from another crate. So i wanted to use structs from the #rbw crate since i am piggy-backing on their logic, but since i need Debug on those, because i am writing a #Relm4 app, i am screwed. Or am i missing something?
    I mean i could just use my own types based on the rbw ones, since they are not likely to change (the crate looks feature-complete), but meh, is there a better way?
    :boostRequest: :boost_ok:
    #RustLang

  12. My biggest enemy today in #Rust is the fact, that i cannot implement/extend traits from another crate. So i wanted to use structs from the #rbw crate since i am piggy-backing on their logic, but since i need Debug on those, because i am writing a #Relm4 app, i am screwed. Or am i missing something?
    I mean i could just use my own types based on the rbw ones, since they are not likely to change (the crate looks feature-complete), but meh, is there a better way?
    :boostRequest: :boost_ok:
    #RustLang