Hacker News new | past | comments | ask | show | jobs | submit | changelink's comments login

My girlfriend has pretty bad post-covid, the thing that helped her most was getting on Citalopram. There's suspicions that many SSRI's have a anti-inflammatory effect on the brain, which might be the mechanism.

She's currently in oxygen therapy, we're positive about the effects but since it's dominating her life (and energy) at the moment it's hard to say what the effect is.


SSRIs have some nasty side effects though, including sexual dysfunction.


For sure, but so does heavy post-covid. It's a trade-off that's well worth it for her. It improved her memory and brain clarity a fair bit to the point that it's doable to get through the days hoping for a cure (or at least a way to get back to a normal life).


FWIW anxiety also results in exhaustion and brain fog, so I'm not surprised that it's had a positive impact in this way, it's just unfortunate that it's not without it's downsides.


I've built this a while back, using a previous version that runs Stable Diffusion on a raspberry pi zero 2 w:

https://hackaday.com/2023/09/19/e-paper-news-feed-illustrate...

https://github.com/rvdveen/epaper-slow-generative-art/


I just checked, and in the last 30 minutes a update has become available for my Pixel 5.

The security bulletin doesn't reference this CVE specifically but does mention a critical vulnerability that could lead to RCE.


The problem is that they'll use the opportunity to schlep a bunch of non-security related stuff into the update as well. That's the thing that really bothers me about these, that you can't say just the security patches and hold the telemetry/marketing/spyware/adware/crapware/malware/etc.


Updates outside the quarterly feature drops on Pixels are pretty much exclusively security patches so I have no idea what you're talking about.


This is what I'm talking about:

https://support.google.com/product-documentation/answer/1141...

Good luck setting things up in such a way that you only get security patches and not a whole bunch of 'improvements' to go with them.


Postgres has a extension called cube (https://www.postgresql.org/docs/9.6/cube.html) that can be used for up to 150 dimensions (which is a compile-time limit, you can have more if you compile Postgres yourself).

It's a pretty cool extension that does distance between points, intersections between n-dimensional cubes (hence the name), different distance metrics etc.

It'd be perfect for storing and searching through large amounts of n-dimensional embeddings, I'm guessing it's used for that already.


In my experience, the cube extension is unusable for >10M x 128D vectors without PCA. I'm using Faiss now with ~500M vectors, and it works great!


With how many dimensions are you using Faiss with 100m+ vectors? I’m currently looking a solution to handle 1024 dimensions for ~100m items.


On one index I'm using OPQ16_64,IVF262144_HNSW32,PQ16 with 128 dimensions initially.

1024 dimensions is a lot! Could you elaborate on what application requires that many? If it's a DNN layer output, your data must be sparse, so dimensionality reduction won't affect your recall if tuned properly.


It's actually a DNN layer output. I haven't considered dimensionality reduction, yet. Thanks for pointing my there, I'll look into it. Probably thats the better way to go.

Thanks a lot for your reply!


Fun fact, there’s a bug in the implementation where you can create cubes with much higher dimensions because one constructor doesn’t do the check.

Still wouldn’t recommend it though.


It saves you about 6% of fuel, assuming the launch location is on the equator, is suitable for roads and can handle a lot of noise / avelanches. Getting into space is the easy bit (energy-wise). Getting up to orbital speed takes much more fuel and energy.

The problem is that now you have to transport everything near and up the mountain, which costs a ton in logistics (getting a road up a mountain that can handle a entire assembled rocket isn't cheap, nor easy). Most launches have delta-v to spare because satellites are usually nowhere near the rocket's maximum payload weight.

tl;dr it can save 6% in a ideal situation, but the extra cost and logistical problems aren't worth it.


You seem to only be considering the fuel saving of the higher altitude. If we're considering a ground based mass driver launch, rather than a conventional rocket-only launch, then I think there would be a substantial practicality gain from firing into thinner air.

At the proposed 5000mph, air resistance at sea level would be tremendous. Greater atmospheric losses would entail either bringing more fuel to complete the orbit, or larger launch loop / greater acceleration force.


>tl;dr it can save 6% in a ideal situation, but the extra cost and logistical problems aren't worth it.

Unless you launch by means of a mass driver/rail gun [1] built into the side of Mt Everest with a piggy backed elevator for tourists. Tourists would arrive to a pressurized viewing area at the summit and have the option of donning an oxygen mask, going outside and posing for photos next to a cutout of Sir Hillary. I have never understood why serious rock climbing friends get so upset whenever I have mentioned this idea over the years.

1 https://en.wikipedia.org/wiki/Mass_driver


Skip Everest and go with Mt Kenya. It's equatorial location means that you are getting a nice delta-v boost, its shape is more suited to this purpose, and it is far more accessible.


I always thought they should just make stairs on Everest..


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: