README.txt 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. Initial simple way to Webfinger enable your domain -- needs PHP.
  2. ================================================================
  3. Step 1
  4. ======
  5. First, put the folders 'xrd' and 'dot-well-known' on your website, so
  6. they load at:
  7. http://yourname.com/xrd/
  8. and
  9. http://yourname.com/.well-known/
  10. (Remember the . at the beginning of this one)
  11. NOTE: If you're using https, make sure each instance of http:// for
  12. your own domain ("example.com") is replaced with https://
  13. Step 2
  14. ======
  15. Next, edit xrd/index.php and enter a secret in this line:
  16. $s = "";
  17. This can be anything you like...
  18. $s = "johnny5";
  19. or
  20. $s = "12345";
  21. It really doesn't matter too much.
  22. Step 3
  23. ======
  24. Edit the .well-known/host-meta file and replace all occurrences of
  25. "example.com" with your domain name.
  26. Step 4
  27. ======
  28. For each user on your site, and this might only be you...
  29. In the xrd directory, make a copy of the example@example.com.xml file
  30. so that it's called...
  31. yoursecretusername@domain.com.xml
  32. So, if your secret from step 2 is 'johnny5' and your name is 'ben' and
  33. your domain is 'titanictoycorp.biz', your file should be called
  34. johnny5ben@titanictoycorp.biz.xml
  35. Then edit the file, replacing "social.example.com" with your GNU
  36. social instance's base path, and change the user ID number (and
  37. nickname for the FOAF link) to that of your account on your social
  38. site. If you don't know your user ID number, you can see this on your
  39. GNU social profile page by looking at the destination URLs in the
  40. Feeds links.
  41. Finally
  42. =======
  43. Using this method, though fiddly, you can now be @user@domain without
  44. the need for any prefixes for subdomains, etc.