Emergency Changes
0 guests and 0 members have recently viewed this.
The top 3 point earners from 23rd Nov 2025 to 30th Nov 2025.
| PDStig |
|
|
|---|---|---|
| Master Rat |
|
|
| cupper3 |
|
There are no events at this time
News: Emergency Changes
Emergency changes are being made due to my continually sinking financial situation. Please read more; this article contains important information.
I wish I could help you financially. But I'm living in a rented spare bedroom myself. I don't think the amount I'd realistically be able to pay you would help you. (My Composr site is for my side business, and my side business isn't making enough money that it'd be able to sustain me as a full-time or even part-time employee, let alone you.) It's really probably best for you to stop working on Composr until you can find a day job. And it really seems like you should be able to, since you seem to be a perfectly effective developer. (I've just sent you a LinkedIn connection request, just in case I come across anything that looks like it could fit. I'd certainly let you know if my own day-job company has an opening on our web team. One other thing— the resume links on your personal website seem to be broken right now.)
I'd be willing to attempt to help with hosting the Composr website/forums if that's not something you'll be able to do anymore. I'd need to discuss the load and resource requirements that you've seen to determine if I could do it or not. (I'm able to host my own website on Composr with what I believe to be a similar number of users, so it seems like I should be able to, but I'm not entirely sure since it sounds like you've got a more complex setup for the homesite.)
Yes. However, I experienced the bug on about 30-50% of my attempts at creating bug notes. That is a significantly high error rate. And every time, I lose what I type (Mantis does not have auto-save like Composr does). I can disable the form security token feature (and I considered this), but that opens up Mantis to CSRF attacks, where an attacker can trick you into submitting sensitive information publicly on the bug tracker. It is not a risk that I want to take (not having form tokens is a big no-no in modern security).
That's understandable. We are in hard economic times. I appreciate the thoughts.
Thank you. I accepted.
Funny, I noticed that yesterday, before I had the chance to read your full reply here. I fixed it. All of my Nextcloud share links have changed since I did the operating system upgrade at the beginning of the month.
I appreciate it. And I will keep that in mind. The site currently only sits at < 100 GB (I do not know the exact number at this time). I have a script that automatically cleans up old generated upgrade files after 30 days. And that helps a lot with keeping the total size of the site down. The two big concerns would be the following:
The good news, however, is that aside from the site running off of a git branch, it does not need any special software. It runs just like any other Composr site.
https://composr.app/fo…/potential-challenges.htm
However, the ability to monitor (subscribe for notifications) individual issues and the ability to sponsor issues with points will not immediately be available. Development of those features will remain postponed.
Also, a new page is now up:
https://composr.app/purchase.htm
You can use your points to purchase things. You can donate to me to continue developing Composr, and you will receive points. More things will be added over time.
Nothing is official. But we are working the logistics out.