Conversation

Notices

1. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 18-Feb-2017 14:07:00 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}

   • GNU Social
   • MMN-o ✅⃠
   • Markov Dosto(y)evsky
   • Shnoulle
   @shnoulle First, a @question for you: Are you trying to enable the use of @shnoulle without the "ostatus" subdomain?
   
   If you're not, then you should not need to do any of the socialify stuff. Maybe @mmn can correct me, but I believe he's rewritten some instructions there to clarify the fact that this process is unneeded for most !gnusocial instances. The software will simulate the existence of most of those files and directories on its own (sub)domain automatically.
   • Shnoulle (shnoulle@ostatus.shnoulle.net)'s status on Saturday, 18-Feb-2017 14:16:17 UTC Shnoulle

     in reply to

     • GNU Social
     • MMN-o ✅⃠
     • Markov Dosto(y)evsky
     • Shnoulle
     @lnxw48a1 @question @mmn Yes : @shnoulle follow up to @shnoulle follow up to https://ostatus.shnoulle.net/shnoulle . It's seems to work with #GnuSocial nightly ( see screenshot of my account on quitter.no  https://ostatus.shnoulle.net/attachment/233621). But another #GnuSocial user can not subscribe with master #GnuSocial :)
     
     About !gnusocial : totally right : i didn't put anything on .well-know directory (except acme for #lestencrypt), seems OK too. Just made a little fix for .well-know/webfinger/? to .well-know/webfinger? . The @question is about socialify another domain :)
   • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 18-Feb-2017 14:48:54 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}

     • GNU Social
     • Shnoulle
     @shnoulle The whole "socialify" process is very confusing. Let me read it a little more to see if I can understand it.
     
     If any !gnusocial admins have actually done this, please chime in.