• 68 Posts
  • 1.47K Comments
Joined 1 year ago
cake
Cake day: October 4th, 2023

help-circle


  • investigates

    Hmm. Apparently, yeah, some Tesla vehicles do and some do not.

    reads further

    It sounds like autos in general are shifting away from tempered glass side windows to laminated glass, so those window breakers may not be effective on a number of newer cars. Hmm. Well, that’s interesting.

    https://info.glass.com/laminated-vs-tempered-car-side-windows/

    You may have seen it in the news recently—instances of someone getting stuck in their vehicle after an accident because the car was equipped with laminated side windows. Laminated windows are nearly impossible to break with traditional glass-break tools. These small devices are carried in many driver’s gloveboxes because they easily break car windows so that occupants can escape in emergency situations. Unfortunately, these traditional glass-break tools don’t work with laminated side windows. Even first responder professionals have difficulty breaking through laminated glass windows with specialized tools. It can take minutes to saw through and remove laminated glass. In comparison, tempered glass breaks away in mere seconds.





  • At the time of the K-T extinction, we looked like this:

    https://en.wikipedia.org/wiki/Purgatorius

    The Cretaceous–Paleogene (K–Pg) extinction event,[a] also known as the K–T extinction,[b] was the mass extinction of three-quarters of the plant and animal species on Earth[2][3] approximately 66 million years ago. The event caused the extinction of all non-avian dinosaurs. Most other tetrapods weighing more than 25 kg (55 lb) also became extinct, with the exception of some ectothermic species such as sea turtles and crocodilians.[4]

    Omnivores, insectivores, and carrion-eaters survived the extinction event, perhaps because of the increased availability of their food sources. Neither strictly herbivorous nor strictly carnivorous mammals seem to have survived. Rather, the surviving mammals and birds fed on insects, worms, and snails, which in turn fed on detritus (dead plant and animal matter)

    Luckily, great-grandaddy squirrel-critter was a survivor and had a taste for insects:

    It is thought to have been rat-sized (6 in (15 cm) long and 1.3 ounces (about 37 grams)) and a diurnal insectivore, which burrowed through small holes in the ground.


  • Looks fine to me.

    Little side question: Will the Wi-Fi and Bluetooth on the motherboard work in Arch? From what I could gather, the drivers for it should be in the latest kernel, but I’m not 100% sure.

    If they don’t for some reason and you can’t get it working or need some sort of driver fix, can always worst case fall back to a USB dongle or similar until they do. Obviously, preferable not to do that, but shouldn’t wind up stuck without them no matter what.


  • This was the fourth night in a row when Russian “shahids” flew into Belarus en masse and for the first time in these days the Belarusian Air Force’s duty aircraft was raised. The fighter from Baranovichi took off at about 07:40 in the morning and returned to the base at 08:45.

    What’s the navigation system on those UAVs?

    kagis

    https://www.kyivpost.com/post/25204

    The Shahed “kamikaze drone,” known also by its Russian nomenclature as the Geran-2, is more properly classified as a one-way attack unmanned aerial vehicle (OWA UAV).

    The original Shaheds employed inertial navigation blocks, manufactured in Canada, that relied on commercially available GPS systems for navigation with a limited CEP accuracy of around 10 to 15 meters. The Russian variants use the “Komet” navigation system, which incorporates GLONASS, Russia’s version of GPS for guidance. This is almost the only component of Russian production in these drones.

    Sounds like that system is vulnerable to some form of electronic attack.

    EDIT: Unless the idea is that it’s intentional, to try to come from an unexpected direction. If those tracks in the image represent the actual tracks, though, I’m not sure how useful they are. Doesn’t look very effective.



  • Plus, even if you manage to never, ever have a drive fail, accidentally delete something that you wanted to keep, inadvertently screw up a filesystem, crash into a corruption bug, have malware destroy stuff, make an error in writing it a script causing it to wipe data, just realize that an old version of something you overwrote was still something you wanted, or run into any of the other ways in which you could lose data…

    You gain the peace of mind of knowing that your data isn’t a single point of failure away from being gone. I remember some pucker-inducing moments before I ran backups. Even aside from not losing data on a number of occasions, I could sleep a lot more comfortably on the times that weren’t those occasions.


  • That’s not a completely reliable fix, a third party library could still call setenv and trigger crashes, there’s still a risk of data races, but we’ve observed a significant reduction in SIGABRT volumes.

    Hmm. If they want a dirty hack, I expect they could do a library interposer that overrides setenv(3) and getenv(3) symbols with versions that grab a global “environment variable” lock before calling the actual function.

    They say that they’re having problems with third party libraries that use environment variables. If they’re using third-party libraries statically-linked against libc, I suppose that won’t work, but as long as they’re dynamically-linked, should be okay.

    EDIT: Though you’ve still got an atomic update problem with the returned buffer, doing things the way they are, if you don’t want to leak memory. Like, one thread might have half-updated the value of the buffer when another is reading the buffer after returning from the interposer’s version of the function. That shouldn’t directly crash, but you can get a mangled environment variable value. And there’s not going to be guarantees on synchronization on access to the buffer, unlike the getenv() call itself.

    thinks

    This is more of a mind-game solution, but…

    Well, you can’t track lifetime of pointers to a buffer. So there’s no true fix that doesn’t leak memory. Because the only absolute fix is to return a new buffer from getenv() for each unique setenv(), because POSIX provides no lifetime bounds.

    But if you assume that anything midway through a buffer read is probably going to do so pretty soon, which is probably true…

    You can maybe play tricks with mmap() and mremap(), if you’re willing to blow a page per environment variable that you want to update and a page of virtual address space per update, and some temporary memory. The buffer you return from the interposer’s getenv() is an mmap()ed range. In the interposer’s setenv(), if the value is modified, you mremap() with MREMAP_DONTUNMAP. Future calls to getenv() return the new address. That gives you a userspace page fault handler to the old range, which I suppose – haven’t written userspace page fault handlers myself – can probably block the memory read until the new value is visible and synchronize on visibility of changes across threads.

    If you assume that any read of the buffer is sequential and moving forward, then if a page fault triggers on an attempted access at the address at the start of the page, then you can return the latest value of the value.

    If you get a fault via an address into the middle of the buffer, and you still have a copy of the old value, then you’ve smacked into code in the middle of reading the buffer. Return the old value.

    A given amount of time after an update, you’re free to purge old values from setenv(). Can do so out of the interposer’s functions.

    You can never eliminate that chance that a thread has read the first N bytes of an environment variable buffer, then gone to sleep for ten minutes, then suddenly wants the remainder. In that case, you have to permit for the possibility that the thread sees part of the old environment variable value and part of the new. But you can expend temporary memory to remember old values longer to make that ever-more unlikely.




  • Assuming that this is the episode and the Factorio dev post that references, I think that that’s a different issue. That dev also was using Sway under Wayland, but was talking about how Factorio apparently doesn’t immediately update the drawable area on window size change – it takes three frames, and Sway was making this very visible.

    I use the Sway window manager, and a particularity of this window manager is that it will automatically resize floating windows to the size of their last submitted frame. This has unveiled an issue with our graphics stack: it takes the game three frames to properly respond to a window resize. The result is a rapid tug-of-war, with Sway sending a ton of resize events and Factorio responding with outdated framebuffer sizes, causing the chaos captured above.

    I spent two full days staring at our graphics code but could not come up with an explanation as to why this is happening, so this work is still ongoing. Since this issue only happens when running the game on Wayland under Sway, it’s not a large priority, but it was too entertaining not to share.

    I’d guess that he’s maybe using double- or triple-buffering at the SDL level or something like that.


  • Lynne Ingram, a Somerset beekeeper and the chair of the Honey Authenticity Network UK, said: “The market is being flooded by cheap, imported adulterated honey and it is undermining the business of genuine honey producers. The public are being misinformed, because they are buying what they think is genuine honey.”

    The UK is one of the biggest importers of cheap Chinese honey, which is known to be targeted by fraudsters. Honey importers say supply chains and provenance are carefully audited, but there has been no consensus on how technical tests should be applied, or which are most reliable.

    A fun bit of perspective that I like to mention in discussions about this. Roll back a bit over a century:

    Scientific American, November 2, 1907

    Artificial Honey

    Prof. Herzfeld, of Germany, recently brought out some interesting points regarding the manufacture of artificial honey in Europe. It is noticed that when we bring about the inversion of refined sugar in an almost complete manner and under well determined conditions, this sugar solidifies in the same way as natural honey after standing for a long time, and it can be easily redissolved by heating. Owing to the increased production of artificial honey, the bee cultivators have been agitating the question so as to protect themselves, and it is proposed to secure legislation to this effect, one point being to oblige the manufacturers to add some kind of product which will indicate the artificial product. On the other hand, it is found that the addition of inverted sugar to natural honey tends to improve its quality and especially to render it more easiIy digested. Seeing that sugar is about the only alimentary matter which is produced in an absolutely pure state, its addition to honey cannot be strictly considered as an adulteration. Bees often take products from flowers which have a bad taste; and the chemist Keller found that honey coming from the chestnut tree sometimes has a disagreeable flavor. From wheat flowers we find a honey which has a taste resembling bitter almonds, and honey from asparagus flowers is most unpalatable. Honey taken from the colza plant is of an oily nature, and that taken from onions has the taste of the latter. In such cases, the honey is much improved by the addition of inverted sugar. Prof. Herzfeld gives a practical method for preparing this form of sugar. We take 1 kilogramme (2.2 pounds) of high-quality refined sugar in a clean enamelware vessel, and add 300 cubic centimeters (10 fluid ounces) of water and 1.1 grammes (17 grains) tartaric acid. This is heated at 110 deg. C. over an open fire, stirring all the while, and is kept at this heat until the liquid takes on a fine golden yellow color, such operation lasting for about three quarters of an hour. By this very simpIe process we can easily produce artificial honey. Numerous extracts are now on the market for giving the aroma of honey, but none of them will replace the natural honey. However, if we take the artificial product made as above and add to it a natural honey having a strong aroma, such as that which is produced from heath, we can obtain an excellent semi-honey.



  • despite editing the .sh file to point to the older tarballed Python version as advised on Github, it still tells me it uses the most up to date one that’s installed system wide and thus can’t install pytorch.

    Can you paste your commands and output?

    If you want, maybe on [email protected], since I think that people seeing how to get Automatic1111 set up might help others.

    I’ve set it up myself, and I don’t mind taking a stab at getting it working, especially if it might help get others over the hump to a local Automatic1111 installation.


  • venv nonsense

    I mean, the fact that it isn’t more end-user invisible to me is annoying, and I wish that it could also include a version of Python, but I think that venv is pretty reasonable. It handles non-systemwide library versioning in what I’d call a reasonably straightforward way. Once you know how to do it, works the same way for each Python program.

    Honestly, if there were just a frontend on venv that set up any missing environment and activated the venv, I’d be fine with it.

    And I don’t do much Python development, so this isn’t from a “Python awesome” standpoint.


  • autoplay

    Submitted videos, which should be what is relevant here, don’t autoplay.

    I’ll also add that:

    • While the community is not explicitly one devoted to combat videos, it should be pretty clear that that is part of what is here. If someone is going to browse such a community, then they may well get videos that contain soldiers being killed.

    • One argument might be “what if someone wants to browse All and click on videos and watch them and finds videos that have death in them morally-objectionable”. I don’t browse All – I think that trying to whitelist makes much more sense than blacklisting – but my personal view is that anyone that does so is implicitly accepting that they’re going to get a firehose of content of all sorts. Some of that is going to be political statements that they don’t agree with. Some is going to be content that might have language that one might find objectionable. Some might be images that one finds repulsive – we have one person on [email protected] who rather famously likes making “gross” images. Some of it might just be offensive to various parties, like off-color jokes. A very considerable amount of it might be material that parent might not want their six-year-old seeing, like discussions about sexuality or profanity. Some of it might be religiously-unacceptable to various groups.

      There are a very considerable number of things that some group, somewhere, might object to.

      I do not think that it is reasonable to repurpose NSFW to be a “might not personally like” flag that is placed on anything that anyone out there might potentially not want to see. The scope there is simply too broad. Every group somewhere has their own personal preferences, and has an incentive to try to convert “All” into a feed that matches their personal interests.

      I think that it’s fine to recognize that someone, somewhere, might have different views than someone else, and that one day, having a curation system with finer-grained classification of content added to the Threadiverse – perhaps with someone other than the submitter responsible for adding that variety of tags – that is relatively fine-grained may be a good technical solution. My personal view is that the idea of “taglists” that users or groups can publish and other users can subscribe to, which attach a classification to the content of other users, is a good way to do this. That is, User A submits content. User B – which might be a bot or a group of humans – adds that submitted item to a list they publish with a classification, which might include a recommendation to hide or to bring to the attention of a user or simply to attach a content tag. User C can choose whether-or-not to subscribe to User B’s “tag feed”, and their client perhaps how to interpret that feed. C maybe takes a delay on content visibility to provide time for tagging to be applied to new content. Tag feeds could attach tags to users or to communities. That’s a situation that I think might be workable, scales to an infinite number of content preferences, and permits for fine-grained content classification, without anyone imposing their content preferences on anyone else or requiring submitters or moderators to try to understand and adapt to all forms of content preference around the world.

      In the absence of such a solution, I am comfortable placing the burden on those who want a particular sort of content to do the filtration themselves, rather than just pushing that content to the other side of a wall for everyone else as well.

      I do not think that trying to repurpose NSFW for other content-filtering purposes is a reasonable approach. The intent of NSFW is to let people browse content in public or workplace environments. It is obviously not completely perfect – there is no one set of precisely-identical global norms for what is acceptable in public. But there is enough overlap that I think that it’s at least possible to talk about that as a concept.

    I will add one final note. While I personally do not think that repurposing the NSFW flag in this way is justified, and think that down that road just lies an infinite number of arguments with various groups who don’t want to see various forms of content and want their preferences being made the norm for everyone, if the moderators here ultimately decide that doing so is their decision, I would then advocate for a different change. Keep [email protected]’s NSFW flag off…but create a new sister community, [email protected]. Move combat video content to that community, and flag that community NSFW, or at least require submitters there to flag a video NSFW if it contains death (or a close view of death, or whatever). Have each community link to the other in the sidebar. That keeps all the content in the former community other than combat video visible under prior rules. I think that there are many problems with this approach, starting with the “infinite groups with their own preferences who will make their own cases to alter the All feed”, and then that there are plenty of news articles that contain non-war-video content and analysis but might also contain war videos…think The War Zone. Not to mention that the content on linked pages might change, something that The War Zone often does with embedded video updates. Many different news sources do not engage in this form of censorship, and are not going to bother segregating their own content. But it’s at least a subset of the problems that the proposed “flag the whole Ukraine community NSFW” approach has.


  • tal@lemmy.todaytoUkraine@sopuli.xyz[META] Discussion regarding NSFW content and policy
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    11 days ago

    The original idea of “NSFW” is to not show content that might be problematic for someone at work.

    I personally don’t have any problem with violence being visible; an employer isn’t going to care, and nobody’s going to care if I’m viewing a violent video in a restaurant or something. But I’m American. Maybe there are places where there are cultural differences. I would like the option to not show nudity in thumbnails and inline images, but that’s not a factor for war videos. As far as I’m concerned, the community not being flagged NSFW is fine.