https://blog.jim-nielsen.com/2023/html-web-components/ - Jim Nielsen has a series of posts on how to use made up HTML tags in a way that doesn't just fail to nothing when the javascript defining the custom-element doesn't get successfully executed.
Some of these new HTML features don't fully work in my "ancient" browser. But all of them partially work (ie opening the accordion element doesn't close others but it still opens and closes) and they still remain functional elements I can read and interact with. This puts them far ahead of any javascript implementation which almost universally fail to nothing.
For corporations, institutions, and for-profits this matters and there's no real good solution.
But for human persons and personal websites HTTP+HTTPS fixes this easily and completely. You get the best of both worlds. Fragile short lifetime pseudo-privacy if you want it (HTTPS) and long term stable access no matter what via HTTP. HTTPS-only does more harm than good. HTTP+HTTPS is far better than either alone.
I think your only defense would be to pretend to be a bot at this point, because what you just said was completely ridiculous and embarrassing. You realize it's not a requirement that you have to post a comment when you have no idea what to say?
The people who absolutely have to have X11 like myself usually have reasons. It sounds like currently a lot of those reasons for using X11 would prevent using this X server. Like reliable non-fragmented and widely supported screenreader protocol. Or the ability to do keyboard and mouse sharing.
>Applications will be isolated from each other by default and can only interact with other applications either through a GUI prompt asking for permission, such as with screen recorders, where it will only be allowed to record the window specified or by explicitly giving the application permission before launched (such as a window manager or external compositor).
Accessibility? Sure. Everything else? Nah, I'm sorry. There are countless ways to do remoting with Wayland. There are countless ways to do kb+mouse sharing.
I love Wayland a lot, but as far as I can tell the available remoting solutions still cannot enable a headless LXC container to serve a KDE Plasma Wayland desktop. I spent the last couple days trying to cobble some solution together for it and failed miserably. If you know a way, I would be most grateful :-)
You realize that's worse, right? And to be clearer: core Wayland protocol does not have countless ways. It has zero.
Instead of a single protocol with the strong X11 reference X server the wayland compositors pick and choose between libinput, or libei, or libportal with the InputCapture PR, xdg-desktop-portal with the InputCapture interface, some I've probably missed, or maybe you have nothing at all (weston). It's a gamble if your choice of desktop environment and it's wayland compositor's non-core wayland protocols will match up with those the developer for $software chose. On X11 linux everything that works somewhere works everywhere. With the various waylands if you stay within your desktop's ecosystem you'll probably not notice, but go beyond it and you will.
Each wayland desktop pretty much runs it's own compositor with it's own set of third party libs because the wayland core protocol spec is very minimal. I would say incomplete. ref: https://wayland.app/protocols/
I mean, at least with web browsers they usually converge on a common spec eventually, and most of the time you just have a bit stupid repetition in your CSS for a bit. Wayland compositors seem to be actively against this kind of process.
It's a very forced comparison trying to swap in the web's security model, where one runs untrusted code from arbitrary third parties automatically, for a personal desktop computer context where a single user is in complete control.
Uh... lived experience? Try getting keyboard and mouse sharing working across all the waylands with the same software. Not having most of the features in the standard implementation leads to fragmentation which apparently you haven't run into with your use cases yet.
For nvidia increasing the numbers of their money-multiplying mutual investment ring is more important than the value of the deals. It's about involving more capital and people and making their grift too big to fail and keeping the stock numbers up. Nvidia has the ability to promise large amounts of money like this in announcements but I haven't read about any of them actually having money or good exchange hands yet.
The problem with this is that NPU have terrible, terrible support in the various software ecosystems because they are unique to their particular soc or whatever. No consistency even within particular companies.
>Making changes can be done with just normal git commands, eg git commit. Many Debian insiders working with patches-unapplied are still using quilt(1), a footgun-rich contraption for working with patch files!
Huh. I just learned to use quilt this year as part of learning debian packaging. I've started using it in some of my own forks so I could eventually, maybe, contribute back.
I guess the old quilt/etc recommendation in the debian build docs is part of the docs updates project needed that the linked page talks about.
Rydberg atoms aren't antennas. When modulated and then read out by the electrical field of a laser they can be used to infer the ambient electrical field at a arbitrary frequency over very, very narrow frequency bandwidths. This can be used to receive radio signals. But it's not very good at it and it's not an antenna. While the specific frequency can be tuned over a very large range the instantaneous bandwidth is still too narrow to actually receive anything but narrowband carrier (no modulation wings) and barely that.
These are physics tools for specific things, not general radio receivers for transmitted information.
Yes, what is really needed is a way to baseband a good swath of spectrum, e.g. in the neighborhood of 100MHz to 10GHz, so that conventional electronics can be used to study something more than simple low rate there/not-there activity. And conversely a way to modulate similar bandwidth onto arbitrary frequencies up in the THz region.
The same way an LED is not a solar panel. It will give you some voltage, but basically a rounding error above zero.
Antenna are about capturing energy over macro scale areas. This atom is measuring electromagnetic oscillation at a particular point in space. Technically you can recover a signal, but only a rounding error above the noise floor. It doesn't capture energy.
Yeah. I see this in every thread. Business types that aren't used to how normal human beings communicate see the human firefox users writing and they can never address the points. Instead they always get hung up on the tone and debate over the irrelevant tone becomes the primary/top thread in HN FF posts.
The post lists a number of ad-tech moves Mozilla has made in recent years, the ever increasing upper management salaries, and the insistence on trying to make Firefox preprocess everything you see on the web instead of showing you the web itself (AI).
I personally agree with these complaints. I think most people who intentionaly install Firefox agree with them. Despite all it's attempts otherwise, Firefox was and still is mostly used by "power users" and we're pretty much the only ones left that intentionally install the browser. Mozilla being the only working alternative to Alphabet domainance over the web doesn't change the validity of these issues. The real issue here is that Mozilla wants to be HUGE instead of just being a browser for humans.
I'd been a Firefox user since K-meleon (with a gap decade when Opera was actually a real browser and innovating). But for me the breaking point wasn't all this ad-tech stuff or the signalling of AI. It was when Mozilla showed they no longer cared about their core userbase and wanted to chase after demographics that didn't care about browsers at all; when they made the security theater Add-ons signing portal in version 37 and made it so one could not edit or install such things without Mozilla's central and continued approval (also, baking in 3 year expiring add-on certs making FF trial-ware). These days, for me, it's just a fallback for my bank. I use a Firefox fork for my main browsers which is much more Firefox than Firefox.
That's a clever way to get a lower bound for power users. I'm surprised. But also, I did qualify my statement and said people who install firefox. I wonder how many of those 200 million users did, or how many of them had it installed by some power user who set up their computer. I know there are at least a couple dozen people right now who are Firefox users because I installed it and put it front and center on the computers I built or setup or fixed for them.
reply