r00ty

Yeah, it shouldn’t happen in a release. But, if I had a penny for every time I’ve seen the last minute development that wasn’t tested yet and not even due for the current release squeezed in. I’d literally have a pound, or dollar or whatever else has 100 pennies in.

In a professional sense my experience is that they’re more often the result of under-staffing and rigid, fixed release schedules.

Yeah. I didn’t understand what they meant by the wtf there. Seemed to me someone wondered if the Action would have a localised version of i (making this stay lowercase on a phone was harder than it should be) or if it used the same i. So made a simple test for it.

Not really sure it’s a wtf unless they expected a different result.

Didn’t have the link to hand. But a search turned this one up: https://reggiodigital.com/blog/nginx-rule-blocking-bad-bots/ it looks to be the same list, and you can see the ones I’ve added to the end of that list.

Hmm, I took an original list and added to it. You got a website I can check? If so I’ll happily remove. I don’t mind slow web crawlers at all.

So on my mbin instance, it’s on cloudflare. So I filter the AS numbers there. Don’t even reach my server.

On the sites that aren’t behind cloudflare. Yep it’s on the nginx level. I did consider firewall level. Maybe just make a specific chain for it. But since I was blocking at the nginx level I just did it there for now. I mean it keeps them off the content, but yes it does tell them there’s a website there to leech if they change their tactics for example.

You need to block the whole ASN too. Those that are using chrome/firefox UAs change IP every 5 minutes from a random other one in their huuuuuge pools.

Yeah, I probably should look to see if there’s any good plugins that do this on some community submission basis. Because yes, it’s a pain to keep up with whatever trick they’re doing next.

And unlike web crawlers that generally check a url here and there, AI bots absolutely rip through your sites like something rabid.

If you’re running nginx I am using the following:

if ($http_user_agent ~* "SemrushBot|Semrush|AhrefsBot|MJ12bot|YandexBot|YandexImages|MegaIndex.ru|BLEXbot|BLEXBot|ZoominfoBot|YaK|VelenPublicWebCrawler|SentiBot|Vagabondo|SEOkicks|SEOkicks-Robot|mtbot/1.1.0i|SeznamBot|DotBot|Cliqzbot|coccocbot|python|Scrap|SiteCheck-sitecrawl|MauiBot|Java|GumGum|Clickagy|AspiegelBot|Yandex|TkBot|CCBot|Qwantify|MBCrawler|serpstatbot|AwarioSmartBot|Semantici|ScholarBot|proximic|GrapeshotCrawler|IAScrawler|linkdexbot|contxbot|PlurkBot|PaperLiBot|BomboraBot|Leikibot|weborama-fetcher|NTENTbot|Screaming Frog SEO Spider|admantx-usaspb|Eyeotabot|VoluumDSP-content-bot|SirdataBot|adbeat_bot|TTD-Content|admantx|Nimbostratus-Bot|Mail.RU_Bot|Quantcastboti|Onespot-ScraperBot|Taboolabot|Baidu|Jobboerse|VoilaBot|Sogou|Jyxobot|Exabot|ZGrab|Proximi|Sosospider|Accoona|aiHitBot|Genieo|BecomeBot|ConveraCrawler|NerdyBot|OutclicksBot|findlinks|JikeSpider|Gigabot|CatchBot|Huaweisymantecspider|Offline Explorer|SiteSnagger|TeleportPro|WebCopier|WebReaper|WebStripper|WebZIP|Xaldon_WebSpider|BackDoorBot|AITCSRoboti|Arachnophilia|BackRub|BlowFishi|perl|CherryPicker|CyberSpyder|EmailCollector|Foobot|GetURL|httplib|HTTrack|LinkScan|Openbot|Snooper|SuperBot|URLSpiderPro|MAZBot|EchoboxBot|SerendeputyBot|LivelapBot|linkfluence.com|TweetmemeBot|LinkisBot|CrowdTanglebot|ClaudeBot|Bytespider|ImagesiftBot|Barkrowler|DataForSeoBo|Amazonbot|facebookexternalhit|meta-externalagent|FriendlyCrawler|GoogleOther|PetalBot|Applebot") { return 403; }

That will block those that actually use recognisable user agents. I add any I find as I go on. It will catch a lot!

I also have a huuuuuge IP based block list (generated by adding all ranges returned from looking up the following AS numbers):

AS45102 (Alibaba cloud) AS136907 (Huawei SG) AS132203 (Tencent) AS32934 (Facebook)

Since these guys run or have run bots that impersonate real browser agents.

There are various tools online to return prefix/ip lists for an autonomous system number.

I put both into a single file and include it into my web site config files.

EDIT: Just to add, keeping on top of this is a full time job! EDIT 2: Removed Mojeek bot as it seems to be a normal web crawler.

Not sure how it is in the US. But here in the UK there’s two ways a business can export.

