smcgregor

5 ms·

1.
by smcgregor 2y ago
Data science is the practice of producing knowledge rather than building/coding. You can make systems that leverage that knowledge in an automated matter, but when you are deciding what to build, it is not a matter of coding. It is a m
2.
by smcgregor 3y ago
The CVE and consumer product incident databases are as close as it gets at present, but that may be changing soon... Much is happening. :)
3.
by smcgregor 3y ago
Please let us know if we missed the mark! https://incidentdatabase.ai/editors-guide/
4.
by smcgregor 3y ago
The line is not so clear as you are indicating. If I produce a system that makes 7 billion people feel slightly more depressed, then that system will in all probability contributed to a non-zero number of suicides. The unfortunate matter is
5.
by smcgregor 3y ago
You found it, more is coming in this regard in about 7 weeks. It is a data annotation task more than a systems one at this point.
6.
by smcgregor 3y ago
Collaborators are already working to provide data labels to all incidents that would support this particular filter. Many filters are available here: https://incidentdatabase.ai/apps/discover/?display=details&i
7.
by smcgregor 3y ago
Great point! We are constantly discussing the criteria. For example, if a robot lost power and fell on someone, do you think that is an incident? What if the robot was never turned on and fell on someone in shipping? When these challenges c
8.
by smcgregor 3y ago
Incident 73 dates back several years -- it is part of the initial Google spreadsheet from 2018. At the time, we had no formal definitions [0] or criteria [1] and only a vague idea of what we would find. My cursory re-read of 73 agrees with
9.
by smcgregor 3y ago
After many protracted discussions among editors, we decided not to threshold the severity of the harm. An allegation of harm is enough. Not all incidents are created equal when it comes to severity and the taxonomy feature helps sort throug
10.
by smcgregor 3y ago
Incident severity and scale varies wildly between incidents. We provide the taxonomy feature to support organizations like CSET adding color to incidents that support more descriptive stats.
11.
by smcgregor 3y ago
(I am from the org behind the Incident Database) I agree about it being a stretch, but we err towards indexing boundary cases. This one turns on whether you would consider the web application as being part of ChatGPT or not. In aviation, th
12.
by smcgregor 3y ago
I am one of the people behind the website and have been building AI "looms" for 13 years. We are working to make AI safer as our goal -- we are not working to smash the looms. Without the FAA and similar orgs/efforts, it is u
13.
by smcgregor 3y ago
(I am one of the people behind the website) We index everything that people believe is AI. Including GOFAI, for example: https://en.wikipedia.org/wiki/GOFAI We also index incidents related to people transferring decisi
14.
by smcgregor 10y ago
This [0] research paper sounds relevant to your "stegonographic social overlay network." [0] F. Beato, I. Ion, S. Capkun, M. Langheinrich, and B. P. (2013). For Some Eyes Only: Protecting Online Information Sharing. In ACM Confere
15.
by smcgregor 12y ago
I don't think CryptoCat has been distributed as a traditional web app for at least a year (probably more). The browser code is distributed as an extension, which does not have the properties you describe. edit for sub-comment: A tradit
16.
Seizing Privacy on Social Networks(priv.ly)
2 points by smcgregor 15y ago|0 comments