This project are dead ?

[mcarbonneaux]

This project are dead ?

[abelcheung]

Nope, Google only retires Chrome Apps. KeePassXC-Browser is an extension and won't be affected.

[baradhili]

there are forks that are more recent.. but not many also put the actual compiled file :(

[mcarbonneaux]

i've seen effectivly different patch with pr... but no inclusion... why i'm intergogate about project freeze...
if perry not abel to maintain while be interesting to transfert the maintenance to any person that can continue to maintaine...
or make a fork, generaly is preferable to transfert the maintenance to group of people...

[baradhili]

I think it is safe to say this repo is dead. Keepass2 itself seems to be on life support - even though KeePassXC does not cover all features.

Happy to help!

[abelcheung]

@mcarbonneaux

if perry not abel to maintain while be interesting to transfert the maintenance to any person

Given that perry doesn't go MIA (still contributing to other projects occasionally), I see it an indicator that perry actually wants others to actively migrate to other solutions instead of sticking to keepasshttp. I have described some possible migration paths here, and there could be other ways I haven't covered as well.

@baradhili

Keepass2 itself seems to be on life support

Nah, KeePass2 is still the pioneer in this area, implementing new crypto algo and stuff, and its plugin ecosystem isn't surpassable for now. KeePassXC is playing the catch up game, though in terms of UX and other basic integration it became superior.

[mcarbonneaux]

@abelcheung keepasshttp is a good product is why i aswered if the project is dead !

i've not seen KeePassNatMsg ! is very interesting solution ! the usage of Native Messaging is very interesting, but there no risk of suppresion of the native messaging ?

Because chrome are removing the chrome apps that are related to...

https://developer.chrome.com/docs/apps/nativeMessaging/

Is not very clear that native messaging while be removed for extension to....