Lol… well this is ironic

https://arstechnica.com/gadgets/2022/09/chromes-new-ad-blocker-limiting-extension-platform-will-launch-in-2023/

Starting in June 2023 and Chrome 115, Google “may run experiments to turn off support for Manifest V2 extensions in all channels, including stable channel.” Also starting in June, the Chrome Web Store will stop accepting Manifest V2 extensions, and they’ll be hidden from view. In January 2024, Manifest V2 extensions will be removed from the store entirely.

Google says Manifest V3 is “one of the most significant shifts in the extensions platform since it launched a decade ago.” The company claims that the more limited platform is meant to bring “enhancements in security, privacy, and performance.” Privacy groups like the Electronic Frontier Foundation (EFF) dispute this description and say that if Google really cared about the security of the extension store, it could just police the store more actively using actual humans instead of limiting the capabilities of all extensions.

The big killer for ad block extensions comes from changes to the way network request modifications work. Google says that “rather than intercepting a request and modifying it procedurally, the extension asks Chrome to evaluate and modify requests on its behalf.” Chrome’s built-in solution forces ad blockers and privacy extensions to use the primitive solution of a raw list of blocked URLs rather than the dynamic filtering rules implemented by something like uBlock Origin. That list of URLs is limited to 30,000 entries, whereas a normal ad block extension can come with upward of 300,000 rules.

Only if logging out actively invalidates session tokens, which appears to have not been the case. https://github.com/LemmyNet/lemmy/issues/3364

It’s a lot easier to shovel a foot of snow thrice than it is to shovel 3 feet of snow that’s compacted, melted down a bit, formed a freezing layer on top and ice on the bottom, and now your shovel is broke because you were trying to pry up that ice with 60lb of snow on top of it.

But at that point you say fuck it and just pay a guy to swing by with his plow and throw out some salt.

I appreciate the sentiment though.

Brain make people dumb

Exactly my reaction as well. The only ‘benefit’ she lists that I can truly see is ‘greater visibility into the code everyone else is working on’ but frankly that seems like it could be a burden as well.

Sometimes you don’t need to know. If your team organizes it’s projects and assignments well, you very well may be able to work on your small piece and integrate it without really needing to know every little thing every other person is working on.

With frequent commits branches just seem like an easier way to resolve conflicts as well as speed up the ability for others to test and merge their changes while you can resolve issues with a build.

Giving Nazis a platform is fucking cringe.

If you’re not familiar with it, windows now has native support to run Linux via the Windows Subsystem for Linux (WSL2). It can integrate pretty well into your environment as well, like pushing vscode applications to run in the Subsystem. It apparently supports gui as well although I haven’t tried setting that up myself.

Yes, it is very much a terrible idea. If you aren’t prepared to properly operate an instance, outside of making one for solely your own use, don’t.

IPv4 is the old standard of Internet Protocol addresses that you’re probably familiar with (something like 192.168.1.10, although the 192.168.x.x range is actually only private addresses). It’s still used on most devices today but it only supports up to ~4.3 billion addresses and as you can imagine, those addresses have basically run out with all of the various devices and servers and whatever else is connected to the internet. IPv4 is in the process of being replaced by the new (10 27* year old) IPv6, but there are still a lot of old devices and a need to support the old protocol. Making IPv6 available for this server will mean any devices connected to the internet should be able to communicate with the server on this new protocol.

As for DNSSEC, when you go to resolve a a hostname, like lemmy.world, your computer will make a request to a DNS server to figure out what IP address it needs to navigate to in order to access the server. In theory, someone could intercept your DNS request and tell you an address for the server that isn’t actually the address for the server, but rather a malicious host. DNSSEC basically acts as a layer of security to help confirm that information you’re getting on your DNS request is good and true.

I’ve noticed a few things going on with this.

If you’re viewing the image or linked url and simply click on the thumbnail for a direct link it doesn’t appear to recognize that post as having been read. You actually need to click on the title/comments to access the post for that to be recognized.

But beyond that, if you are viewing a post from your front page, it doesn’t actually reflect the post as having been read until you reload/refresh/restart the app. Even if you leave the front page to navigate into a community or profile it doesn’t appear to refresh this data to reflect what’s been read.

Strangely, clicking a link from within a given community rather than from your front page will reflect that post as read while going back from the post and viewing the community. But then returning to your front page from there still won’t have updated the post as read.

It’s a bit wonky and will likely be updated in the future but hopefully this helps you for now.

How does Redact handle the current API rate limits on Reddit? I’ve been using Power Suite Delete the past few days to purge my footprint and help incentive myself to move on, but every pass consistently has comments that aren’t overwritten because it’s hitting limits and moving on instead of queueing actions.

Also, I’ve noticed apparently not all of my account’s content is listed consistently which is why I’ve been running it for a few days now. Every couple hours a few new posts or comments are shown that were just nowhere to be found before.