it seems like ideally it shouldn’t attempt to preview the link before a user tries to view the content. i guess that would increase latency for users though

it’s a slow process

https://www.youtube.com/@ExperTtrout9232/videos

The plan is apparently to sell 4 versions going from none of the silly features to all of the silly features (basic -> suction -> forward thrust -> flying iirc) (with the flying configuration being restricted to invite-only). So the stunts with the flying version will probably drive the sales of the versions that will actually get sold in a meaningful quantity. Although from what I’ve heard it seems unlikely to me that any of the additional features will be allowed to be used on roads. (Apparently the gas gets really cold when fired due to the pressure dropping, to a possibly dangerous degree, and the wind will certainly be a problem for things behind it, as well as being extremely loud. The suction thing is probably going to also going to be quite loud and might have a risk of firing small rocks out the back at high speeds, it also requires a gasket that wears out over time so it can’t be used mindlessly)

It might be really good on tracks, since that was apparently a big focus for them (and a current sporty EV with fans for suction is very good on tracks). Then I guess people will want to buy it because of the sportiness for the same reason people normally buy whatever supercars

Tesla in general seems to have lost whatever lead they had in affordable EVs (especially outside of the US where Chinese EVs are allowed to be sold) so maybe they’re trying to shift their brand to more premium?

Yeah, they said it’s about 1.7 tonnes. They’ve also shown off the drivetrain, battery pack, etc in separate displays. Idk, I think it probably is pretty similar to what they plan on selling (to a limited number of selected people apparently)

I’m sure all versions of the car aren’t ready for real world use and manufacturing or else they would be selling it already

Edit: it doesn’t seem like Tesla R&D has done much else in the past 8 years lol. They have a ton of time, money, and manpower and it does not surprise me that they’re willing to spend it on cool but stupid stunts

judging by the shadows i would guess maybe 6in of clearance between the bottom frame and the battery pack? It’s hard to tell because of the perspective of the shot and the perspective of the picture taken of the screen. Obviously there needs to be some open area for the fans, but idk why it would need a frame in it.

Yeah, I think it’s still closed for new contributers as well to combat that, so it might not stay as the place to find everything for long… but if people flock to any other easy to contribute package repository it’ll probably have the same problems eventually. I guess that’s what flatpack is for, but it seems so inefficient to me.

nixos sounds very cool to me in theory but in practice there’s a lot more in the aur than in nixpkgs and arch hasn’t broken for me yet anyways

there’s also an extension called page editor that allows you to directly click on text to edit it when active (a little more convenient) but it won’t work in the settings tab as firefox prevents extensions from modifying the settings page

found the link https://github.com/quiltedhills/good-girl

(edit: i guess it’s technically an autoconfig script and not an extension)

someone on r/countwithchickenlady made an extension to do this

https://en.wikipedia.org/wiki/Moment_(unit)

although they didn’t really have seconds back then, so they would have said it was 1/40th of an hour, and it also apparently changed length depending on location/time of year (because they were defining hours relative to the times of sunrise and sunset)

I would guess that by “geometrically sum” they meant the magnitude (I don’t see what else they could have meant). I’m pretty sure I’ve heard it used in that way before although I don’t think it’s a standardized term

I’m pretty sure that the difference is just that you get sqrt(2)/2 vs sqrt(2)/2 in the middle instead of .5 vs .5

The dot product of 2 unit vectors is equivalent to the cosine of the angle, the magnitude of the cross product is equivalent to the sine

test link

I guess yours isn’t working because there’s a space in it

I was thinking the other day that as a holiday it might be most conceptually similar to Guy Fawkes day, politically motivated holidays celebrating the downfall of someone hated

With the difference being that Guy Fawkes day celebrates the government’s victory over him while Charlie Kirk was aligned with the government and killed illegally, so it’s a more natural holiday driven by organic culture while Guy Fawkes day was government supported

Anyways I’m not British so I don’t really know much about Guy Fawkes day, and this is a silly comparison

I installed arch “from scratch” for the first time after installing it with archinstall like 4+ times previously, and yes it definitely somewhat did this, but honestly not quite to the extent that I expected. I feel like most of my system’s configuration was determined for me by the KDE plasma dependencies and defaults lol

My bootloader configuration is definitely one of the parts that I was more exposed to with a manual install, but honestly I don’t really see how what I learned would help me fix issues like that in the future, more about how I could customize the boot screen and extend my configuration with more boot options

idk it was a good experience to have but I think it brought more personal satisfaction than real practical benefit

you can use arch with the cachyos kernel and repositories to (afaik) get most of that performance boost while keeping the arch experience, that’s what i’m doing on my main computer at the moment

https://wiki.cachyos.org/features/optimized_repos/#adding-our-repositories-to-an-existing-arch-linux-install

lol I randomly searched for a page from collabora about how they reverse engineer GPU drivers (since I’ve seen that they’ve done that for other GPUs) and the very first page I went to was written by this person. Apparently this was a side project while she did fairly similar work on Mali GPUs at Collabora.

Anyways, here’s what she said about the process:

Typically, for Linux or Android driver reverse-engineering, a small wrap library will be written to inject into a test application via LD_PRELOAD that hooks key system calls like ioctl and mmap in order to analyze user-kernel interactions. Once the “submit command buffer” call is issued, the library can dump all (mapped) shared memory for offline analysis…

it took some elbow grease to identify the three critical calls: memory allocation, command buffer creation, and command buffer submission…

With those obstacles cleared, we can finally get to the shader binaries, black boxes in themselves. However, the process from here on out is standard: start with the simplest fragment or compute shader possible, make a small change in the input source code, and compare the output binaries. Iterating on this process is tedious but will quickly reveal key structures, including opcode numbers.

From https://alyssarosenzweig.ca/blog/asahi-gpu-part-1.html , there’s a lot more details about the subsequent parts of the process in the next articles but they’re harder to summarize

I think it’s supposed to be that how AI turns high level instructions into code is compared to how compilers turn code into assembly. Implying that using AI is just a natural extension of the handing off work to the computers that we’ve already been doing.

I wonder if you gave different AI models some c++ or something and told them to write assembly based on it how well they would do compared to an actual compiler