Spectacle8011

joined 2 years ago
[–] [email protected] 3 points 4 months ago

Even if all High Profile patents in Europe expire next year, this means absolutely nothing for US-based companies/orgs or companies/orgs that trade in the US, which still has patents that won't expire until 2027 according to this article. Even then, this means absolutely nothing because there is no such thing as a H.264 decoder/encoder that only supports the High Profile spec (aside from OpenH264, which already circumvents the patents for companies/orgs that want to use it, but is still lacking). x264 supports H.264 features from later specifications, and the patents for those things likely won't expire until after 2030.

[–] [email protected] 3 points 4 months ago

Who is using the Google app for iOS..?

[–] [email protected] 28 points 4 months ago (2 children)

The irony being that some Linux users fear change (or at least fight it tooth and nail) more than any other computer user.

[–] [email protected] 2 points 5 months ago

Autodesk Maya actually has a Linux version. I was surprised to learn this.

[–] [email protected] 1 points 9 months ago

Eh, X11 Forwarding, VNC, SSH, XRDP, Waypipe whatever, it's all very similar

[–] [email protected] 0 points 9 months ago (2 children)

Wow, this is actually fairly technical unlike うぶんちゅ. SSH and X11 forwarding in the first chapter. By chapter 4 we're already exiting Vim.

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

In general I agree, though had something to add regarding these points:

by defaults the sandbox is pretty good

This is a rather major problem with Flatpak; the maintainer decides what permissions they need by default, not the user. The user needs to retroactively roll them back or specify global options and manually override them per-app, but that's not user-friendly at all. Though many Flatpaks do have good permissions because Flathub maintainers step in and offer suggestions before approving the Flatpak for publication, there are a number of Flatpaks that punch big holes in the sandbox; so much so that they might as well be unsandboxed.

But Bottles has a great sandbox, for instance, which is just what you'd want when running lots of proprietary Windows applications you maybe don't trust as much as your Linux-y software.

It's better than what we have with traditional packages but it can sometimes get in the way and not all beginners can easily figure out how to fix permissions issues with Flatseal. This will probably improve as we get more portals built.

some apps are less maintained and use EOL runtimes etc

Not much is different for distribution-maintained packages, either. See TheEvilSkeleton's post about how there are over 1200 unmaintained packages in the Debian repositories, and even over 400 in Arch's much smaller repositories that are outdated (!). At least Flathub applications are usually maintained by upstream, and so are usually as up to date as they can be.

not suited for some apps like terminal apps or system stuff

This isn't really true. It's only true when terminal applications need privileged access to something. Flathub ships Mesa userpace drivers and NVIDIA's proprietary userspace drivers just fine. You can package something like yt-dlp in Flatpak just fine with --filesystem=host. Hell, they've even got Neovim on Flathub. Sure, it's a little more cumbersome to type, but you can always create an alias.

Flatpak is not suitable for all graphical applications, either. Wireshark's full feature-set cannot be supported, for example.


I would add that:

  • You can easily rollback Flatpaks to a previous version (even from a long time ago) with flatpak update --commit. Much harder with traditional package systems, and you'll probably need to downgrade shared libraries too.
  • You get a consistent build environment with Flatpak manifests. If you want to build a newer version of a stable package you're using straight from master or with a few patches, all you really need to do is clone it from flathub/whatever, change a few lines, and it has a very high chance of building properly. No need to figure out dependencies, toolchains, or sane build options. And it's all controlled from an easy-to-read and modify file.
[–] [email protected] 1 points 1 year ago

It's good to see you guys on Lemmy :)

I tested it a bit a few days ago, but I'll see if I can give it a more rigorous go today. The ones I've found Mojeek to be weak in are bug strings that programs I'm working with spit out. Although I think I've had more luck in the past few months.

[–] [email protected] 1 points 1 year ago (2 children)

Kagi is the only search engine I use which has really good results and no junk links. ...and you have to pay for it, of course. It's a meta search engine but they use their own indexes for news results and Teclis, which indexes small commercial sites with fewer than 5 trackers. One of the cool features it added recently was an icon for identifying paywalled articles.

I'd like to recommend Mojeek, my default search engine, but it still has a way to go. If you're just looking for an "answer engine" rather than a general search engine...I guess an LLM probably isn't a bad place to start?

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. The main focus is on getting Japanese-only visual novels to work, because they tend to be much quirkier.

This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/[email protected]. It’s available on our community wiki, https://wiki.comfysnug.space/. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

cross-posted from: https://lemmy.comfysnug.space/post/138679

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/[email protected]. It’s available on our community wiki, https://wiki.comfysnug.space/. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

cross-posted from: https://lemmy.comfysnug.space/post/138679

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/[email protected]. It’s available on our community wiki, https://wiki.comfysnug.space/. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

Wikipe-tan has been the (cutest) unofficial mascot for Wikipedia since 2006. This manga was posted to PIxiv and Wikipedia in 2010 by Kasuga, where he said this:

二年ぐらい昔に、後輩の合同誌で描いたウィキペたん漫画。 (「ウィキペたん」が何か知らない人は、ウィキペディアで検索だ) こんなもん再利用する人はいないと思いますが、 「クリエイティブ・コモンズ 表示-継承 3.0」のライセンスで配布してます。 http://creativecommons.org/licenses/by-sa/3.0/deed.ja

しかし、この子ってこういうキャラだったんだね。

The pages on Wikipedia:

  1. https://commons.wikimedia.org/wiki/File:Wikipe-tan_manga_page1.jpg
  2. https://commons.wikimedia.org/wiki/File:Wikipe-tan_manga_page2.jpg
  3. https://commons.wikimedia.org/wiki/File:Wikipe-tan_manga_page3.jpg
  4. https://commons.wikimedia.org/wiki/File:Wikipe-tan_manga_page4.jpg