iggames

@iggames@lemmy.world
3 Post – 13 Comments
Joined 1 years ago

The article already has one example: “Juneau, Alaska, voted to remove fluoride from its drinking water in 2007. A study published in the journal BMC Oral Health in 2018 compared the dental records of children and adolescents who received dental care for decaying teeth four years before and five years after the city stopped adding fluoride to the water. Cavity-related procedures and treatment costs were significantly higher in the latter group, the study found.”

A nurse at work had “CA$H MONEY” tattooed inside her lip. Sounded like the result of a drunken dare/bet.

Fun fact - we will intentionally inject (small) bubbles of air into your veins to look for connections between chambers of your heart that shouldn’t be there. It’s called a Bubble Study. https://www.health.harvard.edu/heart-health/what-is-a-bubble-study

I often leave Steam running in the background. Indeed, KDE seems to be suspending more reliably after I exit Steam. Thanks for the suggestion!

Added "mdns" service to allowed list for public zone, still get the SANE error. (Previously added 5353 UDP per another suggestion -- sounds like this is the port for mDNS)

1 more...

Added some info to the post. Firewall is blocking 3289 UDP from my printer, so I added 3289 UDP to open ports for "home", "public", and "internal" zones. However, I'm still seeing filter_IN_public_REJECT entries in dmesg, so it seems the firewall is still blocking these. Is there a different way I should be telling it to allow requests on this port?

Firewall also allows mdns service (again, in "home", "public", and "internal" zones), but I also see entries like this:

[41951.119486] filter_IN_public_REJECT: IN=wlp0s20f0u3 OUT= MAC= SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=10725 DF PROTO=2 MARK=0x3214

It sounds like 224.0.0.1 is related to mdns broadcasts, so it seems firewall is also still blocking these (despite mdns being allowed service).

Am I specifying these in the wrong place? (Per Connections - System Settings, my wifi is in Firewall zone "home").

Thank you for the suggestions! I’ll dig into these tonight and see what I can get working.

Looks like there’s an open issue (with fairly recent activity) for adding Wayland support: https://github.com/joshgoebel/keyszer/issues/27

Thanks for the suggestion, I’ll look into this more.

Looks like evremap will do what I want, plus a nifty bonus! The following config lets me use CapsLock + N/P/etc to navigate. And if I just tap CapsLock without pressing anything else, it will act as escape.

device_name = "Telink Wireless Receiver"

[[dual_role]]
input = "KEY_CAPSLOCK"
hold = ["KEY_F19"]
tap = ["KEY_ESC"]

[[remap]]
input = ["KEY_F19", "KEY_N"]
output = ["KEY_DOWN"]

[[remap]]
input = ["KEY_F19", "KEY_P"]
output = ["KEY_UP"]

[[remap]]
input = ["KEY_F19", "KEY_B"]
output = ["KEY_LEFT"]

[[remap]]
input = ["KEY_F19", "KEY_F"]
output = ["KEY_RIGHT"]

[[remap]]
input = ["KEY_F19", "KEY_A"]
output = ["KEY_HOME"]

[[remap]]
input = ["KEY_F19", "KEY_E"]
output = ["KEY_END"]

Note: I used F19 because it doesn't seem to be bound to anything by default. Apparently, a bunch of the other function keys already did things, as described in /usr/share/X11/xkb/symbols/inet

$ cat /usr/share/X11/xkb/symbols/inet | grep FK13
    key    {      [ XF86Tools         ]       };
    key   {       [ XF86MailForward       ]       };
    key   {       [ XF86Word              ]       };      // F2
    key   {       [ XF86MailForward       ]       };      // F3

$ cat /usr/share/X11/xkb/symbols/inet | grep FK20
    key    {      [ XF86AudioMicMute      ]       };

Yes, "sane" service is already in the "Allowed" list.

No change with allowing 5353 UDP through the firewall, unfortunately. But thank you for the suggestion!

1 more...

Looks like that script is for Gnome (based on the StackOverflow post listed on the project page, it talks to org.gnome.SessionManager via dbus). I wonder if there is a similar way to talk to PowerDevil?

I always read “f/u w/PCP” as “fucked up on PCP” instead of “follow up with primary care provider”.