Databases
StackOverflow2013
Usersdbo
USBen
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USBen
    primarykey
    data
    text
    <p>Blog: <a href="http://www.adversary.org/wp/" rel="nofollow noreferrer">http://www.adversary.org/wp/</a> <br /> Code: <a href="https://github.com/adversary-org" rel="nofollow noreferrer">https://github.com/adversary-org</a> <br /> Codes of Conduct Policy: <a href="https://gitlab.com/Hasimir/project-participation-policy" rel="nofollow noreferrer">https://gitlab.com/Hasimir/project-participation-policy</a> <br /> <br /> OpenPGP/GPG key: 0x321E4E2373590E5D <br /> <br /> GPG Key locations: <br /> * <a href="http://www.adversary.org/ben-key.asc" rel="nofollow noreferrer">http://www.adversary.org/ben-key.asc</a> <br /> * <a href="http://pgp.mit.edu:11371/pks/lookup?op=get&amp;search=0x321E4E2373590E5D" rel="nofollow noreferrer">http://pgp.mit.edu:11371/pks/lookup?op=get&amp;search=0x321E4E2373590E5D</a> <br /> * <a href="http://pool.sks-keyservers.net:11371/pks/lookup?op=get&amp;search=0x321E4E2373590E5D" rel="nofollow noreferrer">http://pool.sks-keyservers.net:11371/pks/lookup?op=get&amp;search=0x321E4E2373590E5D</a> <br /> <br /> Please note that in regards to the code on GitHub, if you are one of those in the "delete what I think is offensive" from code or questions camp there is one repo there (not posted here) which you absolutely should NOT ever look at. You have been warned. If you go looking for it and get offended, tough. <br /> <br /> With regards to Codes of Conduct, either here, on any other StackExchange site, any other online community or interaction, or any in person interaction, the following will always be true:<br /> <br /> 1. My <a href="https://gitlab.com/Hasimir/project-participation-policy" rel="nofollow noreferrer">project participation policy</a> deals with these matters in greater detail and is always active.<br /> 2. The actual <a href="https://gitlab.com/Hasimir/project-participation-policy/blob/master/coc-policy.org" rel="nofollow noreferrer">policy document is here</a> and its <a href="https://gitlab.com/Hasimir/project-participation-policy/blob/master/coc-policy.org.asc" rel="nofollow noreferrer">OpenPGP signature is here</a>.<br /> 3. Any Codes of Conduct, or parts thereof, which are or may be utilised to provide cover for discrimination will be considered void and/or subject to my project participation policy.<br /> 4. Any Codes of Conduct, or parts thereof, which breach any of the UN OHCHR's human rights core instruments will be considered void and/or subject to my project participation policy.<br /> 5. Any Codes of Conduct, or parts thereof, which breach the <em>Sex Discrimination Act 1984</em> of the Commonwealth of Australia (i.e. where I am) will be considered void and/or subject to my project participation policy.<br /></p>
    plurals
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI think `import response` should be `import requests`, the "response =" line should be `response = requests.get` and the "bs" line should be `bs = BS(response.text)`. That said, it's far easier to make URL forwards with those services which provide an API (e.g. is.gd).
      singulars
      1. PO
      1. USBen
    2. COCorrect, the --import option can only import everything in the file specified, the --export option allows specifying any number of keys. This is because exporting is working from your keyring, either the default one or a specified one, and thus GPG is able to access the keys individually. Whereas importing is accessing a file which is not (yet) a part of your keyring. That said, if the key file is a .gpg file instead of a .asc file then it can be loaded as a keyring using the examples I gave previously.
      singulars
      1. PO
      1. USBen
    3. COYeah, I left it for much the same reason and I've removed the hat eating part because frankly it was just ridiculous (and I don't want to have to buy a hat :P). Especially after GregS pointed out we were each using different definitions of key size (see also: "size does matter, but it's not what we think it is" and "if a cryptographer says your key is a 'nice size' s/he thinks it's small").
      singulars
      1. PO
      1. USBen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload