

🚀Grow your followers ‼️NOW‼️with 3 easy payments of 1 brain rot! 📈
🚀Grow your followers ‼️NOW‼️with 3 easy payments of 1 brain rot! 📈
And their refusal to listen to what the fans actually want.
And frivolous patent lawsuits on mechanics that they don’t use themselves. Or patents they made after said prior art came out.
And sending their lawyers after streamers and content creators.
And killing fan games that improve on their failures.
And artificial digital scarcity.
Their arrogance will be their downfall.
You mentioned a buzzing in another reply. That sounds like a grounding issue to me. Any chance you blew something under the board that is causing a short? At this point it would be wise to do a full tear down.
I’m almost at my train stop, so one final question before disappearing for the day: when resocketing the CPU did you put it in correctly and was there damage when you removed it initially?
Is the power switch on the PSU flipped on? Are the front panel wires seated in the right places on the motherboard?
Those are the two that get me when reassembling. I used to have an asrock 320m that had absolutely no grip on the front panel wires and it was easy to unseat one when blowing air into the case.
Those are TestFlight notifications you’re getting. If you don’t want them, quit testing and grab it off the App Store instead.
Archive is on American soil. They got sued for lending ebooks during the pandemic and lost, so they are not a safe bet. Archive elsewhere. Anywhere else.
Try searching for a “cross section” image, which should give you slices of the tree.
Tbh I’m not a web person (more of a backend person) and don’t know the recommended practices. display: grid;
is a good friend of mine xD
Tests? Pfffft. I am the test.
And while I’m here: https://blog.jim-nielsen.com/2024/sanding-ui/
Right now we have no other solutions/fixes. You may be able to get Invidious working on residential IP addresses (like at home) but on datacenter IP addresses Invidious won’t work anymore.
This might explain why mine has been reliable even though it hasn’t been updated in months. I guess add me to the list of confirmations that it works on residential connections.
The answer has got to be helix
;)
Forking is indeed the way forward when Mozilla loses its way a little more. For myself, I switched to Librewolf about 6 months ago, along with replacing Thunderbird with Betterbird after using it since the Phoenix days.
I cannot remember what prompted the move to Librewolf, it may have been the AI stuff they were pushing at the time, or possibly the update that forced the tabs into my titlebar without having to go into about:config to fix it. Or the fact that Firefox was constantly pushing me to sign up for an account. There were quite a few gripes that added up over time lol
Betterbird restored some removed things I liked pre-supernova as well as a native systray icon under Linux and that was enough motivation to make the switch.
It is time for a new browser to enter the market. Either Ladybird or something built with Servo seems likely.
I’ve got some bad news for you. Mozilla bought an ad company.
Have you looked at Duplicati? I use it and find it dead simple and reliable (I did a full recovery from a total data loss last year).
Someone will likely share it for preservation purposes soon enough.
Apple confirmed that the Epic Games Store for iOS in the EU compiled with most of its guidelines, but it had an issue with the “a download button and related copy”.
Apparently, Apple felt that the download button and related copy might mislead users into thinking they were made by the iPhone maker. While Apple has approved the app, it wants Epic to make the changes before the next app review.
There’s the catch. Emphasis is from the original article.
Don’t worry about seeming dumb or noob-ish. Everyone starts somewhere. How can we learn without asking questions or making mistakes?
The /r/selfhosted wiki is still amazing and you might learn the terminology needed to turn your “stupid questions” into smart ones :)
I think about a feature or bugfix that I want to work on, then shoehorn it in by any means necessary. Once my code is confirmed working, the planning phase begins and I go through the module(s) I’m working with line-by-line and match the original author’s coding style and usually by that point I pick up a trail or discover a bunch of helper functions/libraries that I can use to replace parts of my code, and continue from there.
As others have said, configuration files is a great way to learn that. Pick a config option you want to learn about, jump to the config loader, find where the variable gets set, then do a global search for that function. From there it starts to fall into place.
Sidenote: I also learned rust this way. It took me around 6 months to learn the rgit codebase solely from adding features that I wanted from cgit. Now I’m at the point where rebasing from upstream to my soft-fork doesn’t mess up any of my changes, and am able add or fix things with relative ease. If memory serves, a proper debugger (firedbg is excellent!) was used on several occasions to track down an extremely annoying and ambiguous error message that was due to rust’s trait system being a pain in my ass.
Inline diagnostics was implemented earlier this year, and is still not enabled by default (likely to prevent breaking existing configs). The changelog is from January of this year:
https://helix-editor.com/news/release-25-01-highlights/
You can set it up here, and is straightforward:
https://docs.helix-editor.com/editor.html#editorinline-diagnostics-section