Skip Navigation

Posts
3
Comments
106
Joined
2 yr. ago

  • It's a famous quote from The Call of Cthulhu.

  • I played it back in March 2012 after learning about it from a Let's Play (thanks Toegoff, if you're still out there, somewhere!). The comments recommended Katawa Shoujo, and, yeah, I went down a bit of a rabbit hole after that too...

    I've been digging through a lot of old anime lately looking for amusing lines and striking images and so on to post to various kbin/lemmy communities, and I guess something tickled my memory of this game, so I dug it up out of a backup of my old hard disk and fired it up again to get this screenshot. This line is one of the things that's stuck with me from it over the years.

  • This is the gag error message you sometimes get when you visit the 4chan parody in the VN called "don't take it personally, babe, it just ain't your story".

  • If you want minimal effort to get a good Linux setup for Steam, just buy a SteamDeck. Get the dock if you want to use it like a regular computer or console with a wireless gamepad. I did that -- hooked it up to my monitor, headphones, plugged in a mouse, keyboard, and my old XBox360 USB wireless dongle and it all just worked. I've got a few ideas for fun projects I want to try with it as a handheld and have written some software on it using desktop mode (little Python utility scripts for shuffling data around) but mostly I just use it like a gaming console; it works well for that.

  • Rule 9 from Agans's Debugging: If you didn't fix it, it ain't fixed

    Intermittent problems are the worst...

    • GLFW is intended to be built with cmake.
    • After unzipping the source, make a build directory, and configure glfw3
    • ^^ I like using ccmake to do this interactively, but you can also just pass flags to cmake if you know what they are
    • You should build with GLFW_USE_WAYLAND and GLFW_USE_OSMESA turned off to get it to try to build against X11.
    • You will probably also want to turn off GLFW_BUILD_DOCS, GLFW_BUILD_EXAMPLES, GLFW_BUILD_TESTS
    • You can adjust CMAKE_INSTALL_PREFIX if you don't want to use the /usr/local default install path.
    • After generating a Makefile, run make and make install
    • glfw3 generates a pkg-config compatible .pc file as part of its build process that lists flags needed for compilation and linking against the library. Normally, you'd just call pkg-config --cflags --libs --static glfw3 to get this info as part of your own build process (in a Makefile, for example) or else require glfw3 as part of a cmake-based build, but you can read what's generated in there if that program is not available to you for some reason. In case it's helpful for comparison, what I get with a custom build of the static library version of glfw3 installed into /usr/local on a slightly old version of Ubuntu is output like -I/usr/local/include -L/usr/local/lib -lglfw -lrt -lm -ldl -lX11 -lpthread -lxcb -lXau -lXdmcp but you may need something different for your particular configuration.

    Basically, something like this, probably, to do the compilation and get the flags to pass to g++:

     
        
    wget 'https://github.com/glfw/glfw/releases/download/3.3.8/glfw-3.3.8.zip'
    unzip glfw-3.3.8.zip
    mkdir build
    cd build
    cmake -D GLFW_BUILD_DOCS=OFF -D GLFW_BUILD_EXAMPLES=OFF -D GLFW_BUILD_TESTS=OFF -D GLFW_USE_OSMESA=OFF -D GLFW_USE_WAYLAND=OFF -D GLFW_VULKAN_STATIC=OFF ../glfw-3.3.8
    make
    make install
    
    pkg-config --cflags --libs --static glfw3
    
    
      

    If you want to just compile a single cpp file after building and install, you can do something like

     
        
    g++ main.cpp `pkg-config --cflags --libs --static glfw3` -lGL
    
    
      
  • Try compiling GLFW from source against GLX instead of EGL. If glxinfo is talking to a software implementation running on your system, I'd expect GLFW built to use GLX would use the same implementation on your computer.

    • You are running Wayland
    • Your GLFW programs are using EGL, not GLX, to talk to your graphics drivers/hardware
    • glxinfo is talking to a software implementation, not your hardware
    • glxinfo's output is irrelevant if you want to talk to your hardware with your current configuration; if you want to use the software implementation recompile GLFW targeting GLX and it should match that (but will be VERY slow).
    • One of your old posts describes your GPU as: Intel GMA3100 (G31) -- is this the same system you're running on now? If so, that is ancient. It looks like that came out in 2007 -- which predates the existence of OpenGL 3.0; so, getting 2.1 as the newest context available when talking to actual hardware is not surprising...
  • I've used Wireshark when I want to inspect the traffic going through my computer. I've found it particularly handy for debugging my own networking code. I've also used netstat to see active connections and programs listening for traffic when I don't care about the packet contents specifically.

  • I think it's probably an Indian English-ism. It's understandable but sounds weird to speakers of American English (and maybe other English dialects).

    A more natural sounding title (to an American English speaker) would use "Microsoft is making" or "Microsoft is planning to make" rather than "Microsoft might want to be making".

  • With that said, can I possibly only allow traffic to and fro from the proxy through my firewall?

    Yes. That is what I suggested. If you configure the firewall to only allow traffic to/from the specific IP and port combination of your proxy, other traffic will be blocked.

    I should be able to (in theory) inspect traffic too, although I don’t know how far that will take me.

    You can do content filtering via a proxy like that, yes. A similar sort of configuration is used on school computers to do things like block adult content, with varying degrees of success. Some ad-blocking techniques work on similar principles.

  • If I understood your question correctly, you'd run the proxy application (which might be Squid or Apache or some other program) either on the host computer outside the VM or elsewhere on your network. (I'm not well versed on all the ins and outs of setting Firefox up to communicate through a proxy; I just know it can be done.) The proxy would listen for incoming traffic on a specific port you configure. You then tell Firefox (in its network settings) to communicate with the specific IP and port of the proxy instead of talking to web servers directly.

    To prevent other programs from communicating, you'd firewall off the VM with iptables (or maybe ufw or something else depending on what you use on your system). You'd set it to drop all traffic going to/from the VM's network except packets going to or coming from the specific IP/port combinations you want to allow.

    This isn't a bulletproof way to block other apps from talking to the internet -- anything that knows about the proxy (or which can hijack/manipulate a program like Firefox that you've told about the proxy) could communicate with web servers via the proxy, but depending on your specific concerns it may be good enough.

  • You could try configuring Firefox to access the internet through a proxy and then block the VM off from everything except the proxy and your network mount with a firewall (outside the VM).

  • For anyone who just wants to know what component: they want to drop the influenza B/Yamagata variant of the flu virus since it appears to have gone extinct in the wild.

  • It's preinstalled if you buy a Steam Deck -- which by default runs a corporate backed (i.e. by Valve) Arch-derived distro called SteamOS. I bought one. If you hook it up like a regular computer (plug in mouse, keyboard, and external monitor with the dock) damned near everything I've tried has worked acceptably. Some games need a little fiddling around (e.g. installing video codecs or CJK language support or changing the proton version from the default setting to "experimental") and I've run into bugs with full screen or the on screen keyboard a couple times, but I have yet to find a game I straight up could not play even if it was marked as unsupported. (I expect some games with obnoxious DRM/anti-cheat or that need ridiculously powerful cutting edge GPU specs probably wouldn't work well though, but haven't really tested the limits in that direction.)