overview for Spectacle8011

Ubunchu! A manga about Linux that came out in 2009 [PDF link] by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 19 points 3 months ago

You can get the manga officially from here in its original form: https://www.aerialline.com/comics/ubunchu/

It's licensed under CC-BY NC 3.0 and the author includes the original photoshop files if you want to edit them.

It's pretty funny. I own a physical copy.

India blocks GitHub, after lobbying done by copyright trolls by Spectacle8011 in c/piracy@lemmy.dbzer0.com

[-] Spectacle8011@lemmy.comfysnug.space 25 points 10 months ago

The main Github.com domain was still accessible but raw.githubusercontent.com, where code is typically stored, was blocked.

Some days, like today, I regret commenting TorrentFreak out of my RSS feed reader.

It's kind of funny, but it's also kind of scary that not having access to Github would probably significantly impact a lot of companies and services. It would definitely impact me.

Oh well. We can always move to Sourcehut, right?

The future is now by Spectacle8011 in c/programmerhumor@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 18 points 11 months ago

Interesting choice to romanize Japanese. Now you have to figure out which romanization system to use (I was surprised を was romanized as o and not wo). But I do get it, I guess, because you have to wonder it would only use Hiragana or mix Kanji in:

大文字と小文字を無視する
だいもんじとこもじをむしする

Well, for the sake of being international, we should just use Katakana everywhere. That's the sanest suggestion (who's with me?):

ダイモンジトコモジヲムシスル

Of course, you're kind of screwed on a TTY, since they don't generally render unicode...so let's go back to figuring out which romanization system to use.

The Paperweight Dilemma: Original Pinephone might lose future kernel updates if devs can't pay down tech debt by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 18 points 11 months ago

I didn’t see any communities or articles talking about this, so either it’s not a big deal, or nobody is talking about it.

More than likely very few people own a pinephone, and the few that do don't read pinephone news. Thanks for posting this.

As for me, I'm not buying another pinephone/GNU+Linux compatible device until both the community and the manufacturer get their shit figured out. I bought the PInephone expecting it to one day become more useful to me, so I guess that's on me.

Firefox will support HEVC decoding on Microsoft Windows by Spectacle8011 in c/firefox@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 17 points 1 year ago* (last edited 1 year ago)

In about 5 years, the last patents for the baseline H.264 (AVC) video codec will expire. This means Firefox will finally be able to support decoding for H.264 (the codec most commonly used with the MP4 container) without Cisco needing to cover the licensing fees for them. DaVinci Resolve will also be able to support decoding/encoding on GNU/Linux. Basically, anyone will be able to implement a H.264 decoder/encoder without needing to pay royalties, which means free software programs like Firefox which don't charge their users will be able to implement it. The codec will no longer be patent-encumbered. See Wikipedia's debate on whether to support H.264 in 2014 for lots of opinions on this: https://commons.wikimedia.org/wiki/Commons:Requests_for_comment/MP4_Video

However, H.265 (also called HEVC) is the "next-generation" video codec after H.264. The patent pool situation is so confusing and expensive compared to H.264 that Mozilla, Google, Apple, Microsoft, Netflix, and dozens of other companies using video compression technology formed the Alliance for Open Media to develop a royalty-free codec they could use instead of HEVC. As a result, HEVC has seen very little adoption, particularly on the web. Most companies continue to use H.264. Windows 10 asks you to pay $0.99 for HEVC decoding support in the default video player. In fact, Google even announced they were dropping support for H.264 in 2011 because of their "focus on open web principles": https://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html

They never went through with it, of course.

AV1 is finally at a point where there are production-ready encoders and decoders. The iPhone 15 Pro is shipping with AV1 hardware decoding support, so even Apple is on board (though only for the most expensive phone so far). So, we'll see hardware decoding support in more phones in a few years, and hopefully AV1 will see a lot of adoption.

