Search results

Jump to: navigation, search

Page title matches

Page text matches

  • ...erships, mod privileges and bans. Most of the edges are stored here, since edges can cross clusters.]] {{DBTable|reluser2}} stores related information in th
    1 KB (183 words) - 15:56, 22 July 2010
  • ...things such as community memberships, banning, etc will be implemented as Edges. But not yet.)
    7 KB (1,180 words) - 06:08, 7 March 2009
  • ...rrent 'maintainer') is the only person who can add/remove other maintainer edges at first; over time they can add others. (Adding another person with a "can Sample maintainership edges:
    2 KB (328 words) - 13:11, 1 August 2014
  • ; Edges: Data that makes <dwuser>foxfirefey</dwuser> very happy. See [[Data_Sources
    92 KB (14,343 words) - 18:34, 27 August 2018
  • # username.dreamwidth.org/data/edges DW::Routing->register_string( "/data/edges", \&edges_handler,
    8 KB (1,208 words) - 18:29, 23 March 2016
  • == [[Edges Data]] == http://exampleusername.dreamwidth.org/data/edges
    2 KB (286 words) - 18:52, 13 September 2009
  • ...an set their own FOAF files, or limit who they list. It's better to use [[Edges Data]] for data about relationships between users.
    539 B (81 words) - 21:21, 13 September 2009
  • ...the vertices and the train services operating between the stations are the edges. ...In this case, the table users holds the vertices while wt_edges holds the edges.
    6 KB (1,010 words) - 19:27, 12 August 2015
  • ...number of users that you like, validate them, randomly create watch/trust edges between them, and optionally have them all join an existing community. It's ...user2, and so on up to testuser100. Each of them will then be given random edges to each other, and will, if set up to do so, join the community you specifi
    6 KB (899 words) - 17:21, 5 March 2016

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)