> FerretDB is an open-source proxy, converting the MongoDB wire protocol queries to SQL - using PostgreSQL as a database engine.
Based on this description I'd agree that FerretDB isn't a database itself. However the conversion between the MongoDB wire protocol to SQL queries could have bugs, data resiliency could be an issue if you need to guarantee writes, No guarantees of on-going support, etc.
New db's are always welcome but to use a brand new one in production would be very.... bold.
Can you elaborate on what you mean by not interrupting the scrape and instead flagging those pages?
Let's say you're scraping product info from a large list of products. I'm assuming you mean if it's strange one-off type errors to handle those, and you'd stop altogether if too many fail? Otherwise you'd just be DOS'ing the site.
It's in a container with xorg running. It doesn't need kernel level access but it does need userland access which it does have access to in the container.
There's a lot of telemetry, and a few other services such as time checking.
The features you're mentioning include the user syncing, translation, and DRM platforms (though you can add widevine to chromium, you cant add the others). Those are not the only things that call home to google.
Keep in mind this will only work for non-court-gag-ordered instances. If the US subpoenas Apple about an individual they won't be allowed to notify them.
I have no idea how this applies to other countries.
I think this is more like: "We noticed unusual API usage and we don't have a gag order so whatever it is, it's not likely to be good"
Disclaimer: I think everyone in this thread agrees we should try to improve the lives of all animals
> why not just stick with feeding the locals? At least those are free to decide to visit you or not.
This is almost never a good idea (for any animal). Assuming you're feeding them the right type of food (bread is terrible for ducks for example), you're training the animals to rely on humans for food. This both makes it more difficult for them to survive on their own should you stop feeding them, but for some of the potentially aggressive ones (like geese) will become comfortable approaching humans, even the humans who do not want to be near them.
I've read your stance on animal rescue places and I generally agree - most aren't good or are glorified zoos. But I do think there's genuine ones that are helpful, and I think between those and rescues where you can give the animal direct attention are the best ways to humanely assist animals who would otherwise die in the wild.
My problem is with the traders and terrible owners who only use them as a show piece. A good owner should be providing ample enrichment and attention
Leetcode only gets you pass the first round of interviews and not every company does them. I consider these useless textbook problems but you'll need them to get the job. They won't help you much in the job.
More importantly (imo) he needs domain specific knowledge. I.e. if it's going to be web development then he needs to start a web project with the backend in python. If it's stats/analysis he needs to start on analysis projects. Etc.
My advice is on making small projects that cover topics he'll be working on in the jobs he applies for to build a small portfolio. And brush up on the leetcode like a month before.
Take this with a large grain of salt, but possibly about 1/3 the size of coinbase and nearly 1/15 the size of binance by volume.
Using https://etherscan.io/gastracker#gassender to see who spends the most gas in ether (not the best metric but it's something) they're somewhere in the realm of a quarter the gas spending compared to binance and coinbase in the last 24 hours.
IMO - they're relatively tiny. They are not a common name in the crypto space outside of their aggressive marketing, and only recently have people really talked about them at all (in the crypto space).
They are not well established in the crypto space, I think they're going for a brute-force marketing approach to force their way in.
I apologize I misread OP's question. I incorrectly interpreted it as "hardware that supports opensource firmware such as DD-WRT/Tomato".
In terms of hardware like you mentioned there's few open source SBC's at all. Even fairly open hardware like the raspberry pi have a proprietary firmware blob. I guess it will come down to how strictly you define "open source". If you define it as "we have firmware/schematics for every chip on the board" then we'll likely never have that (I don't think even Linksys has that type of access).
I haven't stayed up to date with them to be honest. I've switched to ubiquiti access points with my WRT1200AC as just a switch/router. My plan is to upgrade to a x86 box with openwrt or something similar.
So if you had issues with the WRT3200acm I'd go a different route
They have a series of routers designed to support OpenWRT (which IMO is better then DD-WRT but preferences of course). If it supports OpenWRT then others shouldn't be difficult to load on it either.
I know some people think all scraping is bad or malicious. I'd like to point out this is a perfectly legitimate use case for it, in fact this is how Google Search operates.
Web scraping done correctly should be barely noticeable if at all to the operators. Don't send 10,000 req/s, have aggressive delays, make your retries extremely generous, try to avoid pages or actions you know are "heavy". You don't need to update data from every product page every 5 minutes.
I don't think so because there's rarely a drop in replacement unless you designed your board ahead of time for multiple options (of course exceptions exist, there's drop in replacements for many devices including the esp8266 I mention below).
But for example, an ESP8266 hasn't really lost much value in the past few years, and is unlikely to lose significant value if it sat on a shelf for another few years, so they don't mind a bit of an overstock.
Meanwhile the current year car model will lose a ton of it's value when the next model comes out so they don't want to risk over-stocking it.
All the big industries got scared when COVID hit thinking consumer spending was going to plummet so they drastically cut orders.
Meanwhile the IoT space has been growing rapidly in the past few years, and those suppliers didn't cut their orders. IoT devices like the ESP8266 can sit in a warehouse for the next few years before being sold for use in some smart lightbulb, but automotives will lose their value as they become last year's model.
With the supply chain disruptions and increasing consumer spending automotive industries basically lost their reserved spots are struggling to claw back their manufacturing and shipping capacity.
So basically in this game of musical chairs the automotive industries stood up while the IoT space stayed sitting, and then the supply chain disruption removed the chair the automotive industries had been sitting in before...
Yeah that's why I figure it'd have to be something fairly important - most people should at least know their area's emergency number, and hopefully at least one close friend/spouse/partner/parents to help you out. In the states we carry a paper with our insurance info which will include a tow company if you have towing insurance.
If like the sibling said they develop on-skin electrodes or micro-needle patches I 100% agree.
Currently it requires an invasive and risky brain surgery which AFAIK would be a definite no-go. At least in the US, this would likely be considered extremely inhumane unless it could be done without such significant risk of death or brain damage - given the nature of the surgery I find that unlikely.
In the cases where an invasive brain surgery would be permitted, I imagine torture would already be an option. Keep in mind torture doesn't have nearly the same risk of death and permanent brain damage as an invasive brain surgery.
Based on this description I'd agree that FerretDB isn't a database itself. However the conversion between the MongoDB wire protocol to SQL queries could have bugs, data resiliency could be an issue if you need to guarantee writes, No guarantees of on-going support, etc.
New db's are always welcome but to use a brand new one in production would be very.... bold.