rationably

From the Privacy Policy:

> When you use the Service, we collect and store: > Input prompts and parameters submitted to the API

For how long and what for apart from the transient compliance/safety checks?

While we have you here, could you please clarify a point in your privacy policy?

> For data collected from the UI or other usage: We retain the personal information described in this privacy notice for as long as you use our Services

I have two quick questions:

1. Why are UI prompts and responses kept for the entire life of the account?

2. When an account is closed, is the data actually deleted or just de-identified?

There is also NotepadNext which is oddly similar, sans the Lua: https://github.com/dail8859/NotepadNext

Is there a link to the dataset in machine-readable format?

Do you plan to release Sweep 3B/7B on HF?

Unbelievably, still supports IE 11 which is scheduled to be deprecated in jQuery 5.0

And to add to the above, is there a list of the websites you use and any information on sampling methodology? Is it perfectly random or weighted? Do you trust the timestamp from an RSS feed?

Comments like this make me think that a "downvote" button at HN would be quite handy.

Have you considered Sourcehut? sr.ht

New Qwen3 or older Qwen2.5 in larger sizes would be great.

> some kind of minority, politically active, or in legal trouble

That's... Sufficiently concerning, don't you think?

Do you plan to offer a high-quality FIM models in the bundle? Would be handy to perform autocompletion locally, say via the Qwen3-coder.

The age of "vibe coding" is upon us.

- Introduction section in the privacy policy:

    Flask App ("we", "our", or "us") respects your privacy and is committed to protecting your personal data.

- Contact us section, also in the privacy policy:

    Email: privacy@worldnewsmonitor.com
    Phone: +1 (123) 456-7890
    Address: 123 Main St, City, Country

...or Marshmallow, which allows one to do many complex validations in a relatively trivial manner.

I can use it for personal needs, sure. Bringing AGPL in a closed-source project is a no go for obvious reasons.

It says nothing about "asian people". Verbatim quote, in full:

> The contest is open to individuals or teams of individuals who are legal residents or citizens of the United States, United Kingdom, European Union, Canada, New Zealand, or Australia.

The fact that it's "backed by NVIDIA" and licensed under AGPL-3.0 makes me wonder about the cost(s) of using it in production.

Could you share any information on the pricing model?

If you are on Debian, ROCm is already packaged in Debian 13 (Trixie).

llama.cpp can be built using Debian-supplied libraries with ROCm backend enabled.

From commenter's website [1], "About" section:

> living a loveless life in the dusk of decadent Western Europe

If it quacks like a duck...

[1] https://world-playground-deceit.net/about/me.html

Can relate, try searching "s0ix battery drain".

> she kitted out her home PC with a terabyte of memory and an Nvidia processor so she could play Counter-Strike and World of Warcraft.

I wonder if anyone bothered to proofread the article.

> yet to see anything better.

Try Beyond Compare v5.

Could you provide an example where maintainer "ripped out" a feature because of a strictly political reason?

Thank you, Internet stranger. This LLMNR/mDNS dichotomy has been on the back of my mind for quite some time. You've made it clear.