@dside Yeah. That fucking Perl one-liner.
Also, yes, those VT-100 conventions clashing with desktop conventions are also disorienting as hell if you don't know what's going on.
As for command naming... Well, keyboard shortcuts can also be counterintuinive, the advantage however is that you need to learn them once. But yeah, Pacman sucks for this.
Noticed a redirect loop on the help.libreoffice.org website, but failed to find an appropriate address or page to report it (except for Bugzilla, which requires an account, and I see no "project" for the website there). Noticed a Mastodon contact though, maybe this will work. Or maybe somebody on Mastodon will point to an appropriate place to report #LibreOffice website issues? Either way, it should be better to write here than to ignore.
@libreoffice, <https://help.libreoffice.org/latest/en-US/text/sdatabase/dabawiz02pgsql.html> redirects to <https://help.libreoffice.org/en-US/noscript.html> with a meta refresh, which then redirects to <https://help.libreoffice.org/latest/en-US/text/swriter/main0000.html> with the "location" HTTP header, which redirects back to noscript.html, as the first one did, and the loop goes on.
As another minor website issue report, icons are broken if pages are not allowed to set custom fonts. Some contrast ratios (e.g., in the footer) are very low, some elements (e.g., operating system choice on the "download" page) do not fit into the areas dedicated for them and overflow awkwardly if minimum font size is set (to 16, for instance). Some content (e.g., on <https://www.libreoffice.org/discover/templates-and-extensions/>) is simply unavailable with JS off, while with JS on it is just hidden behind an unnecessary click.
We actually have more features than the original, by quite a bit margin. What features they finally implemented came years after we had them in most cases.
There are two features we hired people to bring in and should be coming early next year now that we have developers hired. Those are editing posts without reposting, and in-line translation. Everything else we are ahead of the curve on.
As for clients, if you use a generic ActivityPub client it should work fine as we adhere to all AP standards. Just avoid mastodon specific clients and you should have the full clients features working fine.
@AnarchoNinaWrites
I really don't get this attitude from people. It's so surreal. Okay, you think these people are getting wrong or bad information, that can be frustrating.
But just 'how dare they find something they like to listen to/enjoy'? C'mon. I don't like tiktok much, gen x brainpan doesn't mesh, so I just get linked it, nod, then move on.
As for OF- my recent disapointment with it was 'damn, this didn't click for me. Oh well. Good for him anyway. Unsub.' Then I moved on.
@evan But someone else has another implementation! This one is publicly _modifiable_ in narrow ways. Let's say that people can submit _translations_ for it. That's also a cool feature!
But very, very different from Auditable.
So my type for that one is [Note & CommunityLanguageSupport].
This provides clear signal to anyone who looks at the object what's going on.
As it is, and I'll freely admit this may be a "me" issue, I have trouble with "this Note may have arbitrary actor behaviors" 2/2
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.