Follow-up Comment #2, task #16582 (group administration): [comment #1 comentário #1:] > * To me, it appears the package is taking a web site as input and presenting it in a different form (with different styling and possibly different structure). Is that correct?
It is actually a way to circunvent the requirement of non-free JavaScript in the official website. One could disable JavaScript in the browser and still use this project as a browser extension (even though some source files are in JavaScript, the browser doesn't block extensions' JavaScript). > * What are the problems that the original web site has and that the modified/augmented web site does not have? The original requires non-free JavaScript. The submitted project doesn't. > * How does the approach of doing this in the browser compare with the approach of doing it on a server, in a website of yours? a) in terms of user freedom, b) in terms of ease-of-use? Forcing random client-side autoexecuted software against the end user is bad for software freedom, and this is the problem with websites/servers by third parties. See https://www.gnu.org/philosophy/wwworst-app-store . > * How is the perennity of the software? I would expect that each time the original web site is restructured or reprogrammed (every couple of months?), your package breaks and needs considerable effect to revive. (Just like yt-dlp needs to catch up every time youtube's code is restructured.) Is this correct? How often did you have to catch up in the past? The initial work started in 2019, and was changed in 2023 and 2024. _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/task/?16582> _______________________________________________ Mensagem enviada pelo Savannah https://savannah.nongnu.org/
signature.asc
Description: PGP signature
