Viewing profile — dustyharddrive

6. is a sign of bad UX but not leakage to the recipient.

https://media.ccc.de/v/39c3-a-post-american-enshittification...

The founder... runs a crossposting bot here: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... spammed package maintainers: https://news.ycombinator.com/item?id=31588…

Great news for this site's most prolific spammer!

One might wish to avoid overbought and uniquely unethical companies.

I mean a custom index, but not one of those fintech apps with small limits on the number of stocks.

Is there a direct indexing service that doesn't have exorbitant fees?

That's the latest ESR ( https://www.mozilla.org/en-US/firefox/organizations/notes/ ), which seems good enough for Tor Browser.

They pivoted to "AI": https://browsercompany.substack.com/p/letter-to-arc-members-...

Arc has been abandoned.

https://www.freetaxusa.com/privacy > The information given may be used to improve and develop and train our artificial intelligence and other machine learning models.

nu 0.103.0 released with background job support a couple months ago. Maybe give it another shot?

Bad for Oracle or its victims?

This looks very GDPR compliant!

Why sign their limitation of liability?

If this is about OTF, do you also distrust Let's Encrypt, Quad9, Tails, F-Droid, Signal, and Tor?

Keep in mind that Startpage is owned by an American advertising company: https://en.wikipedia.org/wiki/System1

It's FOSS and maintained by Tor Project team members: https://gitlab.torproject.org/tpo/applications/mullvad-brows...

Maybe they've used those names to test their OpenAI-compatible API ( https://api-docs.deepseek.com )?

And you can run one written in a memory-safe language, like Caddy.

Anyone have an informed preference between MLKEM and SNTRUP?

> CPU vulnerabilities These are another source of obselence. Intel generally sets an "End of Servicing Updates" date at seven years post-launch.

> every email through "git send-email" contains my original IP address for everyone to see Is this the fault of git or your SMTP provider? I looked through a mailman archive and co…