Here's the gist; the reason it's been so long since a new version has been released is because I switched languages. I just couldn't couldn't get the RAM usage as low as I wanted in Java so I'm doing in on C++ now which means rewriting all the instructions for connecting with other sites. And for that I'm taking my time by having my own XML, HTML and JSON parsers to my liking to make work easier.
Also It will have a new name and logo that I will reveal when it's released. And I will be reworking my patreon for that and other similar sites I've discovered.
Things to expect on the next release or later ones:
→ Get notified when someone mentions you → Ignore users → Reposting submissions → Rich text editor for descriptions and literature submissions → Simple builtin browser for adding accounts, enhanced privacy and quick account switching → Manage multiple accounts in the same site → Modability features (it is already modable but it will get mod management) → ARM server version for use in lightweight home servers such as Raspberry PI → Streaming interface - both stream and announce on the same in one go → Upload work files directly (.psd, .kra, .ora and maybe others) and have the program convert automatically to the proper format and your size of choice for uploading → Cropped thumbnail creator → Schedule submissions → Filtering messages and submission feed → Automatically linking users' multiple accounts (reduces redundant notifications of the same artwork being posted in multiple places, and allows better linking when writing descriptions on submissions) → Description templates → Keyword autocomplete → Importing/synchronizing galleries → Editing submissions
Also I want to have some form of commission management, but I haven't figured out how it would work yet. To have something to show for have a screenshot, showing the filter interface: https://www.dropbox.com/s/69qc548x7qt1dvf/Captura%20de%...
Now here's a few questions: - Would you be interested in watching dev streams for artwatcher and other apps? - Which site(s) do you most want to use it for? Since I'm going to have to port things the next release, it should only have 4-6 supported sites initially, so I'll take than into account. - Are you interested in it for following artists without having to check multiple websites, for the uploading features, or both?
Also I'm going to have something else interesting I'm finishing out, I'll talk about it when I later.
An ARM version does sound cool. There are some cheap hosted ARM servers out there, too; I ran an nginx cache on one (and they could run the whole of Inkbunny with the new parallel query features in PostgreSQL, if you threw enough cores and RAM at it - might not be sensible, but an option).
That's a big potential feature list, though. I think you need to manage the product carefully in order to get a solid deliverable which can do useful things, and then evolve from that. C++ can be a tricky language to get right. And I'm not sure what you mean by "have my own parsers", but beware; such code can be hard to write correctly, and it can be hard to beat the performance of existing solutions. Plus you're spending time on writing a parser rather than actual features.
I would be surprised if people wanted to watch you writing code - it's never seemed a particularly interesting spectator activity, especially as the audience would probably need to be programmers to appreciate fully what you're doing.
If you're looking specifically for furry stuff I'd suggest focusing on FA, DA, Inkbunny, SoFurry, Weasyl, Furry Network, in that order, because I see those as the sites with the largest furry traffic. I don't know if e621 is relevant to your plans, but if so, it might slot in after FA.
An ARM version does sound cool. There are some cheap hosted ARM servers out there, too; I ran an ngi
