seebye/ueberzug is no longer maintained

[thimc]

Hi,

As many of you probably know, the author of Ueberzug, seebye has decided to stop maintaining Ueberzug because of various reasons that I won't go in to here. You're free to read that bit for yourself.

Until there is a maintained fork of Ueberzug, I will stop any development for vifmimg and lfimg as I don't want to maintain anything that relies on projects that no longer receives updates.

I hope that everyone here understands the situation and I just want to thank each and every one of you who contributed.

seebye/ueberzug: https://github.com/seebye/ueberzug/blob/master/README.md

[eylles]

there is an ongoing talk to do a unified repo for continuing with ueberzug with an organization on this issue: gokberkgunes/ueberzug-tabbed#1

i will start an organization and set up things so that we can tidy up a fork of ueberzug to make it the next upstream.

[thimc]

there is an ongoing talk to do a unified repo for continuing with ueberzug with an organization on this issue:

Great news! Please let me know when it's up and running and I will make sure to update my repos so that any new users are directed to the maintained fork.

[jstkdng]

Hey @thimc ,as a personal project I rewrote most of ueberzug's functionality in C++ (proper tmux support is in progress). The codebase is simpler and so far is faster and has more image format support than current and past ueberzug.

https://github.com/jstkdng/ueberzugpp

I'd be thankful if you could show my project for your current and new users.

I'm also part of the org @eylles made, and this is the new repo that has been set up. After fixing the few bugs seebye left a new release will be made.

[eylles]

aaand we got a release

https://github.com/ueber-devel/ueberzug/releases/tag/18.2.0

now it is just a matter of distribution, due to current pep standars the ideal would be for distros to package this fork as such i will send a series of emails, still will look into getting it on pypi

[jstkdng]

borgar