121–130 of 369 posts
Earlier quoted context omitted.
Its good for privacy if you don't live in Russia... I don't think that they share the data with US governments?
I tend to think that it's not the govs tracking us that we should care about but the big tech. Yandex is one of them.
They use p0f for TCP fingerprinting in their nginx config :) Edit: Cool spam factors in extsearch/robot/index/metadoc/lib/links/spam_factors.h: SF_WEB_HOST_RANK = 0, SF_GREEN_TRAFFIC_SHARE_NORMALIZED = 1, SF_ADULTNESS_BETA = 2, SF_NOT_FOUND_RANKS = 3, SF_RANK_DOOR_TUMBLR = 4, SF_NASTY_CONTENT = 5, SF_LANGUAGE = 6, SF_IS_SHOP = 7, SF_WEB_HOST_SIZE = 8, SF_RANK_HACKED_NOVA_PHP = 9, SF_IS_FOREIGN_HOST = 10, SF_PESS_LEVE…
I wonder what SF_FROM_SEARCH_SHARE_YA_BRO is. "Share, ya bro!"
That's huge. What takes up most of that 40Gb+?
2. Git repos tend to get rather large over time and yandex has been around since before git.
Interesting that most of the code comments are in English.
Has anyone found the FSB back-door portal?
Earlier quoted context omitted.
I think the problem is people are entering a matured industry, all they know is the professional buttoned up culture we have today. People have no further curiosity beyond working and making money in tech. They do not have memories of a time when people tinkered around doing all kinds of crazy and possibly illegal stuff, just for fun, just to see if the could. Sad really.
Tinkering is fine. Even leaking and study is fine. But re-licensing someone's else code is at the very least impolite. People avoid using BSD-licensed code in GPL code base, or vice versa, just to not violate an open-source license of some fellow hacker who won't sue (but would yawp on Twitter, or something). Also, cutting proprietary stuff out of the thick scaffolding of proprietary dependencies is often hard. Remov…
Huh? I don't believe they do that. It's completely fine to use BSD in GPL code, but not the other way around.
They use p0f for TCP fingerprinting in their nginx config :) Edit: Cool spam factors in extsearch/robot/index/metadoc/lib/links/spam_factors.h: SF_WEB_HOST_RANK = 0, SF_GREEN_TRAFFIC_SHARE_NORMALIZED = 1, SF_ADULTNESS_BETA = 2, SF_NOT_FOUND_RANKS = 3, SF_RANK_DOOR_TUMBLR = 4, SF_NASTY_CONTENT = 5, SF_LANGUAGE = 6, SF_IS_SHOP = 7, SF_WEB_HOST_SIZE = 8, SF_RANK_HACKED_NOVA_PHP = 9, SF_IS_FOREIGN_HOST = 10, SF_PESS_LEVE…
SF_AVG_TITLE_CAPITAL_LETTERS_RATIO and SF_HOST_CLIPART_IMAGE_COUNT are pretty funny. I wonder what SF_FROM_SEARCH_SHARE_YA_BRO is. "Share, ya bro!"
Earlier quoted context omitted.
I wonder if that's a function of their technology or their database. Google's image search used to be good, but regulations have forced them to cripple it in some ways, and they might have chosen not to surface results in some contexts.
I never realized that reverse image search was so bad because of regulations. Can you give me some more context about which regulations affect google reverse image search and why?