[1] www.nubrella.com
683 karma · joined May 7, 2016
[1] www.nubrella.com
Anyone familiar with the product know, what the annual fee is for, when the customer seems to be charged the delivery fee too, per delivery?
I have seen many security bugs reported by Tavis show up here on HN. I haven't seen Tavis behave poorly in either explaining these issues or reviewing the fixes. On the contrary, his comments in the issue discussions have almost always given a benefit of doubt to the product and its developers when it comes to the way they have handled the security issues.
Gitlab.com is a repository hosting product i.e. it's in data storage business. Of course there are other important aspects to the product, like the web interface and such, but they are primarily into data storage. They literally lost data of their users [1] (some of them might have been paid customers too), not because someone accidentally deleted the data (which happens and is understandable), but because they did not have the basic things, that you expect of data storage products, functional or tested.
They have been offering gitlab.com as a SaaS product, since 5 years [2] and yet the very basic thing, like backups, wasn't tested or functional. If that's what increases the faith in a data storage company, then I don't know what to make of it.
[1] https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...
...and that's the point I was making in my comment
That doesn't sound logical to me. The chances of such incidents happening isn't related to how they announce that incident.
Like I said in another post a while back, it's fine being transparent but gitlab just have taken this to an extreme. It's important to be private about certain details and just get real work done and be known for that.
Instead this is about gitlab's definition or rather level of transparency and something they seem to be proud of and are even being appreciated very often here at HN. I feel that gitlab have taken the transparency thing to an extreme, to the extent that they even named the engineer that caused a recent downtime. I don't think it matters that the engineer didnt object to it. Then there are posts about why they are choosing some UI framework and why they are moving away from cloud and now this. It's fine to be transparent but in a professional world it's also important to be private about certain things. Trying to please people by being transparent for the sake of it will take a toll on the team eventually. It's much more effective to just get things done instead of constantly being transparent to the external crowd, about every single detail
Wouldn't your team now even have to decide how to deal with this even after some specific well known caches have been cleared? I mean there's no guarantee that someone may not have collected all this data and use it to target those cloudflare customer sites. Are you planning to ask all your customers to reset all their access credentials and other secrets?
[1] https://www.lix.polytechnique.fr/~liberti/public/computing/p...
If you are using the same attitude as you use in this comment, with their team, i'm pretty sure they will be thrilled to keep aside all their regular work and help you out cleaning up a enormous mess created by a bug in your service.
Furthermore, I won't be surprised if they have seen more concentrated spam attack, after the news of this data loss surfaced.
Is this for real? That article also claims around $1000 per hour earning with these ads. I had google ads on my blog for years and hardly made anything of note in terms of earning. I understand this is different type of site attracting a different audience, but even then I find it hard to believe people would have clicked those ads (let alone bought anything) to earn him that much.
Is this rate of earning common for sites like these?
Agree with you on that part. However, this specific article wasn't aggressive at all.
content = 'a'
with open('content.txt', 'w') as f:
for x in range(1, 18888789):
f.write(content)
It took me 39 seconds (consistently) to open it. The generated file size is less than 20MB.The problem appears to be that ST3 slows down while loading this file which just has 1 huge line. If I tweak that script to change the content from 'a' to 'a\n' to include a new line within the content, the generated file loads relatively quickly and in reasonable time (around 6 seconds for the 37MB odd file).
I admit, this now I think can be considered a corner case but when I ran into this pretty frequently, I just assumed this happens with all files with such sizes. As for why I believed ST2 doesn't have this issue - I'm not sure anymore, because when I try these files now with ST2 it too behaves similarly.
I no longer work on that project which generated these files so had it no been for this thread, I would never have bothered to dig deeper into this and would have just stuck with ST2 :)