Adding support for HEVC in browsers feels like a step back because it legitimizes the codec and works against AV1 adoption. Many of these companies have resisted implementing HEVC support (aside from Apple) because it positions AV1 as the only realistic option to shift to from H.264. With HEVC in the picture now, it might be a realistic option in the future. Well, there's VP9 too, but there are some patent disputes over that codec that might make companies sheepish about adopting it. Not that AV1 is free from those disputes either, but they are far more confident about it and Unified Patents is doing great work invalidating Sisvel's AV1 patent claims (and even some HEVC patents here and there).

My opinion is that the ship has already sailed. Chrome caving in and adding HEVC support last year, albeit only with hardware decoders, was all it took with their 90%+ market share. Firefox's 3% market share isn't going to make a dent, and not doing it risks keeping users who need HEVC support on Chrome. I also don't think hardware decoding support is a big deal right now due to all the older devices without HEVC hardware decoders, but it opens the door to ask for more support down the line. I very much doubt Google is going to do that, though.

Video codecs: Adding AV1 stateless video decoder support to Linux by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 15 points 1 year ago* (last edited 1 year ago)

All in all, having AV1 support heavily benefits the open source community, as AV1 itself is an open source codec. This means that AV1 has a royalty-free licensing model that makes it suitable for adoption in various open source projects. It was also designed to solve long-standing patent litigation issues that were common in other codecs in the industry.

It was certainly designed that way. However, Sisvel believes that AV1 uses patented technology in the specification. Sisvel announced this one year after the AV1 standard was finalized, and not during the three years the standard was being developed. Of course, patent holders can't be expected to deeply investigate every new technology that's coming out on the market...but this was the largest new technology, formed by a coalition of some of the biggest companies in the world deliberately designed to get away from patent-licensing organisations like MPEG LA, under development for 3 years. Read into Sisvel (and its member companies) motivations as you will.

Nonetheless, Unified Patents is hard at work challenging invalid AV1 patents, among others:

Don't know who Unified Patents is?

Unified is a 350+ international membership organization that seeks to improve patent quality and deter unsubstantiated or invalid patent assertions in defined technology sectors (Zones) through its activities. Should Unified determine that its goals can be better served by settling a post-grant challenge (or agreeing to never file any challenges), Unified will consider settling in exchange for a license, though never for money. As with all aspects of its challenges, Unified acts independently when settling, and never provides members with advance notice of negotiations, draft settlement agreements, or actual settlement.

They also do...prior art competitions?

Unified is pleased to announce prior art has been found on three patents owned by Speir Technologies, an Atlantic IP Services subsidiary.

We would also like to thank the dozens of other high-quality submissions that were made on this patent. The ongoing contests are open to anyone, and include tens of thousands of dollars in rewards available for helping the industry to challenge NPE patents of questionable validity by finding and submitting prior art in the contests. Visit PATROLL today to learn more about how to participate.

In other news, more than half of the H.264 patents have expired, and all the essential ones will be expired by 2027.

5 years ago Valve released Proton forever changing Linux gaming by Spectacle8011 in c/linux_gaming@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 15 points 1 year ago

macOS has made it difficult for both game developers and Wine developers to support the platform by letting their OpenGL support rot, removing 32-bit support, ignoring Vulkan and coming out with their own graphics API, Metal. Wine is in a worse state than on GNU/Linux. There aren't many native games available for macOS.

That being said, your best bet is likely CrossOver. They employ the principle Wine developers, worked with Valve on Proton, and have put a lot of effort into supporting macOS. They've got a free trial with complete functionality you can try out.

But if the games you're playing have native releases for macOS, that's not something you need to worry about. There are just so few games available on macOS that I assumed they don't. Now, I only have an Intel iMac which I never play games on so I couldn't tell you how the newer ARM laptops perform.

Red Hat stops all upstream and downstream work on desktop Bluetooth, multimedia applications (namely totem, rhythmbox and sound-juicer) and libfprint/fprintd by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 20 points 1 year ago

Not Power Profiles Daemon...

