My understanding is those files for previous versions go away so you can't reliably get packages for older versions even if you "pin it". If I'm wrong, please let me know, I would like to be wrong.
I don't know what volunteer / manpower is needed to just keep files around but storage and bandwidth is definitely an issue.
FreeBSD's quality implementation, quality documentation and overall sane configuration / management should be apluaded. There are so many little things that make using it joyful, like the ncurses TUI for configuration options when building packages from source.
I have used it for servers and NAS/ZFS/Samba applications for over 10 years and it's been exceptionally solid. But these days I've moved over completely to Debian systems now that OpenZFS 2.x branch is pretty mature and probably won't go back and it's due to the package management aspects.
Sometime around FBSD 10.x the package system moved to a rolling release which means if you don't keep your machine up to date you eventually can't get binary packages for whatever FBSD version you're on which seems like a sadistic thing to do. A server that works fine but one where you might need to install some random utility suddenly breaks in 20 different ways if you enter the depths of trying to install said utility on modern FBSD.
I thought my understanding of this was broken and reached out to FBSD devs on IRC and they confirmed that it's basically a rolling release model these days.
With Linux distros like Debian after development on a version ceases (i.e 10.x) apt-get still works but you may not get the latest or greatest, bug fixes or security fixes. But if you need something and it's in the repository you can at least limp along until you bite the bullet and do a major release upgrade, assuming you need the latest/greatest.
I know everyone's experiences here will vary but I've had very little breakage going between major version of Debian, but with FBSD too many things would break when doing a major release upgrade.
Teams is like many other MSFT products, written / designed by comittee, not enough testing and questionable UI choices that will never be revisited.
I've experienced a myraid of issues that others here have mentioned, not limited to meetings never ending, resources spiraling out of control, poor organization of conversations (no segmentation between 1:1 or group conversations vs. conversations from a meeting).
I wouldn't hold my breath that things will get better. People have complained about Lync/Skypes for a DECADE with little to no improvement...
Since I was curious myself to see what was out there for EDIF, I stumbled upon this -- an open-source C++ library to read/write EDIF (I haven't used the library nor do I have any affiliation with the project):
This is definitely the wrong way to ask but in another thread about the PineNote, you mentioned you have a flow to sync your RM2 to Bookstack -- are your scripts on github or any other place? If not, would you consider making them public or posting on Reddit /r/selfhosted/ and/or /r/RemarkableTablet/ ?
I'm new to HN (as a poster, long-time lurker) and I didn't find a way to directly send you a message.
Like a few other people have said, EDIF has existed for decades and it works and it's open.
As of late it seems to be a lot of re-invention of problems that have been solved, except there's some use of JSON, Python, etc. It feels like people solving problems they find interesting rather than solving problems that are necessary.
I don't know what volunteer / manpower is needed to just keep files around but storage and bandwidth is definitely an issue.