Until this moment, I did the same thing… but right now I realize, this behavior incentivizes a domain owner to intentionally break their site, to trick the visitor to disable their blocker.
Then the browser: refreshes the page, downloadz all the thingz… presents cookie banner.
I’ve been using uBlock (or Brave) for years now, and when “something doesn’t work right” the first thing I often do is lower my shields… :facepalm:
From now on, I’ll just bounce. Keep your cookies, I’m not hungry.
> Wayland smells like IPv6 to me. No need to switch, and it hurts when you try.
I'm very happy with Wayland, but what a strange comparison to make if you're not. IPv6 is objectively an enormous improvement over IPv4, and the only gripe with it is that it's still not ubiquitous.
I’ll concede that IPv6 has usefulness on the public Internet, where adoption is actually gaining nicely. No issues there really.
However, my comparison is end-user focused (ie. the Linux desktop experience). I should have been more clear about the scope perhaps.
Both IPv6 and Wayland have increased complexity and surface area for pain (cost) without an obvious benefit for the end-user.
Also: wrt IPv6 specifically, I don’t believe every device on a private network should be publicly addressable/routable. To me that’s a bug, not a feature, and again does not serve the consumer, only the producer.
> Both IPv6 and Wayland have increased complexity and surface area for pain (cost) without an obvious benefit for the end-user.
I'd argue the opposite: IPv6 has lowered complexity for the end user: SLAAC, endless addresses, no need for CIDR – these are all simplifications for the end user.
> Also: wrt IPv6 specifically, I don’t believe every device on a private network should be publicly addressable/routable. To me that’s a bug, not a feature,
Some would argue it's a feature. But let's say it's not useful. It's still surely not a bug. An address being publicly routeable doesn't mean you have to route traffic to it. Just don't, if you don't want to.
> and again does not serve the consumer, only the producer.
I'd argue that it simplifies some things for the consumer (see above), and also lets the consumer be a producer more easily. I'd argue that that's a good thing, more in the spirit of the internet. But even if the end user doesn't care, it's not a detriment.
I agree with the parent comment. I have sway on my laptop, i3 on my desktop, I don't notice any difference. Well except sharing and annoying small sway things that works on i3.
Just as I am oblivious to whether this is posted over ipv4 or 6.
That they all have to implement the protocol seems like 20 years of wayland might actually have hurt Linux more than it fixed - without it something else would have happened. Think of how many man hours have been wasted doing the same thing for KDE, gnome, sway, hyprland, etc.
(also I agree about the publicly available thing, it's a bug for me as well. Companies will harvest everything they can and you better believe defaults matter - aka publicly available, for the producer, but they will say your security, of course)
It’s all fun and games until your ISP changes your prefix and breaks all your firewall/routing rules. I tried to adopt IP6 with Spectrum internet, but every time the cable modem reboots, my prefix changes and breaks everything. No thanks.
This doesn’t even come close to CodeCompanion[1], which doesn’t require any new LSP config/dependencies or filetype limitations.
There is no ability to share the current buffer(s) for context, no tool support. This seems like a checkbox release. You’re better off using CodeCompanion with Amazon Bedrock, which includes the added benefit of sovereignty.
CodeCompanion doesn’t have tab completion right? I love Neovim but Cursor’s tab completion is just next level and I haven’t found any nvim plugin that comes close to it.
Nvim 0.12 (prerelease) also has ghost text with the "textDocument/inlineCompletion" LSP server capability[1]. Currently supported by the "copilot" config[2], but any LS that supports "textDocument/inlineCompletion" can be used (and the config[2] shows optional QoL improvements).
I’m a big fan of durdraw[1] for crafting ANSI/ASCII art in the terminal, but this takes it to a whole new level, excited to try this especially if it includes color? From the website examples it doesn’t appear to include a color palette, but if it does then game on!
These images are top-notch, well documented, and have recently been refactored to use Selkies under the hood. Even with gamepad support, I’ve used these for running DOSbox, RetroArch, streaming video, and many other things.
There’s even a mature extensibility layer for using their images as a base layer to add services and apps.
Can’t speak highly enough of the linuxserver.io folks.
I actually wanted to try webtop for a long time, and did it only recently. I could not figure out these selkies for the life of me. It wanted a bunch of ports, was complaining about something all the time (don't remember, it's been a month). Might be a skill issue, but I've been using docker for the past 10 years.
Moreover they want root access to the host system, which kind of defies one of the reasons to use containers. Is there a video that explains the benefits in a good way? I mean, if it's for gaming only, I can understand the use-case, but say you just want to run something like Gnu Radio in a container, why would I need 60 fps and root permissions for that.
Then the browser: refreshes the page, downloadz all the thingz… presents cookie banner.
I’ve been using uBlock (or Brave) for years now, and when “something doesn’t work right” the first thing I often do is lower my shields… :facepalm:
From now on, I’ll just bounce. Keep your cookies, I’m not hungry.
reply