Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
4
Comments
1081
Joined
3 yr. ago

  • The idea is that Google and Apple on Android and iOS have purposefully gimped PWA functionality in order to maintain the popularity of their app stores. Which I get, because web apps are much more useful and functional on full computers. So it’s not really the fault of the PWAs that PWAs suck. But unfortunately, they do suck.

  • The existing Wi-Fi infrastructure was “overtaxed” so they just threw up satellite instead of , I don’t know, improving the Wi-Fi infrastructure? There’s perfectly fine WiFi at sprawling work and college campuses, and stadiums that seat tens of thousands of people. What a joke.

  • PWAs are god awful on IOS.

  • My current home server that runs three dozen containers including Plex and Emby as well as two dozen other services and many terabytes of data is literally an old Lenovo desktop I got for free out of somebody’s garage 14 years ago. So yeah it’s sort of a perfectly fine place to start.

  • Just put the image over a larger white backdrop before you feed it to the AI

  • The funny thing about this scenario is by simply thinking that’s true, it actually becomes true.

  • That would be really useful if the people behind these texts were subject to US laws.

  • Watching Tim Berners Lee write about his new AI project kinda hurts my soul a lil bit

  • No. It’s a term which means a services hosted by…yourself.

  • I mean there’s no legal reason that would exist now that didn’t before.

    My guess is that they did honor the setting, but that was because the amount of people that used it was so low vs the total number of people that used the devices. Now with smart speaker adoption rates declining, and their desire to train AI, they have to dip into the pool of people that opted not to share.

  • The author actually explains that his original solution was just saving them locally on his phone and playing them from there, but that was too much legwork for his wife to want to switch from a cloud service like Audible. So the whole self hosting part is to become “Audible” for his wife lol.

  • I mean if they were doing this already there would be no point in sending this email out. They would have just happily continued letting people think it wasn’t happening while doing it anyway, while not having to deal with the backlash this will generate.

  • Actually as much as I’d love to use Firefox all the time, there are many times it won’t work properly at all. This isn’t entirely Mozilla’s fault, but it is the case.

  • The problem is that the sales pitch of these AI answering services in search engines is to save you time from having to open search results and read them yourself. The problem with 80-90% accuracy is that if the summaries are hallucinated even once, you can no longer trust them implicitly, so in all cases you now have to verify what it says by opening search results and reading them yourself. It’s a convenience feature that doesn’t offer you any actual convenience.

    Sure it’s impressive that they are accurate 80-90% of their time, but AI used in this context is of no actual value.

  • If you couldn’t suss out the obvious sarcasm, it might be time to go offline for awhile and recalibrate.

  • You can get a VPS on Vultr for $5 a month that’ll be plenty for your use case. For security look into mTLS. Web servers like Caddy support it pretty easy. You put a certificate on you and your wife’s phones and only you will be able to connect to your endpoint.

  • The definitions you've linked above do not contradict what I've posted below or how I've described the behavior in the article. You're running a narrow definition, I'm running a broad definition, the distinction is really fine and neither is wrong.

    From the linked Wikipedia article I linked above:

    Ok so a couple things here. You mention your knowledge is decades old. If you're talking more than two decades ago there’s a chance your definition was correct a very long time ago. But to be clear, today in the year of our lord 2025, in the United States of America, your definition is not correct. There are no “narrow” and “broad” definitions. There is a single definition for each in the context of firefighting in the U.S.

    One of the things you’ll want to get in the habit of doing, is not quoting Wikipedia as your source, but rather the source that Wikipedia refers to when it says something:

    there is considerable disagreement about categorizing backdrafts as flashovers

    The disagreement mentioned here refers to the long history of loose definitions in the distant past of fire science as these phenomena were being studied and categorized, as well as differences between scientific and firefighting applications, and European/ US entities. If you follow that reference in your quote [5],

    You’ll see it goes over the history of the terms and how we’ve ended up with the current definitions. In the U.S. based fire service, the be-all end-all of these terms in NFPA 921-2004 which is as follows:

    The newly crafted NFPA 921-2004 definition of flashover is: "A transitional phase in the development of a compartment fire in which surfaces exposed to thermal radiation reach ignition temperature more or less simultaneously and fire spreads rapidly throughout the space resulting in full room involvement or total involvement of the compartment or enclosed area."

    The source goes on to explain:

    However, for firefighting purposes, the NFPA have recognized for over twenty years (in their annual reports concerning firefighter life losses) that there are several other forms of related phenomena or terms used, such as smoke explosion; flameover; backdraft; flash fire; etc and that many of these phenomena cannot be explained or directly attributed by on-scene firefighters.

    Therefore, the NFPA reporting system has established the term 'Rapid Fire Progress' to cover all situations where some form of fire phenomena led to an extreme event of combustion causing sudden transition from a small fire to a large fire, even where flaming is not sustained. They further refer to various sudden or extreme fire phenomena as falling into one of three categories:

    • Flashover
    • Backdraft (Backdraught)
    • Fire Gas Ignitions

    The whole “All backdrafts are flashovers but not all flashovers are backdrafts” comes from studies done by the Swedes in the 1980s which, depending on how long ago you spoke with your lieutenant, may have been what he was referring to. The source article touches on these as well, but again, these are not acceptable terms today.

    So if in your article you wanted to use the non-specific broad definition of these phenomena, you’d use “Rapid Fire Progress”. But if you wanted to use terms like flashover or backdraft, you’d need to use the correct one for the phenomena you’re trying to describe because they are not interchangeable any longer.

    Here is another great article in PDF format about RFP and its categories that really goes into detail on their differences. It also explains the issue I take with your article, which is that these terms are still to this day sometimes casually misused as if they’re unimportant and interchangeable. This is harmful when presented in an educational context (like your article is to some degree), because these terms need to be clear, distinct, and have a universal meaning so that conditions can be accurately communicated when you’re fighting a fire.

  • Why is the article using diagonal screen size as their measurement for phone size? In that case you could have a phone the exact same size get “bigger” just because bezel sizes have shrunk over the years.

    They specifically call out the iPhone SE as a “small phone” that they seem to want. But the newest iPhone, the iPhone 16 is only 6% bigger in width and height. Fractions of an inch larger. I can totally understand why somebody would want a phone with smaller overall dimensions, but why on earth would your metric for an ideal phone be a smaller screen?