I personally don't see the correlation between what he's been saying about AI and his blog site's reliability requirements. It's a blog, not some high availability service.

Also, was Henry Ford asking for regulation because his cars may destroy our civilization as we knew it?

Does Kagi still use Yandex index behind the scenes? If this is true, then certain fraction of the payment goes to Russian Federation and financing its war and genocide in Ukraine. This is the reason I have to refrain from using this otherwise excellent service.

HN users really hate this piece of truth.

I really wish that browsers natively supported some sort of "402 Payment Required" HTTP status code (or any other well-known specified indicator) that users could pay with micropayments, so that they wouldn't have to drown us in this ad garbage. I would gladly pay small but justified sum for an article without setting up payment method on each site and be able to return to it. I would be glad even to donate some amount of money to some authority that'd pay for viewership of those less fortunate and not being able to afford reading quality news.

This is doable today if there was a will. But the advertising/surveillance industry doesn't want it.

Transaction costs make it inefficient. Costs more to effect the transfer than they would be able to charge for the articles.

So sorry to hear your story, in some ways I can relate. Others have already given great advices, I don’t have to repeat them by myself. Just one specific thing regarding the “brain fog” you mentioned: check your vitamin, iron, and ferritin levels in your blood. And, of course, rest more, apparently you are holding a company on your single shoulders, you can say no from time to time.

Wishing you all the best and good luck!

For me, personally, FB just became boring and uninteresting at some point. I sometimes open FB for Marketplace and, I think, this is it. Had no need to go cold turkey and delete the account. I still have it for Messenger which I use as an app both for desktop and mobile because I don’t want to lose touch with my friends, esp. during these times.

How well is this handled from the accessibility point of view? I imagine that wrapping text in consecutive “p” tags is semantically clearer, however on the other side it shouldn’t be too hard for any accessibility software to recognize this pattern described in the article.

EDIT: some wording changes.

Re: black screen when using Teams from browser. Check you have environment variables set correctly: XDG_SESSION_TYPE=wayland and XDG_CURRENT_DESKTOP=sway. I set up them in my .zshrc before starting sway. This helped me to fix the black screen issue. Hope it helps you too!

If those env vars weren't set screen-sharing with xdpw would be broken as a whole because pipewire wouldn't invoke it, which wasn't the case. Other applications like that one python gstreamer script could access xdpw just fine, and Firefox and Chromium could screen-share in other websites (like Mozilla's gUM test page) just fine; the only one broken was Teams.

From my experience: they end in a situation where nobody is happy - they both try to figure out what is the best for the other person and in the end they both end up in a situation that is not good for both of them. I know, twisted.

Not so ironic any more if we consider Microsoft’s work on WSL in a last couple of years.

Which version are you using right now? I have the latest one and it does not allow me to share anything else than a white canvas. Do you launch zoom somehow differently? For me it behaves like a regular XWayland app

zoom-2.7.162522.0121-1.x86_64 which seems to be their latest.

With the previous version I had the same thing, only allowed me to share white canvas.

Here's the process hierarchy:

  \_ gdm-session-worker [pam/gdm-password]
      \_ /usr/libexec/gdm-wayland-session gnome-session
          \_ /usr/libexec/gnome-session-binary
              \_ /usr/bin/gnome-shell
                  \_ /usr/bin/zoom
                      \_ sh -c export SSB_HOME=/home/me/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; /opt/zoom/zoom ""
                          \_ /opt/zoom/zoom

Besides installing the new RPM, I haven't done anything differently.

Sadly I'm not able to test this since I'm not running Fedora and GNOME. I'm using sway. Interestingly enough, Zoom change log does not seem to mention anything related to Wayland support: https://support.zoom.us/hc/en-us/articles/205759689-New-Upda.... Thank you for your comment, will try this in GNOME some time.