• 0 Posts
  • 38 Comments
Joined 3 years ago
cake
Cake day: August 15th, 2023

help-circle
  • I like using e-reader because it’s cheap, better on the eyes, the battery lasts forever, and generally screens are bigger than the phone. Also not killing your phone battery showing text is a plus.

    I’ve been kicking around a couple of nook simple touch for several years. it’s ancient, android 2.1! It was easy to jailbreak them and add a launcher, and a couple sane ebook readers (though you’ll have to find older versions of apps that will work with eclair). pop stuff on it over usb, and it’s on there. The ones with backlights are getting super rare, but if you don’t care about that you can probably snag one for round $20 places like ebay.

    Really can’t beat that, costs more to get a power bank to keep from killing your phone reading things.



  • boot/efi partition is where boot info/startup logic goes, but windows makes a very small partition (only 100mb) on setup, so between windows and bazzite data, there is not enough space.

    It will install the system in the 500gb partition, but will not boot without the proper data in the boot/efi partition. The installer is warning you of this situation, and the install will probably “work” but most likely be unbootable, or if it does work, cause problems later during bazzite updates.

    There are partition management programs that can boot into a temporary environment and move/resize existing partitions so you can grow the existing EFI partition, but there is no tool built into windows for such a maneuver.



  • Grntrenchman@sh.itjust.workstoLemmy Shitpost@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    4 months ago

    See link with interesting title.

    Look at actual domain, if it’s *tube/invidious immediately skip over link.

    Click, see it’s loading (any) video site.

    Immediately close page.

    Skipping some steps here, usually fast enough that you don’t even have to hear voice.

    If you won’t write it out in text, it’s not worth receiving the information.



  • I prefer appimages, it feels much more “open” than flatpak ever will.

    Flatpak: install flatpost and flatseal.

    Appimage: Download appimaged appimage to ~\Applications and run once.

    then

    Flatpak: Go to site for cool software I heard of, see it’s flatpak with a link on the page. Click link, wait for flatpost to open, wait for flatpost to update repos, get cool software and possibly another copy of mesa and gnome compat stuff, then head to flatseal to fix drive/device permissions as needed.

    Appimage: Go to site for cool software I heard of, see it’s an appimage, download said appimage to ~\Applications, appimaged automatically loads in a desktop entry and we’re done.

    As far as updates, all the appimages that are in active development that I use, offer auto-updating when I open them, plus I’m not reliant on a centrally-controlled repo of the packages (which if it dies, takes all updates with it).

    I feel appimage would be an easier adoption for people fresh to linux, as it follows the same model as windows or macos (download executable, install app), even for the initial setup of appimaged.

    And either way, there’s no “winner” here, if we’re playing that game, native installs still win. Every distro supports (and uses) those by default, except for ubuntu, who has money on pushing snaps.


  • I tried different guides, and eventually went to the source, this worked great for me.

    From SE Discord, posted by “lord.of.woe”:

    Space Engineers Linux Installation Guide Last Updated 2025-07-24

    Prerequisite Packages

    git

    wget

    WINE

    Step 1: Install GE-Proton9-25 and GE-Proton10-X. There are several methods you can use to install this, but this guide uses only common terminal commands. (Edit: I used Protonplus for this)

    wget -qO- https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton9-25/GE-Proton9-25.tar.gz | tar xzvf - -C "${HOME}/.steam/steam/compatibilitytools.d"
    wget -qO- "$(curl -s https://api.github.com/repos/GloriousEggroll/proton-ge-custom/releases/latest | grep "\"browser_download_url\": \".*\.tar\.gz\"" | cut -d'"' -f4)" | tar xzvf - -C "${HOME}/.steam/steam/compatibilitytools.d"
    

    Step 2: Remove local Space Engineers data. ‼️ WARNING: THIS WILL PERMANENTLY DELETE ALL SAVES, GAME DATA, ETC. THAT ARE NOT BACKED UP TO THE STEAM CLOUD OR ELSEWHERE. ‼️

    export STEAMAPPS_PATH=${HOME}/.steam/steam/steamapps # edit as necessary
    rm -rf ${STEAMAPPS_PATH}/compatdata/244850
    

    Step 3: Restart Steam

    Step 4: Change the compatibility layer in Steam to GE-Proton9-25.

    Step 5: Launch Space Engineers in Steam and close the game upon reaching the main menu.

    Step 6: Install dotnet48. DO NOT USE PROTONTRICKS.

    WINEPREFIX=${STEAMAPPS_PATH}/compatdata/244850/pfx winetricks --force -q dotnet48
    

    or experimentally

    WINE=${HOME}/.steam/steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64 
    WINEPREFIX=${STEAMAPPS_PATH}/compatdata/244850/pfx ${HOME}/.steam/steam/compatibilitytools.d/GE-Proton9-25/protonfixes/winetricks --force -q dotnet48
    

    Step 7: Change the compatibility layer in Steam to GE-Proton10-X, where X is the minor version.

    Step 8: Launch the game and hope everything worked.



  • Hard no.

    We loved the first, but the second adds the stupid infection thing, and was in the “ok, playable” pile at the start, but all the glitches and bugs made us stop. Between day/night not working for non-hosts, buildings with huge map holes in them, and very poorly scripted quests we dropped it. The final straw was when we were doing side stuff, ignoring the main mission, and passed over a building that was part of a later stage in the main mission, causing us to softlock, then on restart being at the later step in the main mission. Just trash programming.

    If you really want to play it, pirate it. Don’t give money for it.









  • For Android: learn the hard reset combo for your phone, especially if you encrypt it.

    After rebooting, pattern/PIN will be required to decrypt the phone. Biometrics won’t work for this step. This is what graphene does for security, tries to keep the phone in a “before first unlock” state by rebooting on a timer. You can’t even read anything over USB/ADB, it’s scrambled until you unlock the phone.

    The only drawback to just keeping your phone in this state is none of your apps are loaded, so no notifications/updates/processing at all.