Privacy

4703 readers

190 users here now

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 3 years ago

MODERATORS

Ategon@programming.dev

danielintempesta@programming.dev

A tool for concealing writing style to evade linguistic fingerprinting (git.anarchists.space)

submitted 1 month ago by cm0002@mander.xyz to c/privacy@programming.dev

3 comments fedilink hide all child comments

Everyone has a unique writing style, word choice, sentence structure, punctuation habits and that can be used to identify them. Lingunymous rewrites your text using a local LLM to mask these patterns, making it harder to attribute writing to a specific individual.

Use cases include:

Protecting anonymity when publishing sensitive or controversial content

Evading authorship attribution and stylometric analysis

Separating your personal writing fingerprint from pseudonymous accounts

top 3 comments

sorted by: hot top controversial new old

[–] logging_strict@programming.dev 0 points 1 month ago (1 children)

The amateurishness is unfckingbelievable. This is the first time seeing a requirements.txt file and no pyproject.toml. What is that requirements.txt for exactly?

packaging is 80% of coding.

This includes: tests, dev environment (tox.ini, tox-test.ini, tox-req.ini, pre-commit, Makefile), full docs not just a README, gh workflows, stubs, pyproject.toml file ffs, static type checking with both mypy and pyright.

This is worse than strictyamlx which i actually would like to use, but come on! It's also terribly amateurish. What is with the partial typing signatures? Listen to Yoda, you either do or you don't, there is no try.

Everyone can be brilliant, everyone is brilliant, but packaging separates the little boys in their diapers from the men.

This author is sucking his thumbs in full view of the public.

If this project was a dart board, a blindfolded drunk could point out its shortcomings. Where to start?

Why even list the packages purpose and features, just beg/plead/grovel for help.

[–] thesmokingman@programming.dev 2 points 1 month ago* (last edited 1 month ago) (1 children)

The pyproject.toml spec is ten years old. Python 3 is almost twenty years old. The community standard moved within the last five years. Tox is only necessary if you want to validate across specific versions so it can be replaced by tools like Poetry. If you’ve got GitHub workflows that’s the standard anyway so you should be running something like act locally. Static typing redundancy is a waste of compute.

If you’re going to be an asshole, make sure you can back everything up. You can’t so I’d recommend taking a breath and going outside.

Edit: I looked through your GitHub and even though your profile name is “msftcangoblowm” you don’t seem to use .yaml but instead the YAML extension Windows devs use.

[–] logging_strict@programming.dev 2 points 1 month ago

Thank you for introducing me to act. First time seeing it.