Counterpoint: I once wrote a paper on accelerating blockciphers (AES et al) using CUDA and while doing so I realised that most (if not all) previous academic work which had claimed incredible speedups had done so by benchmarking exclusively on zero-bytes. Since these blockciphers are implemenented using lookup tables this meant perfect cache hits on every block to be encrypted. Benchmarking on random data painted a very different, and in my opinion more realistic picture.
In my experience this affects techie users just as much. Especially when there is a UI that has been crafted and slowly perfected over the years, and where any remaining idiosyncrasy has long been learned by the user, changing that UI has profound negative impact on the productivity of anyone using the platform.
I have rarely seen UI changes where users were genuinely excited to have a new UI with the understanding that they'd have to learn new paradigms. Most web apps should still be Bootstrap apps, but of course then you can't put that on a giant dashboard wall at a conference ;)
No it's not, not if you want to win customers from the US. Their annual budgets are in USD, so they don't have the flexibility to pay more next year just because the foreign exchange rate has shifted. You take the foreign exchange risk by listing prices in USD, but it could just as well be a windfall, and your customers pay stable prices in return.
I just wanted to say thank you for your work on Nomad. It's one of the most pleasant and useful pieces of software I have ever worked with. Nomad allowed us to build out a large fleet of servers with a small team while still enjoying the process.
I don't know why / how messages should be ordered. NSQ is a message queue and not a log. Some messages take longer to process than others, and some messages need to be re-queued and re-tried out of order, and that is a very common use-case.
I would love to be able to use a distributed log like Kafka/Redpanda since it's HA out of the box, but it simply does not fit that use-case.
I could say the same thing about NSQ which is a distributed message queue with very simple semantics and a great HTTP API for message publishing and control actions. What it doesn't offer natively is HA though.
It is not straightforward, and it is complicated by a number of factors. The first would be bad "brand hygiene": If a company has dozens of legitimate domains across different TLDs, different providers and different geographical locations then it's already more complicated than just one canonical .com domain. If teams within the company are permitted to spin up their own domains (e.g. marketing campaigns, branch offices) then it gets 10x worse. Lastly if a legitimate brand frequently changes its appearance, it will be harder to pin down the true brand identity.
But even if you follow all of these best practices there are still powerful attack vectors. A threat actor could host their phishing page on an unrelated (compromised) domain with good domain reputation, in that case you wouldn't even know about that site until the first email or SMS hits your customers. Or the threat actor could use one of the many file-hosting or website services to create their site and host it on a shared third-party domain with perfect domain reputation (e.g. amazonaws.com).
And then there's incentive: It's no the companies that suffer financial losses, it is their customers. If you were talking about their employees being phished that would be a different story. Same thing for Google Safe Browsing: Their incentive is to protect against most of the obvious phishing, without any false positives, ever. If they are slow to detect something they won't suffer any losses. If they generate a False Positive their Chrome browser might suffer significant reputational damage if a popular legitimate domain is blocked.
Seconding this. Evading detection has become a real cake-walk since threat actors are able to sign up for a free Cloudflare account and then put their phishing site on their 2-hours old domain behind a level of protection backed by a $20B company. Funny that you almost never see phishing on Akamai ;)
Disclaimer: We operate in this space so we obviously have an interest in being able to detect these threats going forward.
Here's hoping they don't run great tools like Consul and Nomad into the ground somehow. If I'm ever forced to ditch Nomad and work with a pile of strung-together components like k8s I might just quit tech altogether.
Everything written in this article is true, but there are as usual more nuances to all of these. One of the primary reasons for me to go with a GmbH (and a holding) was the expectation of excess profits that I'd want to reinvest instead of drawing a salary. The other neat aspect of stacking a holding company on top of the operating company is that capital gains are not taxed in the event of a sale. That goes for investing into ETFs for example, but more importantly if the holding company ever sells the operating company then that sale is tax-free for the holding company. The ultimate owner is then able to pay out the proceeds and only be taxed using his personal capital gains tax rate (25%-ish).
To the people dismissing the idea of binarising vectors: Fair criticism, but consider the fact that you can also train a model with a loss function that approaches a binary behaviour, i.e. so that the magnitude per dimension plays an insignificant role and only the sign of the dimension carries information. In that case you can use the binary vector for search and ranking.
Cool idea, I can definitely see the appeal of having everything in one database. I would probably also add an "attempts" column (int) so you can discard messages after X attempts.
Thanks, that is great feedback and we'll try to improve how the scan visibility is shown and what it actually means. The suggestion of adding a text to the loading page is a great idea, and the feedback about the colors on the result page is totally valid.
I'm the last person who wants to see private data accidentally leak into the public domain. However experience has shown that combating the massive amounts of fraud and malicious activity on the web nowadays requires many eyes that are able to access that data and actually do something about it. That is the reason we have these public scans in the first place.
Thanks for your feedback. We show the Submit button on our front page as "Public Scan" to indicate that the scan results will be public. Once the scan has finished it will also contain the same colored banner that says "Public Scan". On each scan result page there is a "Report" button which will immediately de-list the scan result without any interaction from our side. If you have any ideas on how to make the experience more explicit I would be happy to hear it!
Scanning for malicious and phishing websites. These types of sites are just enjoying the ease of free services like Cloudflare to block automated analysis tools and tailor their phishing campaigns to very specific geographical locations and user groups.
We just use a combination of numerical limits (e.g. API calls per day) and product flags as an array of tags (features:["module1", "module2"]). These limits and flags are attached set on "plans" which can be attached to accounts. Plans can be combined, in which case we'll take the larger value for each numerical value and combine the tags using union. Additionally one can override / add to any of these values on a per-account basis, so if your customer needs PlanX but a custom API quota then you just override that single value directly on their account.
Call me old-school, but I don't get why something like this should be outsourced to a third party.
Ugh, when I saw the HN headline about this TLD I thought it belonged to ING Group, just like .barclays and .chase belong to their corporate owners. Just shows how suited this TLD is for phishing...
Regarding some of the comments: Yes, I had trouble sleeping with earplugs initially myself. It's definitely something you have to get used to, but once you do you don't notice them at all. Then it feels like having acquired a new super-power. I use Bilsom 303 type of disposable plugs, the type you'd find on a worksite, although I only change them after a few weeks of use.
Personal anecdote, but I sleep with earplugs most of the nights as I have a very light sleep. I would wake from really small noises multiple times every night. In contrast, sleeping with earplugs feels like entering a dark and quiet chamber and then suddenly emerging after 7-8 hours of uninterrupted sleep. YMMV, but for me it's a godsend.
Yes, the recently introduction of a stricter exit tax bit me too, before that I would have entertained the idea of moving across the border to Belgium or Netherlands (both literally less than 5km away). My tax accountant was of the opinion that the recently passed German exit tax will eventually be overturned by EU courts since it contradicts freedom of movement within the EU, but that will likely take years...
For what it's worth, the exit tax applies to all corporate ownership above 1%, foreign or domestic.
Serious counter-question: How do you run Postgres in a native and hands-off replicated failover setup? With MongoDB you create a three-node replica set and you're done. I've yet to see a simple guide for Postgres. But I might be wrong, so happy to hear how you would achieve the same with Postgres.
There are none unfortunately. I've found Vultr to be good value if you really need dedicated servers, OVH probably as well. However, a Hetzner VPS with dedicated CPUs in the US is still less expensive than the equivalent dedicated server at those providers.
Thank you for that comment, I don't think it's something many people really understood. The same is true for phishing websites. So much depends on the context and incomplete background information. Is a website that asks you to put in your username and password bad? Well, it depends on what the website does with that information in the background. I've seen very suspicious websites asking for user information which were, in the end, just sites set up by marketing departments of the larger company who were unaware of the dangerous precedent they were setting.
Just taking this opportunity to highlight again how stupid BSL licensing for HashiCorp Nomad is when they don't even offer their own cloud product for it...
Counterpoint: Providers offer k8s managed solutions because it's such a pain in the ass to run yourself. Nomad is far simpler to setup, operate and upgrade. And lastly the folks that are independent-minded enough to go with the less-popular option (Nomad) are also the folks more likely to host it themselves no matter what.