CalcProgrammer1 @ CalcProgrammer1 @lemmy.ml

Software Engineer, Linux Enthusiast, OpenRGB Developer, and Gamer

---

Read more

Posts

0

Comments

452

Joined

4 yr. ago

I thought their reputation was tarnished explicitly due to uploading footage to the cloud despite claims otherwise. How can you be sure it isn't uploading when their words mean nothing?

Hacker's Keyboard is the only keyboard app I'll accept on Android.

Drastically nerfed the quotas. FOSS projects with a valid license used to have GitLab Premium access to shared runners and now even FOSS projects with a valid license get a rather useless 400 minutes. They also require new accounts to add CC info just to use that paltry sum which means FOSS projects can't rely on CI passing on forks to ensure a merge request passes the checks before merging, as even if you have project specific runners set up forks don't use them and neither to MRs.

I wish companies didn't offer what they can't support from the beginning rather than this embrace, extend, extinguish shit. I guess in GitLab's case there was no extend, it was just embrace FOSS projects and let them set up CI pipelines and get projects depending on the shared CI runners as part of merge request workflow for a few years and then extinguish by yoinking that access away and fucking over everyone's workflow, leaving us scrambling to set up project side runners and ruining checks on MRs.

The stupid thing is mutter-vrr works far better than Plasma's implementation in my experience. Plasma locks refresh rate to max if your cursor is moving, causing games that use the cursor to stutter badly while the mutter implementation refreshes the cursor at the game's rate as expected.

I still left my old and unmaintained projects on GitHub but I moved all my active projects to GitLab and any new projects go there too. I have them auto mirrored back to GitHub though as the more mirrors the better. I also recently set up a Codeberg mirror for some of my projects, though GitLab's CI is what is keeping me on GitLab even though they nerfed the shit out of it and made it basically a requirement to host your own runners even for FOSS projects a year or two back. Still hate them for that and if Codeberg gets a solid CI option, leaving GitLab would make me happy. They too have seen quite a lot of enshittification in the years since Microsoft bought GitHub.

I've used Raspberry Pis since the first model came out and other SBCs and the lack of RTC has never really been an issue. The Pi syncs time by the time it makes it to the desktop. I can see it being useful for early boot timestamps but the most useful such log (dmesg) is just elapsed time since power on anyways. I can also see it being useful for devices doing data logging without Internet or regular power supply like a remote sensor logging device. I guess I just don't see it as a crucial component of a home router. I agree it's a cheap and useful addition though, just not maybe the most essential of one.

Interesting, though I question why a battery backed RTC is seen as so critically important. Of all the features I can think of wanting in a router, a battery backed RTC doesn't even begin to make the cut. A device that is powered up 24/7 and connected to the Internet can just get NTP time whenever it boots up and keep time using the OS. What is so necessary about an RTC here? I get that time is used for certificate verification and other security stuff, but again NTP and always powered. Are they concerned that NTP could be an attack vector?

I'm interested in a new OpenWRT router as my WRT1900ACS is getting older and the WiFi driver on it never had amazing support. Right now the Banana Pi R4 looks promising as a WiFi 7 OpenWRT supported router as it looks like most off the shelf WiFi 7 routers do not have OpenWRT support.

I started using gyro on the Steam Deck recently. It is pretty good for fine tuning your aim. I have been playing Overwatch with it and while nowhere near keyboard and mouse, it's noticeably better than gamepad alone. I can still only play a select few characters with it though.

Hacker's Keyboard is a good Android keyboard for doing terminal stuff. It adds a lot of the keys you need to efficiently work in terminal. Only Android keyboard worth using.

Sodium ion sounds like a very promising battery tech for a lot of things due to sodium's abundance and ease of access, but it's less energy dense than lithium so I still see lithium battery tech being king in most applications where battery size and weight matter - portable electronics and EVs mostly. Sodium ion tech sounds best suited for grid-scale energy storage, home backup/solar batteries, and other such applications where cost is more important than size or weight.

I'm in the middle and I don't always like it. 100% coverage is mandatory for the industry I work in though. I get that module testing is important but it can be such a chore to work on. I got pulled in to help write tests for another project this month and that is somewhere between watching grass grow and watching paint dry in terms of level of excitement.

Also fork the repos. Git makes duplicating a repository simple, and preserving history with a fork is way better than uploading a zip snapshot. For best results fork to GitLab, Bitbucket, Codeberg, etc. as well.

Does this change run the 32-bit .exe using x86_64 instructions? From the description it just sounds like it allows 64-bit Linux libraries to be used in place of 32-bit ones, but that the Windows layer still operates in native 32-bit mode. This means there is still a need to emulate 32-bit x86 instructions which I don't think box64 can do at this time (x86_32 translates to arm32 with box86, x86_64 translates to arm64 with box64). If box86 could translate x86_32 to arm64 then this might work as Wine would handle the conversion between 32 and 64 bit addressing and argument passing into the libraries but I'm not familiar with the inner workings there.

Hacker's Keyboard on Android and I created a custom Squeekboard layout for my Linux phone.

I make a point of using smartphone onscreen keyboards that have these keys. They are too useful!

This should allow nouveau to reclock NVIDIA 2xxx and newer GPUs. Huge step forward for open source NVIDIA drovers and I've been testing this on my laptop for a few weeks now woth the rc kernels and the NVK driver and it's pretty impressive so far.

I mean, they have the money. They could build their own fiber network. They already have the permits, pole access, equipment, maintenance network, distribution network, utility boxes, etc. that they could leverage to build a truly modern network infrastructure in parallel to their outdated coaxial one if they wanted to stay relevant in this century, but they don't. They stick with their shitty cable and its shitty uplink limitations and let much smaller third parties spend all that money to get their own permits, equipment, etc. and build their own fiber networks that can actually deliver the performance people want. Then Spectrum cries like the crybaby they are when everyone abandons their ancient infrastructure when competition arrives. Hell no I don't want to stick around for your lame "gigabit" cable with a pathetic 20mbps uplink.

I had to yell at them on the phone to cancel when I switched to symmetric gigabit fiber last summer after over a decade of 200/20 Spectrum. They said "but wait we can offer gigabit too" and I said that what they were selling was theoretically impossible to match what I had. Garbage company selling inferior product. I'm glad they're starting to see real competition in more and more places from smaller fiber companies.

But it's way easier to find a phone with a micro SD slot than either of those. Mini SD was a thing and it was very short lived.

I've been very happy with my Arc A770, it works great on Linux and performs well for what I paid for it.

NVK is changing things for the better on NVIDIA. I tested it out the other day on my RTX3070 laptop and a lot of games are already playable. Performance has a ways to go to match the proprietary driver but it's incredibly refreshing to see modern games running playably on an open source driver stack on an NVIDIA GPU.