Red Hat stops all upstream and downstream work on desktop Bluetooth, multimedia applications (namely totem, rhythmbox and sound-juicer) and libfprint/fprintd by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 18 points 1 year ago

Red Hat has decided to stop allocating resources for maintaining and improving these parts of the freedesktop project. Red Hat isn't working on proprietary versions of them. They've just decided to stop paying for work to be done on them. It just so happens that many of these projects were only being maintained by Red Hat employees, it seems.

HashiCorp changes license from Mozilla Public License 2.0 to Business Source License 1.1 on their products by Spectacle8011 in c/programming@programming.dev

[-] Spectacle8011@lemmy.comfysnug.space 21 points 1 year ago

Its still open source. You can still view the source code. That’s what open source is.

"Open Source" does not, and has never only meant, "you can view the source code". This is the Open Source Definition: https://opensource.org/osd/

Relevant excerpt:

No Discrimination Against Fields of Endeavor

The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

The Open Source Definition is very specific, and this license does not meet it. This license is, as it calls itself, "source-available".

If the OSI had obtained that trademark in 1999 on "Open Source", it would be abundantly clear what software really is and is not open source https://opensource.org/pressreleases/certified-open-source.php/

What is your opinion on GNOME 3 and 4? Why do you like/dislike it? by Spectacle8011 in c/linux@lemmy.ml

[-] Spectacle8011@lemmy.comfysnug.space 23 points 1 year ago* (last edited 1 year ago)

What I like:

I like GNOME 40 more than GNOME 3 because it's prettier.
I like GNOME in general because it's stable with pretty, high quality bundled programs.
I like the UX. It takes all the good things about the macOS UX and makes them better, while taking all the bad things and making them less stupid.
I like that they completely separate the dock from normal window management, so I never hit it when my cursor reaches the edge of the screen.
I like that you can set Nautilus to use one-click to open folders, even though that is cribbed from Dolphin. (Even if I use lf most of the time)
I like the simple IBus integration that lets me setup my Japanese IME easily.

What I dislike:

I dislike that I need a system tray extension for some software.
I dislike how in-your-face the notifications are and that they can't be stacked.
I dislike that I need to use Dconf to set shortcuts for workspaces 5-10.
I dislike needing GNOME Tweaks to set autostart software/daemons—this is a basic feature, not a "tweak".
I dislike not having an easy way to port my settings for GNOME to a new computer. It's annoying to have to set all this stuff up again compared to Sway, where I clone a repository and copy some config files over.
I dislike the new screenshot tool in GNOME 40+. It automatically saves photos to a directory, rather than letting me copy it. Come to think of it, I also dislike that it doesn't support the same screenshot protocols Sway does for grim and slurp, which is my favorite screenshot workflow.

17

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago* (last edited 1 year ago) by Spectacle8011@lemmy.comfysnug.space to c/japaneselanguage@sopuli.xyz

0 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

30

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/linux@lemmy.ml

2 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

10

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/linux_gaming@lemmy.world

7 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

14

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/linux_gaming@lemmy.ml

0 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

1

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/visualnovel@lemmy.ml

0 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

2

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/visualnovels@burggit.moe

0 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

10

[Guide] Playing Visual Novels on GNU/Linux (wiki.comfysnug.space)

submitted 1 year ago* (last edited 1 year ago) by Spectacle8011@lemmy.comfysnug.space to c/visualnovels@lemmy.comfysnug.space

2 comments fedilink

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/neo@lemmy.comfysnug.space. 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.

Has anyone used Kagi Search (search engine)? by Spectacle8011 in c/privacyguides@lemmy.one

[-] Spectacle8011@lemmy.comfysnug.space 15 points 1 year ago

My main search engine is Mojeek, and my secondary search engine is Kagi. I've paid for Kagi for over a year, and it gets good results. I think it's great that every part of both search engines work without Javascript, and that Kagi's results pages are very light. It's also cool that it returns results for pages in the Internet Archive, which can be useful for certain esoteric topics. I'm de-ranking certain sites so they're pushed to the bottom of results, like quora, twitter, w3schools, and reddit.

