| We hope you enjoy your visit. You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. Join our community! If you're already a member please log in to your account to access all of our features: |
| Solving moles and leaks | |
|---|---|
| Tweet Topic Started: Mar 17 2015, 11:51 PM (454 Views) | |
| minotaur1 | Mar 17 2015, 11:51 PM Post #1 |
|
Member
![]() ![]() ![]()
|
Hi there, I wasn't sure whether to post this here or in suggestions since I guess it's kinda both but I'll bend it into two parts so it fits here better. The board I run is based around trust, and information leaked can cause us problems when it happens. It's not really possible to filter down who it can be since the thread involved is typically viewed by around 20/30 members a day and it isn't possible for me to be online 24/7 to see who's viewing the thread at all times. I guess what I'm trying to ask is, is it at all possible to find out how many times a certain thread has been visited per day, by who, and if they've viewed it at different times, what times? Now I this second part is a request if the first part isn't possible, so if needed feel free to move this thread to the appropriate place (sorry for annoyance if so ).To make a section on the admin control panel which allows certain members to be monitored. To show when they log into the forums, topics they view, at what times, and duration. Cheers, Mino
|
![]() |
|
| Ben | Mar 18 2015, 10:16 AM Post #2 |
|
Quantum-locked when observed.
![]()
|
I don’t think it’s an exaggeration to say that all communities are based on trust. That’s the fundamental currency that allows a community to function cohesively. I understand the difficulties you have in isolating the source of leaks and trying to figure out which of your members are not living up to that expectation of trust. As you have surmised, there is no way at the moment to obtain the statistics you’re talking about. I can see the benefits in having access to some form of these statistics. Even in a more general sense, it would be nice to have analytics that provide a more nuanced picture of how members engage with a topic beyond views (which is a nebulous and ill-defined statistic that actually has little utility) or replies. Twitter recently rolled out its analytics dashboard to all users, even those of us who have no brand to promote, and I admit I’m fascinated and a little addicted to seeing how people engage (or, uh, don’t engage, in my case) with my tweets. It would be sweet if board admins could see, on average, how far down a topic people read before leaving or posting, or how many skip right to the last page, or how much time they spend “reading” a topic before moving to something else. The past few years have seen an explosion in this type of big data across the web; being able to collect and analyze that data is going to continue to be a big part of making the web a more responsive and adaptive environment. From the security standpoint you approach the issue, however, I’m not sure this would really help your problem. You said it yourself: this is an issue of trust; it is a fundamentally social problem. The statistics you’re asking about, even if narrowed to individual users, can’t in and of themselves identify untrustworthy behaviour. Is there a correlation between leaking information and viewing a sensitive topic for longer periods of time, or more frequently? Do moles go directly to the topics they are leaking when they log in, or do they nonchalantly browse the rest of the board first? Exactly how you can identify a mole from that behaviour escapes me. It’s also worthwhile to note that leaks are often unintentional and a result of loose lips or enthusiasm. I’m sure this is something you’ve already done, but it might be time to do it again: talk with your staff about what constitutes a leak, what they are authorized to share, and when they are authorized to share it. Make it clear why leaking information before it is ready to be released can be harmful. This won’t stop leaking with malicious intent, of course, but it could go a long way to reducing accidental leaks (and if your staff are of the trust and the calibre you’d expect, those are always going to be the most common and most frustrating types of leaks!). The use case for collecting and exposing more statistics to admins is definitely there. However, I think it extends far beyond the motivation of wanting to protect information security and integrity, instead tapping into the very basis by which we explore, share, and curate information on message boards and across the web in general. This is the type of feature request I can get behind, because it speaks to something I see as part of the core of ZetaBoards—giving people the tools they need to help create great communities. I would just be wary of thinking it will provide much usefulness as a security measure. |
![]() |
|
| 1 user reading this topic (1 Guest and 0 Anonymous) | |
| « Previous Topic · Service Discussion and Feedback · Next Topic » |
| Track Topic · E-mail Topic |
10:55 AM Jul 11
|



![]](http://b1.ifrm.com/0/1/0/p601690/pipright.png)
).




10:55 AM Jul 11