Hoping someone can explain this to me because I'm genuinely curious.
What is TLOU doing when it sits around for upwards of an hour, claiming to be building shaders, and telling me performance will be bad if I play while it's happening?
Is it just not possible to, say, prebuild and distribute whatever the final product of this build process is alongside the game like any other binary artifact?
Not even for fairly standardized hardware, like the Steam Deck?
Haven't played TLOU in a couple major updates, and now my poor Deck is building shaders again. At least I can stick it in another room and leave it on the main menu while it does, but jeez. I have no idea what they were smoking when they briefly claimed this was Steam Deck certified. What, someone brought theirs into the office one day during development?
@objectinspace Yeah, sorry, I know what a shader is. What I'm wondering is why they're being built on my device and, presumably, on everyone else's too.
Like, if you're building an executable for the game already, why not pre-build whatever this shader build process is creating and ship that with the game? Or ship it as a separate package that Steam downloads when, say, it detects that the game is running on a Steam Deck of which many identical versions exist?
I'm fairly sure the answer is something dumb, like "it's easier for us to just outsource the effort to everyone's device, and we'd rather skip on the extra storage/bandwidth costs."
Well that was stressful. Had to set up a dev environment for $dayjob. Each repo has its own README, along with an overall setup doc in a tool where I can't accessibly edit. Each of these docs was wrong in a bunch of subtle ways. One repo isn't even used anymore despite the overall dev doc claiming it was essential. At one point I asked in Slack if I should use X, only to have one person tell me yes and another no back-to-back. I'd be having major impostor syndrome right now if folks smarter than me didn't admit that they too don't even know how to start the whole stack reliably, just restart bits of it until the whole thing eventually works.
In the end I got it running. I ain't touching it anymore, and I'm not even sure which bit of dark magic was the key.
To paraphrase something I heard a while back, anyone who likes sausage or technology probably shouldn't look into how either is made.
@objectinspace It's not even git. There are a handful of things that may or may not need to run depending on what you're trying to do. We're trying to port from one thing to the other, and if you try to set up the other thing like normal, it does things that break the one thing if you try to set it up first. IOW, set things up in the wrong order and you either have to know exactly what you're doing, or nuke the whole thing from orbit and start over. Then there's the other other thing that the docs say you need but everyone in slack says you don't, which I spent a lot of time trying to get running unnecessarily. At one point I commented that we'd skipped past footguns straight to the whole foot arsenal.
Not enough weed in the world... Glad I have cool coworkers, this would be a whole lot worse if we believed in that year of efficiency bullshit.
Anyone have good UPS/APC recommendations for something that a) works with #Linux and b) would power a small form factor desktop for a few minutes but still leave time to shut down safely?
Heard back from the repair shop on the Proxmox box. The tech was unable to replicate my issues that look a whole lot like CMOS battery failure, so I guess power loss is wiping my BIOS settings in a way that pulling the plug doesn't seem to. I certainly have seen that inconsistency myself, so my hope is that keeping the power from just cutting out abruptly might be all that's needed to keep this thing going.
I'd like to pick something up in the next day or two, but don't know if I have the bandwidth to thoroughly research my options. And I'm finding a bunch of stuff with custom software, so am vaguely terrified that I'll end up with something that won't work with Linux. ~$200 budget, preferably something I can get on Amazon so it arrives quick. Server returns this weekend.
OK, let's see if Firefox 113 fixes whatever weird possibly accessibility-related slowdowns I experienced with 112.
Anecdotally, I remember hearing more "Loading"/"Busy"-style notifications under 112 than I was used to with nightly. Haven't encountered that yet on 113.
Nightly wasn't bad, but not having to update every couple days would be a nice change of pace.
Wow, the #HomeAssistant folks weren't kidding at all when they said this would be their year of the voice.
Each new release seems to bring exciting new voice features. The last few have made it possible to run everything from speech-to-text and better text-to-speech locally, or to fall back to the cloud for TTS if you'd prefer.
Digging in a bit more, it looks like they're building out a standard protocol called Wyoming to make everything, including intent handlers/skills, separate services that you can run locally and use across assistants.
They're selling a few $13 USB C-powered mics. Once this gets wake word detection, apparently planned for later this year, I'm all in.
@objectinspace@weirdwriter From a technical perspective, the fact that they're using Go probably indicates significantly lower resource usage when compared to Mastodon.
I'd like to eventually self-host my own server one day, but the thought of self-hosting Mastodon with its many moving parts vaguely terrifies me.
Haven't seen anything about this on the fediverse yet, but the PG13 folks will be streaming games from the recent Games for Blind Gamers jam in a little over an hour. Check it out--their streams are always a fun time. https://www.youtube.com/watch?v=tDBjPfOhFUo Enter a title
@objectinspace It was on my shorter list of projects to try and fix, but it looks like someone filed an issue, and some buttons were labeled last weekend. Hopefully that's all that was needed.
Well that was annoying. Last weekend Friendica started doing this thing where every post, including threaded replies, had an h5. Literally started happening within an hour or so of me posting about how accessibility had been improved. This made it incredibly difficult to keep up since I essentially had to read my entire feed, comments and all. And given Friendica's default mode of pulling in thread-starters that folks reply to and grabbing whatever thread context it can, I was about done.
Turns out Firefox nightly is doing this thing where it opens my history sidebar. Or maybe I am somehow and just don't know it. If as a screen reader user you've ever had to maximize a page to get all your controls back, it's like that, except maximizing made no difference.
Anyhow, it's fixed now. I wish I knew why this sidebar kept popping open, even though I have it set to not open unless I do it myself.
@Orinks Friendica is a mostly Mastodon-compatible system. It's been around over over a decade, so a lot longer. It's a lot more Facebook-like, though. So instead of just getting updates from people I follow, I'll sometimes see posts from other people that the folks I follow reply to, then I see their replies lower down. You can opt out of that if you want, but I like it as it tends to pull in more interesting things I might otherwise miss. Friendica also has events a bit like Facebook's. There are also groups, and one account can manage and share other accounts so you can have something like a Facebook page/group shared between several moderators. And you get a lot of control over what your account does--whether it follows other accounts back automatically, reposts everything from a specific contact, etc.
All these things work between Friendica instances, but they get a little weird when crossing over to Mastodon. Hopefully that gets fixed when Mastodon/AP natively supports more of these features.
@objectinspace I guess so. I suspect it narrows the page and triggers some sort of mobile/small screen CSS change that flattens out the threading and picks the smaller heading size.
@objectinspace I think it's the same issue I commented about on Twitch one night. The chat was missing even though the window was maximized, and I couldn't find the button to expand chat. I'm guessing the sidebar narrowed the whole page and Twitch prioritized showing the video over presenting chat. Chat appeared again when I closed the sidebar.
Of course, the only way I know the sidebar is open is if I tab into the page from the toolbar and find it. Guess how often I do that.
@fireborn Not sure if you've seen my recent posts on the subject, but I'd be interested to know whether it continues to feel faster for you after a few days.
Stable still locks up for me after a couple days or so of use. Nightly doesn't, and I go days between an update.
Anyhow, I'm trying to figure out if it's just me, or if maybe other CTW changes are in flight in 113 or 114 that might also be making a difference in nightly performance.
This may be an unpopular take, but...
I don't think any blind person will ever be completely independent. I do, however, think that every blind person can be self-sufficient. Independence, to me, implies a lack of reliance on anyone/anything. But everyone needs help sometimes. Self-sufficiency, on the other hand, is about having the tools you need, and the ability to get assistance, to go where you need to go/do what you need to do.
Thoughts? #Blind#Disability#Disabled#A11y#Accessibility
@JesseF8693 It's inter-dependence rather than independence, and it's true for all of us to greater or lesser extents. Wish I'd learned that when I was younger. I tried far too hard to be independent because that was the line I was fed, when in actuality I should have embraced the limitations that made sense and inter-depended.
Holy fuck do I hate GitHub CI so much. Just tried updating godot-tts and it vomited 4 errors. Basically what that means for me as a blind screen reader user is digging into the raw logs for each failed job, hitting pageup half a dozen times, and trying to find whatever error caused the job to fail amidst thousands and thousands of lines of inconsistently-formatted spew. If I'm lucky I can search for "error" but it's usually far from that simple.
I'm out. Today I'm resentful that this has been a thing multiple screen reader users have struggled with for years, and a multi-billion-dollar company can't be bothered to fix it. Just because someone tells me I have to try harder to do what able-bodieds take for granted doesn't mean I actually do.
Hopefully one of the other folks wanting this project steps up and fixes the errors. To be clear, I don't resent my users. I resent how this is a tool that piles of open source projects use, the UX for getting at errors probably takes me an order of magnitude longer to use, and I'm supposed to just take that in stride and try harder. Naw, not today.