save a life, check its not production

this is a very Stupid idea so i wont put it to the dssue tracker. but. how about enabling people to host their own devRant servers with their very own rules? this way, the main server will have a bit more breathing room and common interests could have a shared server.

the client Would have the current buttons + empty buttons that can be given a special function from server side.

also, it would be possible to view rants from multiple servers (color coded so theres no mixup in button functions) in one feed.

the client would come with the main server on first start up. the most popular servers would be listed in the settings. also, rants with 50++ would automatically be put into the main server.

jinja templates make me look towards html in a whole new light. are we 'inserting' data to an already rendered page? am i really mixing server code with ui ? It doesn't feel so. there are if else and loops being executed for html code, like wtf?

I don't know but everything feels so good. like i was literally hating every piece of website i was writing in php. everytime i wrote <div>....</div> followed by <?php ... ?> followed by another html tag /php tag in a fuckin php file, i wanted to kill someone from w3c.
WHY THE FUCK ARE WE ALLOWING THE MIXUP ?WHY IS PHP FILE HOLDING HTM TAGS? WHY?WHY?WHY?

But this... this is beauty. their is separation of concerns. jinja has some big powers, we can loop, repeat, make clauses, inherit other html classes, load html content into blocks, set variables,
but main concepts like file handling, response/request handling,calculations,etc are all being done in separate python files. I know that these jinja templates also might be running python in background, but atleast a developer cannot fuck up that code.
we can be sure that if correct jinja codes are written in html, then it would load correctly. And wherever devs doesn't fuck up, the output is better to understand and more maintainable/scaleable