Conversation
Notices
-
@lohang that is why this new article by @barbijaputa is so good: For those who don't read Spanish, here's an automated English translation. I think it's the first good explanation of 'social network' and why Quitter.* is not the network but merely a node (by @barbijaputa on the @elbinario website): http://is.gd/YV5lEa !fediverse !newbies !novatos
- Claes Wallin (韋嘉誠) repeated this.
-
@erkanyilmaz either that, or we get a lot of repetition and redundancy because the dent itself will have to refer to its context.Neither is good.
-
@erkanyilmaz which reminds me: we still have that bug that makes it impossible to 'attach' a reply dent inside a hierarchical convo view: the reply box opens at the top and has no "in reply to" data any more...
-
@erkanyilmaz attempting to reply to this in hierarchical view... (1/2) http://oracle.skilledtests.com/attachment/57861
-
@erkanyilmaz ...leads this message box to appear at the top (2/2): http://oracle.skilledtests.com/attachment/57862
-
@erkanyilmaz and this is what you get when I use that reply box at the top as shown in http://oracle.skilledtests.com/notice/850674
-
@erkanyilmaz which oddly DOES at least appear in the thread now (huh?) - but you lose (visually) context because the reply box isn't in the thread (as you have in a timeline)
-
@simsa0 too bad - so we're still open to spam attacks from remote nodes - as we're now getting less-geeky average users more attractive to 'commercial interests', about time someone looked at that.
-
@simsa0 but it won't be forever... we'd better be prepared. Both Twitter and StatusNet were initially too late getting instruments to deal with spam which then took enormous effort to get under control. I really hope GNU social is going to repeat that! Now is the time to be ahead of the wave. #antispam
-
@simsa0 do you mean you get the reply box *inside* the thread, below the dent you're replying to? I'm not - using Chromium on Debian
-
@simsa0 well, there we disagree - we are in danger, just not overwhelmed yet. That's why now is the time to build the tools to be ready.
-
@erkanyilmaz do you mean you get the reply box *inside* the thread, below the dent you're replying to? I'm not - using Chromium on Debian
-
@mk oops, wrong number (identicurse)
-
ah, now I understood what the bug is about :-( actually, that's the same behaviour in !gs also
-
@mk well, you are not thrown to the top but to the bottom (can't really test in hierarchical since that is buggy in !gs)
-
@erkanyilmaz aaargh - the (web) UI for private messages is horrible! You cannot even *reply*. Good old Seesmic handled that a lot better.
-
@simsa0 identicurse problem - you reply by number but sometimes the number shifts as new dents come in while you're typing so teh reply goes to the wrong dent.
-
@simsa0 I can understand that one *should not* block ordinary people, not "not be able to" is a different matter because it enables harassment and spam attacks and normal people would just be sitting ducks. Saying one should not be able to block is like saying one should not be able to lock one's front door because no one should steal anyway.
-
@simsa0 luckily it happens only occasionally, but it's annoying
-
@mk don't forget we're in !sn there (not that's it better in the newer !gs ;-) )
-
@simsa0 hard to tell, I have no persoal experience with that, and never heard about it from other women I know/knew on social media. That's not to say it doesn't exist. But my attitude towards blocking is purely practical - if the option isn't there, sooner or later the service will be overwhelmed because there are always people who don't behave as they idealistically "should". Makek sure teh software has the option *before* it's needed, and learn from the experience of both Twitter and Laconica/Identica/StatusNet where they had to scramble to stem a flood when the tools didn't yet exist but the flood could be seen approaching.
-
@simsa0 another aspect is that blocking never worked (or worked well) in groups: even if a person could be blocked as an individual account their dents would still arrive via the groups they targeted - something soon exploited by savvy spammers. So the problem is not only there with federation, it's also local, in local groups. Countless possible counter measures have been proposed, but most of these ideas were never implemented - too much "should" in the heads of the developers. Identi\.ca was a spammers' paradise, starting with the welcome bot who immediately gave a spammer exposure to the search engines. The fediverse is just a mostly undiscovered spammers' paradise but as the population changes, it will become more attractive and they will come.
-
@lnxw48 yes, good point - ultimately it depends on site owners (and moderators, and group admins) to *use* the tools available. But group admins never got many tools though they were requested; what isn't there can't be used.
-
@simsa0 good to hear! I hope that will end up in GNU social then! :) @hannes2peer
-
@simsa0 and - interesting discussion. quite a bit of déja vu for me there ;-)
-
@simsa0 I figured ;-)
-
@simsa0 yes, what I said - it's a missing feature in federation. but, worse, even if you block a person, if that person is a member of a group you are also member of, you'll still receive whatever that person posts to the group. So even if the two are on the same instance, it's not necessarily unproblematic...
-
@simsa0 now combine the two: spammers (or otherwise nasty people) on their own instance, subscribed to a bunch of groups, can reach people who don't want to be reached without recourse. for now, at least.
-
@simsa0 of course, group admins can block group members. but then you have the problem again of whether the individual should decide/do or the admin? Peopel tend to expect that if they block a person, it will work as a filter and they will not see that person's dents anywhere. Public timeline can be explained, group content much harder...
-
@simsa0 and what if the group admin doesn't agree, and does not want to block the person from the group? or other group members don't agree? the victim is then powerless - and shouldn't be
-
@simsa0 sleep well, and have fun then with your little nephew!
Temporary Marjolein
Erkan Yılmaz
All Chirp! content and data are available under the