|Anonymous | Login | Signup for a new account||2021-01-27 02:00 PST|
|Main | My View | View Issues | Change Log | Roadmap | Summary | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005896||opensim||[GRID] Grid Service||public||2012-02-20 02:37||2020-01-21 19:35|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Platform||Operating System||Operating System Version|
|Target Version||Fixed in Version|
|Summary||0005896: Abuse Report Configuration|
|Description||I Find that opensim does not yet have a supported structure for abuse reports. I think in many situations where someone is running a grid system there should be an option to configure an abuse report system that can be accessed by the viewer. Currently on the grid I participate in the abuse report system is done through the website, which can cause issues because a user might misspell a persons avatar name, or misspell the location name etc. And if the report subject is an object they might not be able to get the Object UUID or Owner/creator information depending on the type of object it is. This would make it hard for administration and moderators to pinpoint an abuse issue and resolve it. I have included some suggestions in the Steps to Reproduce section as to how the abuse framework might be structured(I dont know C# so i cant give programming suggestions but I can provide a simple layout of something an administration or moderator team might be looking for.)|
|Steps To Reproduce||1) A configuration file that will allow the individual(s) setting up the abuse report system for their grid to define categories from which a user can select for the abuse report.|
2) A part in the Robust.ini or OpenSim.ini(Robust would be better if possilbe) Where the grid owner(s) can define an email address to which abuse report notifications should be sent to.
3) A table in the core database to record the abuse report information(this would make it easier for a team to develop a web application that could be used to review abuse reports.)this should probably include:
b) reporter UUID/Name(maybe seperate tables for both?)
c) reportee uuid/name(maybe sperate tables for both?)
d) region name/uuid(same possibility for b and c)
e) Object UUID(For Removal via the console)
f) Region Coordinates of the issue(or of the object)
g) timestamp of report
j) body (Should be able to contain 255 for a textfield setting)
k) Status(maybe this should be configurable by the grid owner(s) that way they can define a default status like new, or a finished status like Resolved, Unresolvable, Banned etc)
l) UUID for uploaded snapshot
|Additional Information||Obviously that is just a simple database structure but it should suffice for the information needed. Unless anyone else has suggestions that is. OpenSim is a free service, and most grids are created as a free service, i think it is important that we have a system within this service that would help moderators and admins to keep track of abusive issues to protect the other users.|
|Tags||No tags attached.|
|Git Revision or version number||Not sure|
|Run Mode||Grid (1 Region per Sim)|
|Environment||.NET / Windows64|
Pixel Tomsen (manager)
opensim needs more stability and bug-fixes, your desired option, it will certainly be time later, when the simulation is increased.
I find the time this request as not important.
opensim is a free and public infrastructure, if someone has problems with someone, he can solve the currently already different.
it simply from waiting until opensim increasingly prominent, opensim will not be Linden Second Life.
Bo Iwu (reporter)
|I even wonder if there are no hard-coded links to LL abuse report service within viewers...|
Pixel Tomsen (manager)
@Bo I dont beleive so, using both Imprudence and Singularity when attempting to file abuse reports it returned an attempt to upload, and it looked like OpenSim actually tried to upload the report with no success.
@Pixel I agree that Opensim needs more stability and bug fixes, however even open-source chat programs and other tools have reporting features for issues such as harassment included in the frame work. It is the General understanding that any service offered as a free public service will have abusers of the service. While it may be the responsibility of the "Service Provider" IE grid owners to utilize these tools properly, the hooks and configuration should be implemented. So in this case whether or not OpenSim will be like Second Life or not is irrelevant. Also Providing a module or functionality for Grid owners to set up an abuse report system would increase the use of OpenSim, as many people may not use it due to the difficulty of being able to protect their users or users being angry because Grid Owners do not have those tools.
|Will Require Something To Save the Abuse Report to a File or DB, And Maybe be viewable in WIFI?|
paela argus (reporter)
subject closed, this party is written hard in the viewer and is not editable for opensim,
you have some way of doing abuse reports through inworld scripts etc without having to use this function that even secondlife is starting to deprecated more and more.
moreover i do not think the devs viewer is wanting to edit a wide range of code just for its ...
for me it has no interest to be added but you can add it yourself and edit your own viewer you are free to do!
Abuse Reports are triggered within the client by calling a Caps, which the server can supply.
So it's possible to have AbuseReports send to a database, file, whatever someone want to configure.
Ferd Frederix (reporter)
Now that firestorm is spun off for Opensim as a fork. So viewer features are not showstoppers any more.
I suggest we continue to discuss this. I would love to be able to get abuse reports collected centrally.
@Fred There is a working version of abuse report caps out there, it does not need viewer changes either. The reason this is low priority is because normally filing for abuse reports is simple, sending an email to the grid owner, which should be easily found either in imprint or in the terms of service, both a requirement for websites in most countries. Besides, it gives no guarantee those reports are read either, one can simply ignore them. If sh!t really hits the fan in terms of abuse or other violations those things need to go to a lawyer anyways.
It's not a bad idea to implement this at all, but it could give a false sense of security and may end up being useless entirely that way.
|@Paela This is not a Viewer Thing, but more of being the Devs|
Monamusa Kaliopov (reporter)
|I have to join Paela, there are enough other things that have higher priorities than the viewer to trigger an Abuse Report.|
|@Monamusa Kaliopov , What Other Things?|
+/- One hundred lines of code, 10 years ago ...
edited on: 2019-08-10 16:00
Very funny djphil, a little bit more than +/- 100 lines of code, maybe look at the whole thing ..
|The more I think about this the more I seem to end on the conclusion that adding this would result in users submitting reports that grid operators simply ignore, because you would need an interface to view the reports, which would mean a webroot somewhere to house the code to check the database entries or files. Those operators who can barely start OpenSim without something blowing up are never gonna check the db or look for the files. Ideally the Cap would refer users to contact the grid operator via mail or otherwise, though I am not sure the viewer is capable of giving that information without a bit of "hacking". It could be implemented, but really should remain something like an addon similar to search requiring someone actually set it up consciously.|
The owner can have a choice. He can activate or not activate in his ini file.
Enabled = true
but for this it would already be necessary that this silk implemented ...
|2012-02-20 02:37||LoralaiEnyo||New Issue|
|2012-02-20 12:12||Pixel Tomsen||Note Added: 0020905|
|2012-02-20 12:26||Bo Iwu||Note Added: 0020906|
|2012-02-20 12:27||Pixel Tomsen||Note Added: 0020907|
|2012-02-20 14:27||LoralaiEnyo||Note Added: 0020909|
|2019-04-24 10:59||CodyCooper||Note Added: 0035165|
|2019-04-24 10:59||CodyCooper||Status||new => acknowledged|
|2019-04-25 03:44||paela argus||Note Added: 0035168|
|2019-07-19 12:04||Fly-Man-||Note Added: 0035491|
|2019-07-20 21:16||Ferd Frederix||Note Added: 0035492|
|2019-07-25 16:10||tampa||Note Added: 0035507|
|2019-08-09 09:22||CodyCooper||Note Added: 0035559|
|2019-08-10 01:55||Monamusa Kaliopov||Note Added: 0035560|
|2019-08-10 14:13||CodyCooper||Note Added: 0035564|
|2019-08-10 15:11||djphil||Note Added: 0035565|
|2019-08-10 15:50||BillBlight||Note Added: 0035566|
|2019-08-10 15:51||BillBlight||Note Edited: 0035566||View Revisions|
|2019-08-10 16:00||BillBlight||Note Edited: 0035566||View Revisions|
|2019-08-10 21:30||tampa||Note Added: 0035567|
|2020-01-21 19:35||djphil||Note Added: 0036134|
|Copyright © 2000 - 2012 MantisBT Group|