1: They pre-clear the customs duty and include it in the sales total (so it’s like paying sales tax at the checkout, except it’s the pre-cleared duty fees). Then the parcel has a nice duty paid stamp and goes straight through customs (I guess unless customs are suspicious and check into it).

2: They just charge you the item price with no tax applied. In which case you need to pay local tax and duties applicable once the product arrives. Here it’s a bit different. They will hold it at the local depot and you can either go there and pay + collect, or you can pay online and it will be rescheduled for delivery once you pay.

As others have said, it’s not a scam. There’s no requirement for a business to do option 1, and it’s likely only viable for large businesses to register and have someone/software that knows the various duties required for various countries.

I’ve ordered from newegg and B&M in the past for example, and in both cases the items were pre-cleared and arrived promptly without any hassle.

Maybe there’s something similar for imports into the US too?

This is not even a surprise. It’s exactly what I expected in fact. Just don’t use X/Twitter/whatever we call it this week. Just don’t use it, delete your account. It’s literally a platform for Musk and the people that think like him now. Even taking part is validating him right now.

The sun always shines on pc.

Only one of them.

I would agree. The best thing to do is as others have said. Disable read receipts and let them continue to get new numbers and wonder if they’re even getting through, document each one and the messages received but don’t respond. Keep the reports to police up to date with latest info. Even if they do nothing, it’s good to have a paper trail.

Not really processor based. The timestamp needs to be ulong (not advised but good for date ranges up to something like 2100, but cannot express dates before 1970). Or llong (long long). I think it’s a bad idea but I bet some people too lazy to change their database schema will just do this internally.

The type time_t in Linux is now 64bit regardless. So, compiling applications that used that will be fine. Of course it’s a problem if the database is storing 32bit signed integers. The type on the database can be changed too and this isn’t hard really.

As for the Y10K problem. It will almost entirely only be formatting problems I think. In the 80s and 90s, storage was at a premium, databases were generally much simpler and as such dates were very often stored as YYMMDD. There also wasn’t so much use of standard libraries. So this meant that to fix the Y2K problem required quite some work. In some cases there wasn’t time to make a proper solution. Where I was working there was a two step solution.

One team made the interim change to adjust where all dates were read and evaluate anything <30 (it wasn’t 30, it was another number but I forget which) to be 2000+number and anything else 1900+number. This meant the existing product would be fine for another 30 years or so.

The other team was writing the new version of the software, which used MSSQL server as a back-end, with proper datetime typed columns and worked properly with years before and after 2000.

I suspect this wasn’t unusual in terms of approach and most software is using some form of epoch datatype which should be fine in terms of storing, reading and writing dates beyond Y10K. But some hard-coded date format strings will need to be changed.

Source: I was there, 3000 years ago.

I thought the web page layout looked familiar.

Resistance alone doesn’t cause heat. Drawing current through resistance causes heat at the point (or points) of resistance. Which is why I clarified that it’s not likely so much a problem on small loads.

This is why resisters come in different physical sizes. Because they have differing abilities to dissipate power as heat.

A good example is of dummy loads in radio use. Which needs to dissipate the power output of a radio. That can be anything from milliwatts to a kilowatt. Up to probably 50w they will have a basic heatsink. I’ve seen huge drums filled with oil as 50ohm resisters to handle up to a kilowatt of dissipation.

I think a lot of people are mostly on the money here. It’s to do with resistance. Now, I’m not a qualified electrician, but I’m an amateur radio license holder and a lot of what you learn for that is applicable here.

The main problem as many have said is resistance. This comes about from both the length of the conductors but also from every plug/socket connection adds resistance. Also in the case of the non extension socket multipliers, as you add more the weight bearing down would also likely start to make the connections less secure causing more resistance and possibly adding to the problem through arcing.

Now the resistance alone on small loads likely wouldn’t be a huge problem. But if you had a large enough load (specifically at the end of the stacked connectors/extensions), or a fault that caused a larger than expected load the current would cause the resistance to generate heat.

There’s a lot of ifs and maybes involved, but really why do it? There’s really no real world situation to need to have a dangerous amount of extensions like this though.

For larger loads here in the UK there’s some very specific other concerns when dealing with ring mains. But really you’d need to do really weird/unusual things for that to become a problem.

Instance level censorship isn’t much for the user to worry about (I run my own, so it’s zero problem for me). Most censorship happens at the group level by group owners, and the admins on the instance the group is hosted.

I still don’t have a problem with it though. You subscribe to a group on a certain instance, you cannot be too surprised if you get censored there.

Yeah but they’re a cheat. They’re lithium cells regulated down to 1.5v. Good ones are rare, when you find good ones they’re generally expensive and because they’re regulated down you generally get 100% battery showing until just before they fail.

I used them for some voltage sensitive stuff, but finding a brand that held a good charge for more than even 50-100 charges was hard.

Nimh is much better for anything that won’t be upset about the voltage too much.

deleted by creator