Salamander @ Sal @mander.xyz

Posts

463

Comments

1,016

Joined

4 yr. ago

Moderating

---

Thanks :)

It depends. In my experience: in an academic laboratory I have been able to use common sense.

For example, gloves go on when working with strong acids/bases. The statement:

gloves apparently only give researchers a false sense of security that can dull the sense of touch and prevent you from recognizing chemical exposure

Does not apply as much when you are working with such corrosive agents, because you really should never be in a position where spilling 4 M HCl into your hands would go unnoticed.

When working with large quantitites of oils, even if non-hazardous, gloves go on and they will probably get oil in them.

When working with cell cultures, the goal is often to not contaminate the cultures. Some people prefer to wash their hands thoroughly and not use gloves, and they have been working at it for many years and they seem to do just fine. It's a risk mitigation strategy - if the cultures have antibiotics and fungicides, risk is already not too high.

In an industry setting it is different. Companies often comply with specific standards and health and safety regulations. While the individual can use common sense, the people in charge of ascertaining compliance (sometimes 'EHS', Environment, health and safety personnel) aren't necessarily chemists themselves, nor should they need to be aware of the identity of the transparent liquid in the flask that you are holding. So, generic rules are often set in place not only because of their practical utility but also to simplify enforcement. In some cases external auditors can come in (announced or not) and verify compliance - this, again is much simpler when the rule is 'lab coat behind yellow line, gloves always on when touching a container with a liquid' than having to interview each person to understand what they were touching without gloves and to understand their philosophy of why they chose to do so.

I have experienced issues both over tor and over clearnet. The tor front-end exists on its own server, but it connects to the mander server. So, the server that hosts the front-end via Tor will see the exit node connecting to it, and then the mander server gets the requests via that Tor server. Ultimately some bandwidth is used for both servers because the data travels from mander, to the tor front-end, and then to the exit node. There is also another server that hosts and serves the images.

What I see is not a bandwidth problem, though. It seems like the database queries are the bottleneck. There is a limited number of connections to the database, and some of the queries are complex and use a lot of CPU. It is the intense searching through the database what appears to throttle the website.

By hand. We are only two people, and we usually clean after we cook/eat. When one is cleaning only 2 plates + a pot/pan at a time, it is easy to use little water. Spray of soap, metal scrub, sponge scrub, and then turn the tap on to rinse for a few seconds. Utensils get individually scrubbed and then all rinsed together for a few seconds.

Maybe when we have kids a dish washer will make sense.

AGUCUAGCAUAC

I have been happy with my Garmin. It is functional without having to connect to anything, and data can be easily exported to a computer for more advanced processing. It is a handy GPS receiver that lets me monitor heart rate and log running metrics.

That's good! There's some hope that this won't last forever then. Thanks.

And it's interesting that the challenge via old.lemmy.ca was so impactful. The first wave of bots that I noticed also came through an Mlmym front-end that I make accessible via tor. But lately they have been hitting directly via the regular front-end.

Thanks! The problem I run into is that the bags end up taking up a lot more space than the components themselves. Yesterday I started testing printing a small label with the component's code and sticking it into the reel.

Ooh, I like that idea for the larger components that don't fit into the smaller binder. I bought some trading card sheets to test. Thanks :D

Did this spike for you these past weeks? I'm not sure if it just happens to be our instance's turn or if they have up-scaled their efforts. I have been playing wack-a-mole with IP ranges.

I do have a wall with similar boxes. From the image, I am not sure if they are the same size. I just measured one of my small drawers and it is 14 cm x 5.5 cm x 5 cm. Since I have many different tiny components, I quickly ran out of space when I tried to give each component its own drawer.

But I think that I might be able to do a better job with these if I take everything out and start organizing again. I set the rules for how to place things before I started buying SMD components, and many of the through-hole components I can combine without problem. An improvement would be if I can find something like this but with many more and much smaller boxes.

When you mix different components into one of the boxes, do you have a system to label them? Or are the components easy enough to recognize by looking at them?

This morning I woke up and a new IP sub-net (43.173.0.0/16) was excessively hitting the site from multiple IPs, probably scraping, making the site unresponsive. I blocked that sub-net and the site is responsive again.

Thank you.

A few days ago, I blocked several IP ranges to solve this. I unblocked them about two days ago in an attempt to solve some federation issues... The bots from this IP range came back.

This time I blocked only the IP range that has the most bot-like activity. Hopefully that resolves it.

Woah! Congratulations!!! 🥳 🎉

No problem! Happy to contribute

No, I always yesice

How dare you

Three kids in a trenchcoat

Thanks!

I don't see those specific IPs, nor 16514. But now I see what scrapers tend to look like in the logs :)

I am now pretty sure that the cause was scraper-like activity coming from the Mlmym front-end that I am serving over an onion site. I am not sure if it randomly started mis-behaving or if a tor scraper was using it.

After blocking this, federation was restored, performance increased, and CPU use came down: