[Blacklist Feature?]

We use our blacklist carefully and selectively. We are aware it doesn't fully stop copybotting and we never state it is the perfect fix, but for what it does, it proves a point and does slow things down. This also applies with our group manager system that acts as a 'banlist' for groups, which is also not a perfect solution (and even with the one LL is implementing, it also holds the same issues and flaws), but it does help keep things more organized and reduces problems.

You seem to be inclining that we just fire off the blacklist/ban cannon like fireworks. We know the difference between honest individuals and problematic ones, and that is why we make use of such services to help keep our group chat without spam bots, greifers, and over whelming drama so that the honest individuals can further enjoy the services we provide ourselves. It's been working for us for over a year, and we do not intend to look back.

I've only just heard about the 'must be over 30 days old' from this forum and I agree it isn't practical at all. For our group, we thought about blocking accounts that were not 7 days old minimally but at the very least presenting the reasons why. We haven't pushed forward with it, but we also provide alternative ways of announcing things such as websites and the use of Twitter, which has worked almost flawlessly.

[Blacklist Feature?]

I was wondering if a blacklist feature is hidden away in the merchant home area or somewhere in the My Marketplace menu, since we have some individuals we prefer to blacklist ourselves given past experiences with copybotting and other issues where we'd rather not do business with the individuals.

We are looking towards the marketplace due to the API extensions for our vendor system (before the comment is made, we are not changing from our current vendor system. Period.), and while we don't expect interaction with our currently installed blacklist system (that's asking for too much), just having the option of adding/removing people much like how we add and remove access in regions and parcels is all we are looking for if this exists or is even being considered.

I know a JIRA was made roughly 2 years ago, but considering that JIRA is no longer in use and because some older JIRAs (namely the group ban list feature) have seemingly been given notice, we would like to expand to the marketplace but will have to reconsider if we cannot block certain users from our store.

[More than 1 voice instance on network causes failure?]

When I am on my network, I can log two clients on at the same time with voice active with two machines. At my friends' place, however only one person can use voice. If more than one instance is active on the network, it wil cause voice to cut out on everyone's end. When I am at my own place and they both have voice active, I can hear them perfectly fine and they report cut outs on their own ends (so I assume outgoing signals aren't the problem).

The routers we both have are the same, with the service providers being different. Is there any idea what is going on here?

[Changes to the jira.. hiding bug reports?]

Hmmm.... Interesting life cycle...

 

1. LL gets JIRA
2. Users use JIRA. Users are happy.
3. JIRA suddenly stops letting some users from using it. Some users are said.
4. LL updates JIRA
5. Said users can now properly use JIRA. Users are happy again.
6. Few days later, LL kills JIRA. Users get angry.

I understand that bug fixing and customer support is a task that is comparable to being a living sandpaper tester, but simply making JIRA essentially lose its purpose is as thoughtful as an expired, empty gift card.

As a system analyst, judging from comments on both defense and offence, the main thing I can see is the improper use of JIRA being a possible fault line. While some JIRAS serve their purpose, some (like campaigns for frivolous things) would give a bad image to the service. They should have analyzed the proper usage of JIRA and identify if there are tags that should be removed instead of simply changing the system all together. It'd be easier to migrate if they just disabled some tags and creating a more narrow scope for more serious manors than doing what they are doing now.

From what I can see, the path they are taking is just making work harder on their own ends and everyone else's. With just that in mind, they should revert OR introduce a GRACE PERIOD before said change comes into place. The sudden change to such a major system component is going to be the downfall that ends everything.

Remember, the users are your customers as much as they are your own living skin and muscle. We have been taught to take care of our bodies, and this action is like using a potato peeler as loofah.

-Flame

[Is ANS supported in Direct Delivery?]

Likewise here. If I dont' have ANS support, I cannot trust the marketplace's system enough to leave it be its own entity. It is nice to see that you are accomidating for the majority of users, but don't forget about the ones that really put money in your pocket.

That being said, even if the support for magic boxes are lost before this, I will not use DD until ANS support is added, even if it means removal of my products.

-Flame

[Issues with SL viewer 2.7.1]

I'm SOOO glad I'm not the only one! I tested this back when it was beta and it had the SAME problem! According to the logs, it's trying to load the directories as files!

2011-06-15T20:52:17Z WARNING: LLControlGroup::loadFromFile: Cannot find file C:\Users\Flame Soulis\AppData\Roaming\SecondLife\user_settings to load.2011-06-15T20:52:17Z INFO: LLAppViewer::loadSettingsFromDirectory: Cannot load C:\Users\Flame Soulis\AppData\Roaming\SecondLife\user_settings - No settings found.

 I reported this EXACT problem back in May! Way to go LL!

-Flame

PS - Is it me or are the people who are having this problem using 64 bit OSes and/or Windows 7?