this might work but you’re going to get a lot of write errors.
personally in this situation i would make a separate lightweight readonly UI, possibly using the API, and give people access to that instead, while reserving tt-rss proper to the owner. i would also make it look and function more like a regular news website instead of a web “application”.
tt-rss in this scenario would provide an administrative console and backend services.
Sorry for such a late reply but just wanted to say thanks for everyone’s suggestions!
This is my end goal I guess, but it’s going to take me forever to learn how to do this haha and I don’t know anyone who can help me atm.
I’m making an aggregator for journalists and editors to use, so one of the most appealing features of TT-RSS for my purposes is the UI. It’s super functional and resembles a lot of tools currently used in the industry.
This is what I’ll try to do in the meantime, along with disabling right clicks if possible [yes I know it’s a cardinal sin in webdesign]. I pretty much broke everything when I tried to implement it haha but luckily I had saved a recent .opml file so not all was lost.