Mike Puglin The question is an interesting one – but should be more contextualized than a simple vote count, IMO.

I am also in favor of some kind of systematic feedbacking between development and use – even more specifically use cases or even more specifically some set of defined domain requirements. (Which would have to be defined beforehand, of course)

But certainly there are other criteria at play / w/ legitimacy than pure and broadband user votes. Like vision of devs/team, bussiness + market considerations, balancing-off of features + feature-development (building a coherent architecture) etc.

Also, I think it is good to recognize there have been discussions here and in forums about this. Also worthwhile to acknowledge: Capacities has explicitly started out to solve the problem of personal knowledge management and notetaking, not as a task app. Then, while things can be bend in different directions on the go / while growing, the problem of feature bloat is a real one, – and has 'killed' (in some ways) different precious apps. Also to factor in here: the whole initial success of Capacities is strongly based on its special handling of media within its system (differentiating it from Obsidian, and some respect Notion et al) – so, with regards to legacy trail it makes total sense to keep and build on that strength… etc. etc.

So, I am all for taking into consideration actual use (esp in some real scenario + domain specific contexts) – but it´s not as easy as just counting votes in one forum and leaving everything to subjective demand of an anonymous user base…

… at least in some more 'value driven' projects this can´t be the sole / isolated measure

[I leave out 'stack ranking' here, which is not the only game in town, and especially in quality and creativity conscious contexts has it´s different challengers… safe to not automatically 'assume' it´s the protocol used in Capacities… (if there is one :-) ) ]

Mike Puglin I actually started using Capacities EXACTLY FOR managing my zillions (w/a 'B') of photos and videos that I have on various hard drives, optical, and solid state memory cards / SSDs.

I'm at the point where if I can't get Capacities to do what I need, I've been gearing up to develop an application myself (being a software developer by profession) using Avalonia UI.

Just because you may not need certain features doesn't mean that everyone else doesn't need it either or don't consider it important.

I'm not a big "Calendar" user but I can appreciate what's been recently added.

I'm actually here today to request optional "dots" on the Calendar for days where an Object was created on that date so I can see at a glance when I created something - in my case, added some new photos or videos etc., into my collection(s).

William Bell To each their own. Capacities doesn't seem the tool to use for your purpose. But, we all work differently.

Have you seen DigiKam, it may be better suited to your purpose.

Mike Puglin Thanks Mike, NO I had not heard of DigiKam!

I'm always on the lookout for media management wares; I ran across Mylio just yesterday and was planning on giving it a try!

I def appreciate the tip, especially with it being open source and all - PROPS!

I've been successfully using Obsidian for "File Ingest" chores - keeping track of new files I add to my drives, but have yet to catalog my zillions of pre-existing media.

I had purchased Kyno, but it died shortly after being acquired by another company. 🤬

I'm coming from Photo Supreme, ACDSee Ultimate, Grass Valley Mync, IMatch and bunches of others...

Ultimately I'm going to have to continue w\the development I've already started using Avalonia UI to get all the unique features I have in ny mind.

Thanks again for your tip on DigiKam!

William Bell / Mike Puglin – yeah, we all know the chore this DAM question is for images… I ended up in some weird combo of On1, Bridge (yeah, that old type), a little PhotoMechanic+, a dose of Eagle, and even some DevonThink (for text/content enriched + contextual photo work) …

… one definitely can see its not good.

… but one is always tempted / forced to hop bec somewhere the organic workflows (not to mention metadata compability) simply breaks…

left behind several like Supreme, Mylio, NeoFinder,… and AtomicView from AntWeb in France anyone ?! … 😅

Kyno is a real sad 'market story'. Then there is also a new contender Peakto/Avalanche from Cyme, which might be worth a look for ingestion of heterogenuous DBs and heaps… but it´s a little 'meta'

I always keep returning, with a sigh, to this old article:

… it´s from 2014 originally … 😆