Better compartmentalization, implement Extension system

[ix5]

For ease of maintenance, development iteration speed and long-term viability, Isso should untangle its massive inter-dependencies and offer a way for users and developers to implement their own functionality without having to modify the (upstream or forked) core.

Collecting ideas:

• refactorization and SQLAlchemy #108
• https://github.com/sprin/pg-discuss/ with extension system

Possibly related:

• SQL abstraction layer (such as SQLAlchemy) #61 (moving towards an SQL abstraction layer might enable more robust extension APIs)

Note: I expect to edit this issue quite a lot

[antont]

BTW on server side, comments.py def _process_fetched_list(self, fetched_list, plain=False): seems like a nice extension point: Isso already does processing to add avatar info based on confs, but that same place could call whatever other processors for the comments list.

I'm adding url string avatar info in our fork somehow now, our users already have the avatar url in their data.

[ix5]

Yes, that's a great entry point you've identified.

In case you would like to discuss back-and-forth with other contributors taking a look at this, you're also very welcome to join the IRC #isso on Libera.Chat or via Matrix