> keeping it up-to-date with its dependencies etc.
not if the software is functional today, and doesn't require interacting with third party systems (like this tinylittleoffice suite).
By the time the underlying infrastructure (like browser compatibility, or self-hosting OS becoming obsolete) fails, you're likely no longer using it anyway.
The "documents" seem exportable in text format, and in any case, potentially salvageable with another vibe-coded tool if such need arise.
Therefore, the original author is no required to maintain it.
not if the software is functional today, and doesn't require interacting with third party systems (like this tinylittleoffice suite).
By the time the underlying infrastructure (like browser compatibility, or self-hosting OS becoming obsolete) fails, you're likely no longer using it anyway.
The "documents" seem exportable in text format, and in any case, potentially salvageable with another vibe-coded tool if such need arise.
Therefore, the original author is no required to maintain it.