In a nutshell:
Since June 9, 2025, Internet users located in Russia and connecting to web services protected by Cloudflare have been throttled by Russian Internet Service Providers (ISPs).
134 karma · joined August 7, 2013
In a nutshell:
Since June 9, 2025, Internet users located in Russia and connecting to web services protected by Cloudflare have been throttled by Russian Internet Service Providers (ISPs).
We did not pick them, and cancelled any other relashionship we had with them, in IR space by example.
So the break is already happening in this world...
Basically every vendor has its own formats, fields and the way to centralize this data (syslog still rules...) and parse it in a common way (a source IP is a source IP in all tech) has been a pain point since forever. There is basically a whole industry around it, and a whole bunch of logstash parsers have been scarificed. Even better is that vendors have a tendency to change format once in a while, so even some you have will break way more often then they should. Many vendors dont see that as an issue as it locks their clients in.
This is another attempt at solving this. It does seem to have traction for once, and nobody wants to piss off Amazon, if they make this a prerequesite to be on their marketplace then it will actually work.
I can confirm that we have no brown-outs. Also - We have a mix of very cold and warm weather, so are consuming lots of energy for heating in winter. - Hydro-Quebec, state-owned utility has a stellar record for maintenance, coverage and capacity management. It also send money back to the gov to support social programs. - Even with all that our electriciyy cost for consumers,,entre rpsies, and industrial is one of the lowest in the world.
https://www.cer-rec.gc.ca/en/data-analysis/energy-commoditie...
We built a few racks of Supermicro AMD servers (4 X computes in 2U), and we load tested it to 23kva peak usage (about 1/2 full with nthat type of nodes only, our DC would let us go further)
Were also over 1 PB of disks (unclear how much of this is redundancy), also in NVMe (15.36 TB x 24 in 2U is a lot of storage...)
Other then that not a bad concept, not sure of a premium they will charge or what will be comparable on price.
I can definitely confirm that the IBM statement is true. Execs signed on many projects, and we were always stuck with a blue pile of unusable garbage at the end. For twice the price orginally agreed to...
Working with RedHat as of today is still, well, working with RedHat. Highly competent people building things that will run well for a long time, and (so far) still at a reasonable cost. I do start to see some changes on pricing (high increases are on the horizon...), and more red tape around things that don't fit in the standard boxes. So i'm trying to decouple some areas from being fully dependant to more standardized/vendor agnostic models to keep options opened (mainly in container space).
I was a full-time consultant for a while but decided to go back being a full time employee due to a new baby in the house.
Quite good, almost as fast as my home connection.
I love it!
I am working in security , which is a small world where I am. I usually take a look at a LinkedIn profile to know who an applicant knows that I know as well, that way I can get more insight from people I know and trust if I feel the need. I had a few people call me as well to confirm a suspicion or get a bit of insight into someone's personality. Lots of people can sail an interview but are lacking in person. It saved me a few bad experiences i<m sure, and I know a few other people that hired anyway and regretted it later.
Hope that helps a little. Obviously it does not apply for international candidates or people new to the country/region, which is a profile we see often at the moment.
Also, I decided to change job a few years ago, getting LinkedIn alerts on jobs helped me target decent recruiters that really know the specific field, and it landed me 3 interviews and job offers.
Takes about 5 mins to kick in once an attack has started, which is very good.
It is very easy to setup a system in a corner (here, we'll install this piece of software, that will save us the 99$/month recurly subscription...) then forget about it until it is too late...
Some guidance would be very important, as well as mentioning ways to make it more secure, including tokenization, logging of CC numbers in server logs, knowing if the data transits through your server or not depending on provider, maybe even keep the software behind a a firewall without internet access, these can make a big difference in managing the risk.
As an open source project, you cannot be held responsible on what the people using the software is doing, but I think making sure that they understand that even if the software is free and easy to install and use, that additional work is required to make sure that the data is safe.
- How does this fit into the PCI picture, only thing I have seen on the site is a 2 line faq entry. Not enough to help on scoping or identifying requirements that would apply.
- How secure is it, and how are security notifications done? Keeping the software secure and up to date should be considered as critical. I would add a section on the site pertaining to security and addressing vulnerabilities. I did not see on the site information about security updates/patches. They might be on GitHub but it is way to deep to be useful to most people.
This kind of software is a perfect example of a high-value target for intrusion, I am a bit worried for the security of the information it contains, especially for smaller startups with limited resources, as well as zombie installations that can be forgotten in a corner with personal information or cards information inside.
Not saying it's a bad idea BTW, just a few concerns as a security analyst.
By my experience with Power7, the price/performance ratio is much lower on Power then Intel systems. Maybe it changed but i'm not holding my breath, even if IBM seems much more aggressive on pricing with P8 then they were with P5-P7. The
Quick calculation, absolutely unscientific:
Seeing that the price is 0.14$/hour for the 6-core xeon and 1.08$/hour on the 176 core P8, it would have to be roughly 8-10x faster to justify the cost difference, not sure it will be the case.
That aside, thanks for the book, I am buying it as I am sure that the advice will be relevant for the payment platform I will use (hesitating betweek Chargify and Recurly right now).
I could be biased by the industries I worked in (telecom, engineering, banking), there was a constant push to bring down opex spending, by squeezing suppliers on maintenance fees, reducing headcount and improving efficiency (especially in IT). The target is recurring costs.
In those businesses capex looks good in annual reports as they tend to show investment in infrastructure, security and business support tools and software (we invested X$ to improve our telecom infrastructure, call center or any other field of the business). It shows a willingness to stay current, ahead of competitors.
It just shows that knowing how your potential customer are structured is important. Especially for large enterprise customers. Your business model needs to follow those trends.
So for your product to be competitive, it needs to be very compelling to get over that hurdle, and be much superior to anything else. Being in `magic quadrant` in Gartner or other is also useful (yes I know, it does not mean much, but it looks good for management).
One common way of getting over that hurdle is to find a creative way for your service to move to the capex side of things. One example is selling an appliance which does not do much, and relies entirely on your service, sell it for a very high price, bundle a 3 year support contract that covers the cost of your service, and suddenly it's capex :-)
The opposite is true for dedicated, since they have to compete with us-based players, and OVH got in the East Coast market big time. Prices are lowering.
The number of different 3rd party libraries that are required, the type incompatibilities, matching fields, accounting for changes in the schema, and talking to legacy systems (I am sure there are many of them in there...), all in 5 months? Good luck.
Add to this the overhead of talking to IT and management of insurance companies, the IRS and others, and just the fact that it does answer some queries is fairly impressive in my book.
Also I am sure that most of those systems are failry deep inside the corporate networks of these insurers, just getting access to them probably was not an easy task.
That said the authentication layers failures and lack of testing are far from impressive.
It is truly a sad day and and it really shows the incredibly wrong state of affairs in Russia when comparisons to Hitler are actually justified. In this case the parallels with the situation an the state of affairs in pre-war Germany cannot be denied. It shows the same willingness to create two classes of citizen, and the withdrawal of the rights of that second-class.