No idea. However, it seemed to be working a few days ago, someone posted tweets there and one could view w/o hitting the main site.

Someone posted that there’s a service ‘xcancel’ that lets one view a tweet w/o an account or logging in. Just add ‘cancel’ after the ‘x’, eg. https://xcancel.com/…

This is the sort of resistance we need, no more ‘decorum’ to a fascist leader. He won’t respect international norms so he deserves the benefit of none himself.

Are there any minor failures in your Tesla that you can claim warranty against? I wouldn’t begrudge anyone stuck with one now who bought in the past, but a sort of civil disobedience, aimed at costing the company as much as possible, would be an ethical imperative here. Claim any warranty repair you can. Be a ‘picky’ customer. Make support and sales spend extra effort and money in any way possible for your property. After all, you paid for it, make them spend as much money as possible.

Guess the cheque cleared

Fair enough… I admit I’m a bit of an old curmudgeon, set in my ways. :s

Aren’t you at all curious why it failed though? (If not, no harm no foul – I certainly know time diagnosing a bug is always in short supply, from personal experience). What if it’s a symptom of something important that might happen later even in Fedora 41?

Sometimes it just feels like containers are used as justification for devs to blow off bug reports. As a dev I want to understand why a failure occurs.

Agreed there – it’s good for onboarding devs and ensuring consistent build environment.

Once an app is ‘stable’ within a docker env, great – but running it outside of a container will inevitably reveal lots of subtle issues that might be worth fixing (assumptions become evident when one’s app encounters a different toolchain version, stdlib, or other libraries/APIs…). In this age of rapid development and deployment, perhaps most shops don’t care about that since containers enable one to ignore such things for a long time, if not forever…

But like I said, I know my viewpoint is a losing battle. I just wish it wasn’t used so much as a shortcut to deployment where good documentation of dependencies, configuration and testing in varied environments would be my preference.

And yes, I run a bare-metal ‘pet’ server so I deal with configuration that might otherwise be glossed over by containerized apps. Guess I’m just crazy but I like dealing with app config at one layer (host OS) rather than spread around within multiple containers.

Call me crusty, old-fart, unwilling to embrace change… but docker has always felt like a cop-out to me as a dev. Figure out what breaks and fix it so your app is more robust, stop being lazy.

I pretty much refuse to install any app which only ships as a docker install.

No need to reply to this, you don’t have to agree and I know the battle has been already lost. I don’t care. Hmmph.

Keyboard media keys (Fn + F keys, eg. vol mute, +/-, brightness etc.) do NOT yet work in mainline kernel. There is some good work going on over here on github but it’s preliminary.

Also note kernel 6.10 broke the bottom display it would appear; I’m using kernel 6.13-rc4 currently.

Risky move if you’re taking on an Ice Dragon… it might be Canadian. We love our pineapple pizza.

NEW METHOD which avoids the udev ‘event storm’ caused by docking/undocking the keyboard

[/usr/local/bin/asusUX8406_kbdwatch]

#!/bin/bash

me=$(basename "$0")
laststate=2

while true; do
  sleep 3
  output=$(lsusb -d 0b05:1b2c)
  stat=$?
  if [ $stat == 1 ] && [ $laststate != 1 ]; then
    ## kbd removed, enable lower display
    laststate=1
    logger -p user.info "${me} KEYBOARD REMOVED"
    xrandr --auto && xrandr --output eDP-2 --below eDP-1
  elif [ $stat == 0 ] && [ $laststate != 0 ]; then
    ## kbd replaced, disable lower display
    laststate=0
    logger -p user.info "${me} KEYBOARD DOCKED"
    xrandr --output eDP-2 --off
  fi
done

Hook this up to your init system, or run from a nohup session redirected to /dev/null on login or session startup … for example, on my system I am member of group video, so installing it to /usr/local/bin and setting ownership to root:video and sudo chmod ug+rx allows it to be run on session login automatically.

Quislings.

Not quite on-topic, but since there are others responding here… has anyone experienced issues with the xbox 360 for PC wireless controller not passing its D-pad to games in WINE/Proton? For example, Skyrim. I cannot use the ‘favorites’ weapon selection as a result. The D-pad is seen in the Wine/Windows DX joystick diags so I’m stumped. Any tips would be greatly appreciated.

Can’t SIGTERM be observed to react to a poweroff?

Now retired huh?

I can think of a good penalty… a number of years in prison equal to the years since they committed this crime. “Disgorgement” is a common legal mechanism, forcing convicted to give up their ill-gotten gains. In this case, time as free persons.

Quick, someone tell his lawyer to help him run for office! … Somewhere.

Apparently that stops the clock entirely on these things, right??

Why all the downvotes? Haven’t visited the links yet but this doesn’t sound like a corpo ad; and I didn’t think the lemmyverse was against outside linking – after all we’re against walled gardens right? (OK OK discord… but they also are on libera)

I like the idea of code-as-craft and this interests me.

It’s fine, cuz “Corporations are people, my friend” and money is speech!

Thanks Romney you slimy Bain Capital, corporate-raiding PoS.