There are also no ads! At all! I used Duckduckgo in a VM today and it was dreadful how far you have to scroll just to get past the ads and see the actual results.

Kagi gets great results. My only problem is that, just like Duckduckgo, they use the Bing API. Now, Kagi actually uses their own non-commercial index Teclis, combined with their news index Tinygem, as well as calling Google's API and many other search engine APIs (including Mojeek). My main search engine is Mojeek because they use their own index.

I've found Kagi great for technical/日本語 queries, which is something Mojeek doesn't handle well. If I want to learn about a certain topic, I search Wikipedia directly. I think Kagi is the nicest and fanciest Bing/Google proxy around, with easily the best user experience of any search engine.

23

There's a 4-page manga about the Wikipedia mascot, Wikipe-tan (lemmy.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/japaneselanguage@sopuli.xyz

1 comments fedilink

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

Seiya-Saiga lists whether a physical VN runs "diskless", or without DRM (seiya-saiga.com)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/visualnovel@lemmy.ml

0 comments fedilink

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

Today I learned that Saiya-Saiga has a ディスクレス field for all the visual novels listed on the site. The field essentially labels whether the release is encumbered by DRM or not; whether it performs a check to ensure the disk is in the drive on first startup.

If the developer has provided a DRM-removal patch, as in the case of August with Aiyoku no Eustia, that is also listed with a link to download it.

This should be very useful for players looking for DRM-Free releases.

1

Seiya-Saiga lists whether a physical VN runs "diskless", or without DRM (seiya-saiga.com)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/visualnovels@burggit.moe

0 comments fedilink

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

Today I learned that Saiya-Saiga has a ディスクレス field for all the visual novels listed on the site. The field essentially labels whether the release is encumbered by DRM or not; whether it performs a check to ensure the disk is in the drive on first startup.

If the developer has provided a DRM-removal patch, as in the case of August with Aiyoku no Eustia, that is also listed with a link to download it.

This should be very useful for players looking for DRM-Free releases.

2

Seiya-Saiga lists whether a physical VN runs "diskless", or without DRM (seiya-saiga.com)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/visualnovels@lemmy.comfysnug.space

0 comments fedilink

Today I learned that Saiya-Saiga has a ディスクレス field for all the visual novels listed on the site. The field essentially labels whether the release is encumbered by DRM or not; whether it performs a check to ensure the disk is in the drive on first startup.

If the developer has provided a DRM-removal patch, as in the case of August with Aiyoku no Eustia, that is also listed with a link to download it.

This should be very useful for players looking for DRM-Free releases.

13

[Guide] Reading Visual Novels in Japanese (wiki.comfysnug.space)

submitted 1 year ago by Spectacle8011@lemmy.comfysnug.space to c/japaneselanguage@sopuli.xyz

2 comments fedilink

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

Anime has slowly grown into a global phenomenon, but visual novels are far more niche. Many visual novels remain untouched by localization companies, and sometimes the localizations we do get are…lackluster.

Often, the best way to experience a visual novel is in the original language—Japanese. Whether you’re already interested in learning Japanese, or want to learn Japanese purely to play visual novels in their original language, both motivations are perfectly valid. Visual novels are a great way to learn Japanese, because you get exposure to both the written and spoken language.

I've written a guide on how you can learn Japanese by playing visual novels with the help of a friend who made some suggestions to improve it, and it's available on our wiki, wiki.comfysnug.space. As with all pages on our wiki, it's licensed under CC-BY-SA 4.0, meaning you're free to share, remix, and build on the content.

If you're interested in learning Japanese or have already begun, I hope you find this guide useful. It isn't meant to be a dedicated guide on learning Japanese, but there are some tools you might not know about that will make your life easier.

If you have any additions or corrections to offer for this guide, or are interested in working on our other pages, you can sign up for the wiki here. You'll need to contact Neo on Matrix for a password as emails aren't setup yet (details on page).