May we see it?

Reader Rabbit

GOG, basically. Which feels a bit ironic given Heroic covers GOG

Well I thank you for your contribution regardless. Roku is all I’ve got, so it helps to have people like you annoyed enough, and knowledgable enough to contribute.

It occurs to me I’ve literally never tried to play my music library through Roku. I usually just cast to a speaker with my phone. Is it part of the main branch?

I see this comment every now and then, and it always forgets the cost of the transaction, confirmation time, and of course, the need for miners to exist to process these confirmations/transactions. The energy cost is extraordinary, and the end user is taxed for the use of their own dollars.

It’s not really feasible on a broad scale. Bitcoin is a holding stock, not a valid currency. Its value only increases because it manufactures its own scarcity. And as its scarcity increases, it naturally moves toward centralization since mining becomes too large an activity for the individual to reap any benefit. You can argue for proof of stake to eliminate the need for mining, but then you open the doors to centralization more immediately.

If I’m remembering right, RHEL is Crowdstrike’s primary Linux target. And NixOS wouldn’t even be a factor since it’s basically just not enterprise grade.

That said, they need a serious revision of their QA processes.

No problem, glad I could help!

Arm64 is generally appropriate for most modern phones. Armeapi is targeted at 32-bit arm devices. These are uncommon these days. X86 is rarely used with Android devices, since it’s broadly unsupported.

Of course Universal is as described, and should work if you’re still unsure.

Imo, plugins should have separate config files, with uniform, consistent formatting. Separating them ensures that plugins never modify primary configuration details, they can be updated independently, or deprecated without affecting future functionality. It also means you can take regular and reliable backups of each config.

Hey there, I’m not sure I understand what you mean by “first activated”. In general, you activate a SIM card, not a phone. This would be associated with your current phone plan, not the device itself. Your carrier would be able to provide that info. If you’re referring to when your phone was first purchased/turned on, then most folks tend to add their Google account during setup, which might be why there’s a suggestion to check your Google account to see when the device was added.

The IMEI is potentially useful as it’s a device identifier, but generally doesn’t matter to anyone except your carrier.

As far as I’m aware, Samsung or Amazon are the only other real app “marketplaces”. Most developers using Fdroid otherwise rely on donations or patreon for active development, depending on the nature of the app

When people refer to a particular piece of development aoftware as closed or open source, they are referring to the license/availability of that software’s code. You can use proprietary software to produce open source code, which is the case with Android Studio. The code that makes up Android Studio is not open source, but your own work made within it can be.

In general, “open source” is a broad term that just means “can I see the code that made this?”. There are differing degrees of open source software as well. The MIT license, for example, opens up code to some modification/re-use but protects some libraries. Something like a BSD or GPL license is far less restrictive, usually allowing free modification and use of the code. Android Studio falls under the Apache license, one of the more restrictive licenses that still applies copyright, and may employ proprietary libraries that cannot be modified or copied for use. Again, this ultimately isn’t likely to affect your own work or projects, but it does mean there’s less transparency about the tools you are using to make it.

I apologise if this is overwhelming, but the distinction is important, and I think that as a beginner it makes sense to start with where there is the most documentation and ease of entry. Once done, it’s definitely easier to move towards projects that more closely align with FOSS philosophies.

Android Studio is just the work environment for code and app development. You could continue on to publish all your code/work as an open source application through whichever means you choose during or after the fact.

Imo that’s fine. It’s also still the best tool for learning since it’s the most widely supported one, and contains the greatest amount of documentation for working with android development. It costs nothing to use, and doesn’t lock you into any kind of ecosystem you can’t later migrate from.

Android Studio is the primary toolkit for developing native android apps. If you have no background in programming, there are some more visual tools like Budibase (open source) or Softr (closed source), but you are likely to run into difficulty getting them to apply logic the way you’d like.

If you’re a tinkerer, then honestly I’d look into learning more about Android Studio and Kotlin, the language most used these days for app development on Android.

Also worth noting is their history as an IP mill. Dead By Daylight is a surprise hit amongst many a licensed deal to produce games that would nearly qualify as shovelware in most cases over the last 20+ years. DbD gives them some independence, but they’re still largely a “studio for hire” by anyone who needs them.

While true, I think buying into a proprietary memory format that hasn’t been formally made an open standard is something you have to accept some risk on. CAMM is cool as hell, but it never made it this far.

It’s quite good. It helps a lot with making minute adjustments to aim that the control sticks can’t quite manage without dropping sensitivity substantially.

The controller has gyro, and games like Horizon Zero Dawn/Forbidden West do make use of it. There are others as well, but I’m not familiar enough with the library to recall specifics