openpgp4fpr:2265D7F3A7B095CC3918630B6A6CD5B765632D3A
- 51 Posts
- 46 Comments
1·5 months agoI don’t think (or, let’s hope…) that the current decline is a general overall decline, but rather a before summer decline like in 2023 before vacation where people tend to spend money on their and their families’ recreation.
1·5 months agoF11 toggles the Styles sidebar (in non-full-screen view…).
Try Shift+Ctrl+J to toggle Full Screen. If that doesn’t work (non-English UI, other key bindings, …) try Shift+Esc that presents a search command input field, enter full and it should list “View -> Full Screen” (in English UI); hit that.
Gitea has tea and Forgejo/Codeberg has berg, see also https://docs.codeberg.org/git/clone-commit-via-cli/#gitea-%2F-forgejo-cli-tea
Bad clickbait headline.
Depends on what your language’s script is then with assigned Unicode characters, how wide-spread it is, when fonts will support the glyphs, and what you mean by “changes to be available on my local OS”. What OS? What does available mean here? Do you expect the OS UI to be in your language? Doubtful. Some desktop environment maybe somewhen. Programs using ICU are more likely to support specific script related features (e.g. word/line breaking, transliteration) when ICU will support Unicode 16 in its next version. Locale specifics may have to wait for or could be contributed to CLDR that is also used by ICU. Availability of any UI in the language mostly depends on whether translators contribute to the relevant projects.
They are “looking for a more private” client. With the centralized Discord service that does anything it wants with any message there is no such thing.
Whatever client you use, there is no privacy with Discord. Period. Full stop.
There was the particular LiMux one in Munich that was “solved” by Microsoft moving their head quarter to a district of Munich and the then new conservative coalition in town government thanked them by rolling all back and buying MS products instead.
Someone gave a little overview in that Hacker News topic mentioned.
And a meanwhile growing large topic on Hacker News.
Apparently not, you can check commits in https://git.tukaani.org/?p=xz.git;a=summary the first authored commit was 2022-01-28, then long time nothing until 2022-06-10, the first merge as committer was 2022-12-16.
Making one a maintainer (with merge and possibly even direct commit/push permissions) is handing them a key to the kingdom. Recruiting a maintainer out of the blue without them being already contributor and long term participant in the project is questionable.
Of the xz/liblzma backdoor incident.
Malicious account holders with a long term goal need to build reputation. It doesn’t matter much that such an app isn’t a dependency of other software.
74·7 months agoThis is how one attracts and invites Jia Tan and Hans Jansen types.
They are not beta, they are not test, betas of a to-be-new release are released before a version is released as fresh. And once a new version (e.g. 24.8) will be released, it will become the fresh version and the so far fresh (24.2) version will become the still version. Naming and then renaming releases in between would be even more confusing; that actually was done in the past by having Fresh and Still names but people didn’t grok the rotating scheme so now just version numbers are used.
There are always two versions, the fresh latest with newer features (“If you’re a technology enthusiast, early adopter or power user, this version is for you”), and the still one (“This version is slightly older and does not have the latest features, but it has been tested for longer”) for more cautious users. Citations from https://www.libreoffice.org/download/download-libreoffice/
You may get specific help better at https://ask.libreoffice.org/