Posted by Plasma on Jan 25, 2012 10:10 am GMT + 10
"Just as we thought the hacking issue with Battlefield 3 couldn’t get any worse, it now appears it has just that: in order to prove their point against PunkBuster, the cheaters and hackers over at ArtificialAiming have banned over 150 Battlefield 3 players by using a PunkBuster exploit. A forum post claims:
Quote:
"In 2011 we hit them with a mass ban wave and now were are banning real players from battlelog while ggc-stream is totally unaware. We have framed 150+ bf3 players alone"
There are numerous threads over at Battlelog about this issue, where innocent players have been banned. The issue has to do with PBBans and GGC — third party services that run on the vast majority of Battlefield 3 game servers.
DICE have stated that they’re looking into the issue, but at this point, hackers have pretty much gotten control of the game. And just to make matters worse, innocent players can now be banned with what appears to be a simple command and the user’s BF3 GUID.
Posted by Plasma on Jan 24, 2012 11:13 am GMT + 10
BF3 PC Server R18 will roll out on Tue Jan 24th
A few RSPs will be trialling the server during this evening/morning. The new server update will begin rollout with all RSPs during Tuesday if no gotchas are found.
Changelog Fixed the most common server crash. The story behind this one is fairly convoluted:
When a player begins the process of joining a server, the server will begin buffering some kinds of information in anticipation of the player completing the loading & joining phase. However, players sometimes get stuck in the loading screen. This makes the server buffer more and more info for that player. A side effect of this is a temporary resource leak in the game server. The leak is immediately restored if the server changes map, or the player completes loading, or the player shuts down the game client. However if a player manages to remain stuck for 30+ minutes in loading on a server with lots of activity and the server doesn’t end the round, then the server could run out of the particular resource – it would then crash.
The new server version will forcibly disconnect clients which are threatening to exhaust that particular resource. With this change in place, we do not know of anything that would make high-ticket servers less stable than normal-ticket servers.
Long banlists will not crash the server.
The banlist supports up to 10.000 entries now.
The banList.list command has been modified ...
Tomorrow will mark one of the greatest political protest experiments in the history of the Internet. One of the most useful websites, Wikipedia, will go dark for 24 hours to protest the miserable and stifling SOPA/PIPA bills before Congress.
Most analysts will tell you that either of these two bills could kill the Internet as we know it. This is all done in the name of protecting American intellectual property. In fact, it is a smokescreen to protect the same old paranoid RIAA and MPAA contingents in Hollywood by using Congress to pass onerous laws that do more harm than good.
Note, yours truly is a massive content creator (I could lose some weight) and I am not seeing any protection from these bills. On the contrary.
But Wikipedia's protest and other blackouts will not solve anything. They are a total inconvenience to users who may want to use the service. What is accomplished? People will get mad at Wikipedia rather than mad at the specific Congressmen who promoted these bills.
The only effective measure to take—unless you love these laws—is to directly target the supporters and co-sponsors of the bills. How hard is that? Wikipedia would be better off removing the entries of these people or posting: "This Congressman is a threat to the Internet!" in big bold red letters across his entry and leave it there until he is voted out of office.
Doing so would be taking genuine political action rather than screwing the users as some form of protest.
Welcome, Anonymous
Membership:
Latest: 
Today: 0
Yesterday: 0
Waiting: 2
Overall: 1323
People Online:
Visitors: 47
Total: 47 (0) 
