DDG is just repackaged Bing. Always has been. I remember looking into them when I was ready to job-hop many years ago, and they asked for dedication to their search engine as their foremost requirement for employment. It's the "drop-shipping" equivalent of search engines.
I really don't get that sentiment. Currently Kagi is just as dependent on Google as DuckDuckGo is on Bing. That might only be temporary of course and Kagi does seem to be working on a search engine of their own.
Rather than wanting Kagi to take the place of DuckDuckGo, it would would be better if Kagi could take users from Google, and then when ready, drop Google as a search provider.
DDG used to be the HN darling and you would get downvoted for saying anything negative or even insinuating that they are relying on Bing. Now the spot has been overtaken by Kagi but it looks like it suffers from the same problems. The counterargument that they have their own index as well is the same that was used for DDG, when the reality was that it was only used for widgets and other fluff. Let's see how it plays out for Kagi.
I don't think they use Bing, but yes, Google, Marginalia, Yandex, Brave and others. I still fail to see how that's different to DuckDuckGo, who also run their own crawler. It's really weird that people are almost hating on DuckDuckGo for how they run their search engine, while applauding Kagi, for doing the same, but with a different business model.
You can buy access to the Google Search API, which is what I assume Kagi does. Building your product on being able to circumvent some Google restrictions seems like a bad business move, if you can buy the same service for a reasonable price.
I'm constantly DM'd at work about how I'm able to create the "cool drawings" in my blog/wiki posts, and I enthusiastically point to excalidraw.com.
I have a background in vector illustration, which is all about creating subpixel-perfect designs. I'm also a bit of a perfectionist, which I think a lot of people here can relate to. I mention this because the reason Excalidraw really works for me is that it frees me from worrying about design. When you literally can't create something that looks "perfect", you're freed up to just sketch your idea without worrying about the visual representation.
That post was fascinating. You are a model example of what progressive prison reform can accomplish and your story should be getting major press coverage if it hasn't already.
The Maine model of corrections indeed gets a fair amount of coverage in the "space" of criminal justice reform, as they are essentially carving the path. But outside that bubble (linkedin seems to be where a lot of that space is focused, but that could totally just be my perception as it's the only social media I'm allowed :P), it doesn't appear that many people really care.
I don't think it's responsible to replace http/1.1 with either of these protocols. They both seem like complex beasts with poorly understood corner cases and little consideration for the abuse potential.
My feeling is they both suffer “version-2-isms”, ie having added many nice-to-haves that are complex. That said, I think QUIC is a much, much bigger step. We are literally adding congestion and flow control to user space, as well as packet-level routing. This has been done before, but mostly for bespoke purposes (like UDT - or with per-OS batching, kernel extensions or at least kernel tuning). Now, it’s supposed to be general purpose, across hardware, platforms and languages.
Personally I think either QUIC makes it into kernels, or it will have a loooong time ahead of it with language- and vectorized/batched IO in the OS (maybe even down to the NICs?) catching up. Even the more mature implementations struggle compared with TCP today, for things like high bandwidth on consumer hardware. Not to mention CPU overhead and the battery drain that comes with it. (At least from my own high-bandwidth experiments)
Yes, I know a large part of web is already http3. But remember that http is used outside of browsers and data centers. I don’t know enough to back any specific proposals, but to me it sounds a lot easier to fix the tcp handshake, open 2-3 conns for the HOL-blocking issue, than to rearchitect the entire stack (and add new features) under UDP. I’m saying this as someone who is still very bullish and excited about QUIC.
For the rest of the universe, if you read patents then you are liable for willful infringement instead of accidental infringement, the penalties for willful infringement are much higher. This is why you should never read through patents without a specific purpose in mind if you have any plans of filing your own.
They're a powerful tool that lets you shopt off your foot and half your brains with the same bullet. However, this my router isn't compromised. MikroTik routers can easily be misconfigured to be insecure or misbehave. It's a Cisco clone, so that is the product you're buying.
I don't recommend them to anyone who doesn't enjoy and are familiar with the lower-level intricacies of network operations.
I accidentally ended up running one of the new gTLD registries for a while. It’s a lot more than $185,000 - that’s just the ICANN application fee. It’s all the other stuff that surrounds running a registry that is expensive. Might be cheaper if it’s “private” registry but you’d probably be looking at as least as much again on top.
We spent well over a million dollars on the various bits and pieces that were required to get set up - this was legals, consultancy fees, and all the paperwork and so on necessary to comply with the ICANN registry agreement terms, as well as our registry back end infrastructure provider - but that was for a registry selling domains to end users. That included putting a substantial sum in escrow for “registry continuity” - so if your registry goes bankrupt ICANN can ensure the registrants of domains are not left high and dry.
A big part of my role was to try and moderate costs as much as possible because the registry owners had been talked into the whole project by a consultant who had convinced them that their particular registry was going to make them $100m a year in registrations and renewals.
My job quickly became persuading them that spending $100k on some crazy thing was not going to achieve anything and trying to stop cash being burnt before they realised the whole thing was a crazy pipe dream.
I don’t recall the terms for private registries, but I’m pretty sure the detail will be on the ICANN site somewhere. Searching for “private registry operating agreement” or something similar might surface the relevant documents.
This is only if you have _no_ idea how to use very basic open-source tools to wreak havoc via some open proxies. The real cost of launching small-scale attacks like this is $5/month on your favorite VPS provider.
Open proxies? I heard about this more than a decade ago, but why would anybody in 2022 run an open proxy? Or are these open proxies unintentional, i.e. misconfigured?
Many of them are unintentional: a device sitting on the open internet has some vulnerability and gets exploited. Bad guy sets up a proxy on the device and uses it to click a bunch of ads using bots, or crawl Google results, or launch attacks, etc. Or, as mentioned below, they could simply be the result of misconfiguration.
Unfortunately, this type of abuse is essentially only acted on if you either (a) cause some kind of problem for ops at the VPS company, or (b) the victim tells on you. Even then, the absolute worst thing that will happen to you is your account will be closed. There is just no way on the modern internet to investigate/prosecute these kinds of things. That's why one of our primary goals with the free Cloudflare plan is to invert the problem: make DDoS go away by making it it free to mitigate.
