love it!
Automation and Scripting - An investigation into further abuses of BGS and Powerplay
- Thread starter CMDR Tom D
- Start date
- Status
love it!
Captcha is not a solution to anything. It just makes things a problem for everyone else.
Why are so many people willing to accept captcha?! These days, it is completely unnecessary.
This one was better!
Captcha is not a solution to anything. It just makes things a problem for everyone else.
Why are so many people willing to accept captcha?! These days, it is completely unnecessary.
Most responses were against it (I would guess). Actually I like the idea. It must be fast and easy, but hard for bots, than it wouldn't bother me.
The intercepting mini game is more annoying because it takes so long.
The fact that the offending accounts identified by the Mahon group disappeared when FDEV took action, the focused attacks stopped, and remained out of the game for exactly 30 days doesn't raise any red flags with you?
WOW!
And I am now supposed to take anything you say seriously?
Sorry... I can't grant you credibility you don't have.
Last edited:
Captcha is not a solution to anything. It just makes things a problem for everyone else.
Why are so many people willing to accept captcha?! These days, it is completely unnecessary.
Pssssstt! It was a joke!
Last edited:
No Voice Attack just navigates menus.
It doesn't automatically select missions and trade.
It doesn't fly the ship from point a to point b
Edit: I've love it if Elite had Voice Control as part of the game itself, rather than having to use third party.
True, but a CMDR doesn't do it EVERY, SINGLE, TIME, they leave the station when running loop trade/pp
Agreed, hence why we have no idea why FDEV doesn't seem to be doing anything about it, or already have such a system in place to track anomalous player behaviour during or after the fact.
Not just powerplay the issue effects BGS and the Economy.
The bots are not just harming gameplay, they are plowing north of 30k pp merits to a single system weekly, meaning that us CMDR's have to do more work/play the game more to counter it. The bots can put in more play time hours than the CMDR's can.
Last edited:
i propose to receive a code by sms and a scan of my driving licence..
Pssssstt! It was a joke!
It has been mentioned several times in this thread as an actual solution...
Then person monitoring the bot accounts (for client/server crashes) just has to solve the captcha when the bot requests docking.
And space the bots traffic out a little so all the bots they are monitoring don't try to dock at once.
Solves nothing.
Last edited:
This response is a noticeable pattern of yours over the thread, using smoke and mirror terminology to exaggerate data accuracy or the connections needed to obtain the data/evidence. I'll only address this specific example as there's no need to turn it into a more personal matter.
EDDN re-transmits data sent to it so that other individuals can store or use that data as they choose. Tying into this process is as simple as connecting to the stream via TCP and decompressing each incoming message, resulting in one of the more easily human-readable data formats: JSON
Though it requires a small amount of technical knowledge, it does not require having implied connections to individuals in "high places".
• EDDN Documentation
Code:
EDDN provides a continuous stream of information from uploaders. To use this data you'll need to connect to the stream using ZeroMQ (a library is probably available for your language of choice).
Currently available relays:
• tcp://eddn.edcd.io:9500Which produces the following result (uploaderID redacted):
• Python Example
Code:
{'$schemaRef': 'https://eddn.edcd.io/schemas/journal/1', 'header': {'[COLOR=#00ff00]gatewayTimestamp[/COLOR]': '[COLOR=#99ffcc]2018-03-21T10:47:46.384153Z[/COLOR]',
'softwareName': 'E:D Market Connector [Windows]', 'softwareVersion': '3.0.1.0', '[COLOR=#ff0000]uploaderID[/COLOR]': '[COLOR=#ff6666]REDACTED[/COLOR]'},
'message': {'Factions': [{'Allegiance': 'PilotsFederation', 'FactionState': 'None', 'Government': 'Democracy', 'Influence': 0.0, 'Name': 'Pilots Federation Local Branch'}, {'Allegiance': 'Independent', 'FactionState': 'CivilWar', 'Government': 'Anarchy', 'Influence': 0.090457, 'Name': 'Ngaliba Blue Camorra', 'PendingStates': [{'State': 'Bust', 'Trend': 0}, {'State': 'CivilUnrest', 'Trend': 0}, {'State': 'Lockdown', 'Trend': 0}], 'RecoveringStates': [{'State': 'Boom', 'Trend': 0}]}, {'Allegiance': 'Independent', 'FactionState': 'None', 'Government': 'Corporate', 'Influence': 0.059642, 'Name': 'Apoyota & Co', 'PendingStates': [{'State': 'Boom', 'Trend': 0}, {'State': 'Bust', 'Trend': 0}]}, {'Allegiance': 'Federation', 'FactionState': 'War', 'Government': 'Corporate', 'Influence': 0.00994, 'Name': 'Mbukuravi Crimson Major Dev', 'PendingStates': [{'State': 'Boom', 'Trend': 1}, {'State': 'CivilUnrest', 'Trend': 0}, {'State': 'Lockdown', 'Trend': -1}, {'State': 'Famine', 'Trend': -1}]}, {'Allegiance': 'Federation', 'FactionState': 'War', 'Government': 'Confederacy', 'Influence': 0.00994, 'Name': 'Coalition of Ngaliba', 'PendingStates': [{'State': 'Boom', 'Trend': 1}, {'State': 'Bust', 'Trend': 0}]}, {'Allegiance': 'Federation', 'FactionState': 'None', 'Government': 'Democracy', 'Influence': 0.012922, 'Name': 'Progressive Party of L 639-45', 'PendingStates': [{'State': 'Boom', 'Trend': 1}, {'State': 'Bust', 'Trend': 0}, {'State': 'Lockdown', 'Trend': 0}, {'State': 'Famine', 'Trend': -1}]}, {'Allegiance': 'Independent', 'FactionState': 'None', 'Government': 'Corporate', 'Influence': 0.672962, 'Name': 'Ngaliba Network', 'PendingStates': [{'State': 'Boom', 'Trend': 1}, {'State': 'CivilUnrest', 'Trend': 0}, {'State': 'Lockdown', 'Trend': 0}, {'State': 'Famine', 'Trend': 0}]}, {'Allegiance': 'Independent', 'FactionState': 'CivilWar', 'Government': 'Feudal', 'Influence': 0.144135, 'Name': 'Lords of Ngaliba', 'RecoveringStates': [{'State': 'Boom', 'Trend': 0}]}], 'Population': 11987, 'StarPos': [-30.5, -8.625, 58.0625], 'StarSystem': 'Ngaliba', 'SystemAddress': 5068464072129, 'SystemAllegiance': 'Independent', 'SystemEconomy': '$economy_Refinery;', 'SystemFaction': 'Ngaliba Network', 'SystemGovernment': '$government_Corporate;', 'SystemSecondEconomy': '$economy_None;', 'SystemSecurity': '$SYSTEM_SECURITY_low;', 'event': 'FSDJump', 'timestamp': '2018-03-21T10:47:44Z'}}I appreciate what you are trying to do on behalf of the community but involving intellectual dishonesty will only weaken your assertions.
Last edited:
I am curious. If you have set as anonymous, you see an number ID but not the cmdr name isn t it ?
but can you something with the number as ID ?
Due to a recent change ALL data over EDDN has anonymous ID which is the same for a short period of time. It works the same as a "CMDR Name" you just don't know "exactly" whom it is.
https://ross.eddb.io/eddn/log/30988985 for example
See also my notes on this post https://forums.frontier.co.uk/showt...nd-Powerplay?p=6546118&viewfull=1#post6546118
Last edited:
This isn't screeps
Thats what would be preferred they have all the data.
thanks for answer. Very interesting. I knew about the raw data and uploader ID but i thought you found a way to link this id to an account...
Player in Open. We see them login to the game after a board flip.
AnonIDA and AnonIDB send a "location" to EDDN at about the same time.
Player in open flies out of the station and flies from, say Gateway to Chaxiraxi.
AnonIDA sends a "FSDJump" for Indaol
AnonIDB sends a "FSDJump" for Chaxiraxi
Us in open scans the highwake of the player leaving the station with a wake scanner.
The wake says it went to Chaxiraxi, good assumption taht the Wake For CMDR Bob to Chaxiraxi is AnonIDB.
For example.
("sends a" meaning "sends an event to EDDN", substitube player for bot/cmdr where relevant)
You are correct.
Until recently you could send your CMDR name as identification for the EDDN network unless you specifically chose to remain anonymous, but as of a few months ago only the hashed names are allowed - to combat name-tracking. However, with a bit of cunning you could figure out who owned which hashname by sitting at a station and watching people come and go, checking for submitted data around that timeframe.
Twelve days ago another change was pushed by EDDN so that the hash IDs for each uploader would changed every 12 hour, to combat the hash-tracking and making sure that even if you knew the hashname for a specific pilot... it would change in 12 hours anyway.
Or to simplify: It is no longer possible to track by pilot name. Reversing the new IDs to get the pilot name is not practical. Getting the ID by following a pilot and checking EDDB timestamps is not practical, since IDs change every 12 hours. You would have to follow the pilot nonstop to each location.
OMG! LOL!
- Status