Conversation

Notices

1. @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 01:27:28 UTC @mcscx@quitter.se

   • simsa01
   @simsa01 weird… Just created \!testprivgroup & posted quitter.se/notice/3357250 but this time w/lock closed.Hidden - unless you know the url
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 00:56:59 UTC @mcscx@quitter.se

     • MMN-o ✅⃠
     • simsa01
     @simsa01 I can see 2 posts to !privatevoices,so that group is not really private.But I don't see the posts on the group profile. #Bug? @mmn
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 01:01:08 UTC @mcscx@quitter.se

     in reply to

     • simsa01
     @simsa01 reminds me of the weird behaviour of just-created private groups we experienced when we did the testing for the faq
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 01:31:32 UTC @mcscx@quitter.se

     in reply to

     • simsa01
     @simsa01 … but a 2nd post to the private group without closed lock appears as public, just like in your test: quitter.se/notice/3357282
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 01:36:16 UTC @mcscx@quitter.se

     • simsa01
     @simsa01 sort of, yes - closing the lock when posting to a group seems to make it private to that group (unless you find out the url)
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 01:38:06 UTC @mcscx@quitter.se

     in reply to

     • simsa01
     @simsa01 but that will only work from the (classic) web ui, not from any other client, because there's no lock feature on any known client
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 09:11:01 UTC MMN-o ✅⃠

     • simsa01
     @simsa01 @mcscx Private groups, afaik, mean you need permission to join (i.e. be able to write to it so all members are pinged). Don't assume anything is private as in _hidden_ if it federates (yet at least).
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 09:12:36 UTC MMN-o ✅⃠

     • simsa01
     @simsa01 @mcscx A group post is just like any post on your timeline. It would require the classic view's "lock checkbox" to be checked in order to be private - and then it won't federate (yet).
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 12:19:18 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn yes, but another feature of private groups is: posts to that group are not visible to non-group members. Even without using the lock
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 12:21:40 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn private groups this worked well in the latest SN version. I use a non-public SN instance with a couple of people →
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 12:25:55 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn →and I often post private notices& bookmarks to a private group on that instance,so I'm sure I know how private groups work on SN1.1.1
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 13:42:10 UTC @mcscx@quitter.se

     • simsa01
     @simsa01 Rather bug than featurechange.I think this issue of #posts-to-private-groups-incorrectly-appearing-in-peoples-timeline can be fixed
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 14:34:38 UTC MMN-o ✅⃠

     in reply to
     ...available even for anonymous visitors as long as they know the URL? That definitely sounds like a bug :)
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 15:09:17 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn it does :)
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 15:13:56 UTC MMN-o ✅⃠

     in reply to

     • Qvitter
     @mcscx @simsa01 ...on a second look I think this is a lack of access restrictions in !qvitter
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 15:20:30 UTC MMN-o ✅⃠

     in reply to

     • MMN-o ✅⃠
     • quittermmn
     • gnusocial
     • Qvitter
     Yes, because if I log in as @quittermmn and enter Classic View, I am denied access. :)
     ...but this may be a !gnusocial #API bug rather than !qvitter - so that has to be checked first. I've got 30 minutes now to do so, I'll have a look.
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 15:30:30 UTC MMN-o ✅⃠

     in reply to

     • MMN-o ✅⃠
     • Hannes
     • gnusocial
     • Qvitter
     • snbug
     @mcscx @hannes2peer !gnusocial !qvitter This change at ~L77-80 should fix the notice being accessible despite access restriction: https://gitorious.org/social/mainline/commit/eff3256f5937204f883207781c50399e9b6fd9b2
     Dusty old !snbug ...
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 15:31:03 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn [I wonder what this dent "Yes, because if I log in as" is referring to. I miss #HierarchicalTree]
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 15:37:34 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     • Qvitter
     • testprivgroup
     @mmn my test dent http://qttr.at/jd8 to !testprivgroup is even visible at oracle.skilledtests,so it cant be a !qvitter issue
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 31-Jan-2015 16:07:29 UTC MMN-o ✅⃠

     in reply to
     I hope you'll poke me about this the coming days. Right now I have to get back to work stuff for the rest of the evening with only short internet pauses. :)
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 16:33:32 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn ok, I'll poke you :-)
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Saturday, 31-Jan-2015 22:19:39 UTC @mcscx@quitter.se

     in reply to

     • MMN-o ✅⃠
     @mmn thx :)