indec

5 ms·

1. 1.▲
   Advice to future software engineers(indecorous.com)

   2 points by indec 14y ago|1 comments
2. 2.▲
   Happy Notices(indecorous.com)

   1 points by indec 14y ago|0 comments
3. 3.▲
   by indec 15y ago

   My opinion is that "female-friendly fields" is (or should be) "software engineering". Thus "lets see them set up a special fund or something for female-friendly fields" reduces to the current state of the program.
4. 4.▲
   by indec 15y ago

   Well, generally following the redirects is actually somewhat redundant. The idea of GSB is that URLs that lead to bad things would all be identified and added to the database. Customising attacks for a given site specifically adds complexit
5. 5.▲
   by indec 15y ago

   We follow them on the server side and check the final URL we get to against the GSB database. We don't modify the user-generated content.
6. 6.▲
   by indec 15y ago

   We "unroll" redirects as much as possible so that we can check the URL at the end.
7. 7.▲
   by indec 15y ago

   The privacy risk for GSB in general is that you are sharing URLs with a (trusted) third party. That's most acute with the REST API, but most implementations (including gsb4ugc) cache a local copy of the lookup tables and so don't actually s
8. 8.▲
   by indec 15y ago

   Is there a good way to deal with the case of sigma = 0 (i.e. all posts have the same number of votes)?
9. 9.▲
   by indec 15y ago

   Was there particular value in the YC Y U NO coverage? Seems like coverage for coverage's sake. Networking value, perhaps?