• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • The number seems low, so I looked for some information about how common CO poisoning is in non-Airbnb hotels and motels and found this:

    This study was conducted to determine the significance of the problem of carbon monoxide poisoning occurring in US hotels, motels and resorts. […] From January 1, 2005 to December 31, 2018, 905 guests were poisoned in 115 identified incidents, including 22 fatalities. […] Most poisonings were caused by natural gas fueled appliances and could likely have been prevented by an in-room carbon monoxide alarm. To reduce morbidity and mortality from unintentional CO poisoning in lodging facilities, government should mandate installation of in-room CO alarms, similar to the current requirement for smoke alarms.

    This problem doesn’t appear to occur any higher in Airbnb establishments than any other hotel, motel, or resort, at least according to what this research suggests. It is worth noting, however, that the frequency of poisonings is a lot higher when you consider those that didn’t lead to fatalities.

    With that said, CO monitors are fairly cheap and as the research states, a lot of these incidents could probably have been prevented by using them. In many countries in Europe at least, this is already a legal requirement. I don’t see why it shouldn’t be in the US too.


  • This thread is about KeePass and my comments relate to that. If you pull KeePass2 from the repos in Debian, for example, it’s going to pull the Mono runtime to execute it as well because it’s been built, like most C# apps, for JIT compilation. I doubt it’s even possible to compile KeePass2 using AOT compilation.

    This is what the C# KeePass application looks like using the Mono runtime in Debian:

    This is KeePassXC:

    You can see which has better native integration into the desktop out of the box.


  • Obsidian is really good. Very feature-rich and customizable.

    I personally prefer Joplin for a couple of reasons. It’s fully open source and while it has less features and customizability, I also feel it keeps out of my way more to allow me to focus purely on taking notes and not messing around with other features. Obsidian encourages me to play with its extra features more, which for my case usually just reduces the productivity of my note-taking.

    Probably just a me-thing. I tend to gravitate to more straightforward and minimalist solutions generally.







  • The Lemmy experience has improved immeasurably since the pre-population-boom days, where I saw Kbin as a slightly more attractive option as the UI was more polished at the time. After Lemmy 0.18.2 hit and fixed the issues with the annoying auto-updating timelines, improved the sorting algorithms, and improved database performance I’ve used it exclusively.

    The Lemmy software seems to have more people working on the code and things are being addressed and improved rapidly. This extends to more 3rd party app support too. It feels like the better supported platform and that seems like it’ll be the case moving into the future as well.

    As a personal note I also don’t like some of the terminology used on the Kbin platform. “Magazine” is a confusing term that seems to have been chosen purely to be different. Sometimes it’s just best to stick to common terms to reduce the complexity and learning curve of a platform.












  • I think your points about frustration are valid, particularly at this time when there’s a lot of reddit refugees. That said, it’s Beehaw’s choice what they’re willing to put up with. I think defederation with entire instances is a very extreme response to their issues, but ultimately it’s their choice.

    I think with the admins’ mentality over there, they will probably end up with a very large defederation block list. For that reason, it is probably for the best if Lemmy’s most active communities were NOT hosted there. People should put the energy into building up other communities so the platform more broadly isn’t reliant on extremely moderated instances like Beehaw.

    Major communities should be on instances that welcome a wide range of views that are also willing to have a robust and diverse admin team to handle issues, imo. That would be the healthiest solution overall. Beehaw choosing to defederate now is a blessing in disguise; it’s an early statement proving that instance is an unsuitable host for any community looking to be home to a broad-reaching and diverse member base.