Apparently I’m wrong about this… the preview is said to be created by the server:

https://links.hackliberty.org/comment/1068761

EDIT: well, apparently it’s questionable. No one knows with confidence.

So does that mean jlai.lu is blocked by lecho.be? I figured it was more likely that lecho.be was blocking Tor, thus blocking my connection.

Yeah this article caught me by surprise. Natural gas is naturally odorless so that probably works against awareness.

I tend to be lazy about turning on the loud fans which downgrades the ambiance. But I need to change something because grease cakes up on everything near the oven and on the cabinets. My range hood is also the ventless style, which must be totally useless against the benzine byproduct.

I will certainly put more thought into kitchen design in the future. The gas appliances should probably be in the corner of the room so there are fewer directions to control, and the hood should probably be big, industrial, and vented outside. It’s a shame because I might prefer the gas stove to be in an island layout or at least centrally located.

It depends on what you’re baking. You wouldn’t want your cake to have a crispy hard crust on the outside, but you would want that with bread and pizza.

That’s interesting but it seems like an incomplete answer. I’ve read that it’s very common for people to install a range hood that’s too small. If it’s true that range hoods are often under-sized, then it naturally follows that they would often be ineffective. So I would like to know the answer in terms of a high-end well-designed & /big/ range hood. I would also expect a low hood to be more effective than one installed high above the stove.

indeed some houses have gas-fired wall heaters which have shitty ventilation, if any. In which case the air would of course be moist.

It’s also worth noting that moist air feels warmer and is not prone to any evaporative cooling effects. Some people will vent their vented dryers into the house to boost the humidity in order to save on heating costs.

Indeed. And it’s a needlessly destructive form of sanitization. That is, sanitizing properly normally means replacing the special characters with an encoding to ensure literals render.

I think this is a regression. IIRC, there was a time when a removal only removed it from the timeline. You could still reach it via the modlog. IIRC. But those days are gone. It’s a shame because it’s important for the community to be able to evaluate the mod’s decision making.

I’ve even seen cases where an over-zealous mod gets embarrassed by the mod log and purges the mod log itself to remove traces of the censorship itself. I suppose that’s only possible if the mod is also an admin.

Great find! Glad to see there are some onion hosts as well.

Any idea how to adapt the monero.stackexchange link in the sidebar? The code.whatever.social page cannot handle that link apparently because it does not lead to a specific thread.

There are bug reports and then there is user support. There’s some confusion because I filed a bug report in a user support community (because there is no bug reporting community).

Indeed the user support solution is to either request that the admin to change the slur filter config, or change instances. But the purpose of the thread was to report a bug in an in-band way (without interacting with a Microsoft asset [#deleteGithub]).

I can see your point in many situations but when I say I am the one b*tching (myself… in the 1st person), in this context I am not saying I am acting badly myself. So the “women are bad” narrative doesn’t follow. In this case the word merely serves as a more expressive complaint.

If someone were to talk about someone else b*tching, it might well be what you’re saying, as they are complaining about someone else complaining & maybe they oppose that other person complaining or their aggressive style thereof.

GDPR gives people a fair amount of protection and it is enforced.

Not in my experience. I have filed complaints of ~20+ GDPR violations under article 77 going years back. Not a single one of them enforced to date. These cases just sit idle for years. The problem is the GDPR gives no recourse when DPAs fail to honor article 77 obligations. It’s toothless.

https://www.enforcementtracker.com/

That shows a low count of cherry-picked enforcement actions. If you had a way to get a count of unenforced reports it would likely be an embarrassing comparison.

Do you know what I should look for? Is it the version number? I recall Lemmy was forked to Lenny, but not sure how to recognize Lenny instances.

(btw, fwiw, I wouldn’t use sh.itjust.works because that’s even more nannied [by Cloudflare]).

i’m not the best person to ask since I’m not maintaining and domains myself right now. I thought porkbun.com looked like a good choice at one point. They announced that they were going to move to cloudflare (just for the management portal), which was quite off-putting nonetheless, but it looks like they did not follow through with that.

EDIT-- I recently heard they are using CF for DNS and some people are avoiding #Porkbun for that reason.

Some sites use CF DNS just to have the ability to spontaneously switch on the proxy at will. They tend to keep the proxy turned off but then when traffic peaks a bandwidth detection mechanism switches on CF proxying. The problem with that is users don’t know from one click to the next whether their traffic will be intercepted. It can happen at any moment. So the deCloudflare project treats CF DNS cases no different than always-proxying sites.

So if you have no intention of using CF’s proxy, using a non-CF service would make more sense so your domains don’t get treated as CF. CF is not a good company to support anyway.

A list of Cloudflare-compromised domains is being tracked here. You can also use this query tool to lookup websites:

• onion
• clearnet

There is a browser plugin called BMCA which will detect when you click on a link to a Cloudflare service and redirect you to the archive.org mirror of that site so you don’t connect to CF. There’s another plugin that puts a strikethrough on CF URLs so you know before you click if something is CF’d. Those tools along with others are published here:

http://wmj5kiic7b6kjplpbvwadnht2nh2qnkbnqtcv3dyvpqtz7ssbssftxid.onion/dCF/deCloudflare/-/tree/master/tool?ref_type=heads

Search engines have become extremely polluted with Cloudflare sites in the results. There is a search service called Ombrelo that filters out CF sites from the results:

http://ombrelo.im5wixghmfmt7gf7wb4xrgdm6byx2gj26zn47da6nwo7xvybgxnqryid.onion/

W.r.t. a list of CF’s dangers, I don’t know of a paper that covers that as a thesis. A lot of the problems with Cloudflare are documented here and in other documents in that same repo.

This page covers a lot of Cloudflare issues:

https://git.kescher.at/dCF/deCloudflare/src/branch/master/subfiles/rapsheet.cloudflare.md

The 2nd link on that page goes to:

http://cryto.net/~joepie91/blog/2016/07/14/cloudflare-we-have-a-problem/

which details the traffic exposure to #Cloudflare as a consequence of Cloudflare holding the keys & terminating the tunnel (thus performing the decryption). Indeed the padlock is misleading as most users believe the tunnel goes all the way to the source website.

edit: BTW, I see that you are on #lemmyWorld. You might be interested in knowing that that’s also a Cloudflare site. Cloudflare sees your login credentials, your IP address, and everything you do with your lemmy account. As far as gatekeeping goes, Lemmy World has been manually configured to be less exclusive than default-configured sites like stackexchange. E.g. I am blocked from stackexchange but not from lemmy world.