Randomly clicking on the map led me to learn about this: https://en.wikipedia.org/wiki/Laconia_incident

Would love to be able to filter for events with a Wikipedia page (assuming they were the most significant)!

Thanks for the report!

We have clarified the documentation, sorry about the confusion! 16GB should be enough but it requires some vLLM cache tweaking that we still need to work on, so we put 24GB to be safe. Other deployment methods and quantized versions can definitely fit on 16GB!

Shouldn't it be much less than 16GB with vLLM's 4-bit AWQ? Probably consumer GPU-ish depending on the batch size?

Does no one else find it disturbing to publish the identities of these public employees with their salaries? Even if the data is freely available somewhere, this is high visibility. Would the article have been any less interesting if their names were anonymized and their privacy slightly respected?

I find that publishing the names and salaries of random S.F. security guards is quite an unsettling level of transparency.

A few years ago, the package I received contained a bottle of water instead of the phone I ordered. Amazon promptly refunded me and I was quite pleased, because I was a bit concerned by how I would sound to the customer service representative telling this story

On my end examples do not work (empty placeholders) with Firefox (on Linux). They work well with Chrome though.

The FP16 7B version runs on my Ubuntu XPS with 32GB memory, ~300ms/token. 13B also works but results aren't really good (the model will loop after a few sentences) so parameters probably need tuning.

So far I'm unable to reliably generate outputs in a different language than English, the model will very quickly start to translate (even if it's not asked) or just switch to English.

Funny coincidence that I have received a notification from the Play store this morning saying that analysis of my app (with super tiny outreach) showed that my Data Safety Form was inaccurate and asking me to fix it asap.

Seems like letting the user enter an email address to recover his password counts as email collection (he cannot subscribe, provide or see his email using the app, hence the initial form I submitted).

If you're sending the email address to a server (which is presumably needed to recover a password), I think this makes sense. Apple/Google has no way of knowing or verifying what the the server is doing with that data.

Absolutely, I meant that the app is not used to collect the email address since it is already in our system but it is true they have no way of knowing.

Basic plan is $35/m which is much higher than alternatives discussed in this thread, isn't it?

Especially seeing as you can outright have a full, tiny VPS 24/7 for $2.50/mo or $30/yr from Vultr. I suppose there's a value add in terms of not necessarily needing to setup your own install, but if that's something you're comfortable with I don't quite see the point.

You're right, this is more expensive than VPSs alternatives.

We assumed commercial use cases for that price so the benefits of not having to deal with servers complexity + access control + etc.. are quickly paid back.

For hobby projects, we are thinking of creating a free plan