@oct2pus That's good to know. I'd say most UI changes won't come back to the original. I'm personally on Ubuntu, and don't want to bring over changes that don't make sense on other distros.

If that means maintaining the base writeas-gtk repo and elementary's fork (as I'm already doing now), that's fine.

@writeas_dev from what i can tell from removing granite from tootle, granite does offer a lot of nice features but it can break easily on non-elementary desktops (relative timestamps were broken outside of the current version of elementary for one) so i wouldn't blame you for the temptation, maybe seek out someone to help maintain or see if you can refactor the code so you can at least use most of it build. although the maintainer thing might be wonky since it complicates the monetary scheme of the elementary Appstore

@writeas_dev refactor the code so you can use most of it and maybe be able to maintain a single code base for both for sanities sake*

@oct2pus Great advice. I will definitely look around if the two have to remain separate, but for now I can still relatively painlessly share the same codebase, with the elementary fork containing only changes to get it accepted to the AppCenter. Ideally they'll be much more similar in the future.