resist1984 @resist1984@social.privacytools.io

@eff @HP proposed new rule: the US Bureau of Weights & Measures must require an estimated price per oz or mL on all printer ink packaging, and audit them for accuracy. Regulate it like fuel.

@booteille @dansup @jeremiahlee and since it's in git, you can see the maintenance dates for yourself.

@jeremiahlee @dansup @booteille if you can't counter cited facts with anything at all, you've obviously failed to support your claim. That page covers CF's use of #hCAPTCHA, which was actually a recent change.

@jeremiahlee @booteille @dansup Actually #CloudFlare is incompatible with a free & open society, and particularly incompatible with the #decentralized society that a fediDB project seeks to enable. A company that doxxes child porn whistle blowers is pretty far from tolerable. https://git.disroot.org/cyberMonk/liberethos_paradigm/src/branch/master/rap_sheets/cloudflare.md

@dansup @booteille @jeremiahlee great to hear that!

@jeremiahlee @dansup Bingo. The URL is where the dirt lies. It's a #CloudFlare site: https://social.privacytools.io/@resist1984/105843803109732715 #FediDB needs to clean up their act before I'll consider looking any further. /cc @booteille

If #CAPTCHA registrations are killed by robots, then people are pressured to do what they should have done in the 1st place: walk away from CAPTCHAs & stop engaging CAPTCHA-blockaded services.

I hear #hCAPTCHA gives a way to register to avoid #CAPTCHA solving work. Obviously that attacks #privacy, as all each user's activity can be aggregated together. So why not have a cookie exchange program where registered accounts circulate in a pool until they're cut off? Robots could use those cookies too, which is a good thing. If it forces them to stop registrations, even better.

@anonypla #Keybase is terrible for #security. Avoid it. https://dev.lemmy.ml/post/31190

@Steinar That sounds good to me, so I had a look at #reST. The deterrant is that it doesn't give a way to get the "<details>" tag that I've gotten attached to. There also seems to be a widespread temptation to use #readthedocs.org, a site that I won't touch because it's a #CloudFlare site. Anyway, I appreciate the tip.

@lightweight
Tim Wu's essay "The Tyranny of Convenience" can explain some of the lack of incredulity. People fight the inconvenience of change & the burdon of knowledge. Easier to make decisions on autopilot.

A meat eater who loves pork doesn't want to hear about how they boil the pigs alive to melt the fur off their skin before slaughter. That knowledge invokes responsibility that might lead to loss of their enjoyment of bacon.

I thought there were only 1 or 2 markdown standards and ton of non-compliant wild implementations. Now I'm realizing that there are at least 5 different standards. I think that actually disturbs me even more. Before making a new standard, why not 1st check if an existing standard is close enough?

Does the world really need 5+ different markdown standards?

@anmol That would really help portability to Zap, so someone could use gitea to draft an article then publish it on zap.

@anmol the docs page times out for me, so I didn't realize it supported a mix of languages. that definitely sounds interesting though. I think in principle it would be most useful if it supported GitHub Flavored Markdown, which has this spec: https://github.github.com/gfm/ in addition to your other extensions.

#OpenSPF is the reason I cannot email #RMS.

-- legitimate non-spamming user

@fsf

The #gnu.org mail server has become so restricted that I can no longer post to *@gnu.org mailing lists or reach RMS.

RMS had the fedi acct @rms@gnusocial.no in 2019, but apparently no longer. (strangely the website says no such user, but the 2019 timeline is still reachable via the API)

Would someone plz tell me if he has a gnu social account somewhere else?

/cc @jack