Why
CCP have been snuffing out some of the most passionate and engaged members of the EVE Community. In the last three years we’ve seen neglect evolve into unreliability, undocumented changes, year long outages, gaslighting and bans.
Third Party Tools have long been a driving force behind the success of CCP and EVE Online, members of our community working for free are a force multiplier on CCP development resources and have repeatedly resulted in some groundbreaking and unique tools unique to EVE.
CCP and Third Party Developers used to have a mutual goal of designing safe and effective tools, and It’s been my constant struggle to reignite that professional relationship for the benefit of all players.
I’m Ariel Rin, Third Party Developer, The current Maintainer of the Alliance Auth Project, and I’m running for CSM to bring ESI development back to a reliable, safe and game design approved state. In order to continue to push the envelope on community and social engagement in EVE.
I’ve spent the last two years as an EVE Partner with open arms attempting to bridge this gap with CCP, and while some amazing CCP devs have done their best, on the whole the experience has been heavily weighted against Third Party Developers with little to no interaction outside the Community Team. While i dont feel like my time as a partner was wasted, I think i’ve acheived all we can for Third Party Developers from this angle. More representation and a louder voice is needed, the CSM.
How
I am a realist, Getting CCP to allocate a developer to ESI again is a big ask, time and resources dont come cheap. But I see immense value in the passionate engaged Third Party Developer community as a force multiplier. If i can advocate for CCP to give us an inch to let us deliver a Mile, time after time we can make serious progress.
Advise on prioritising the 450+ untouched ESI/SSO tickets, this is likely intimidating to anyone coming afresh into the ESI role at CCP, but less than a dozen of them are severe pain points driving Third Party Developers and their Apps away from EVE.
Reinforce how the social engagement enabled by ESI is core to the longevity and passion of the EVE community. When ESI goes down and people lose access to Discord, Mumble, Teamspeak or Jabber, people are severed from EVE not just as players but as a community.
Push to re-open communication, the ESI team havent communicated a change or outage to us that wasnt reported by a popular app or discord becoming inaccessible, in almost three years. This really shouldn’t be rocket science and professional curtesy goes a long way. Most developers are chomping at the bit to help improve ESI, if there is something we can do to help, be it to reduce load on the server or move to another endpoint. Let us!
Remind CCP that every single ESI request should be tagged with our Email address, you dont need to ban us to discover who we are.
Work with the community and CCP Support to re-establish procedures around ESI reporting. A Support Ticket shouldn’t fall into a black hole because they send you to a dead Slack server (o7 the people that still use it), We have a Discord, We have Githubs, but after such a period of neglect these fall from the mind.
Continue to advocate against the narrative being pushed by factions of CCP that ESI is rogue, evil, unnapproved by game design, untrustwothy and bad for the game.
Push the Partner Program to fairly consider activity metrics for Developers as those for Streamers, Video Creators and other types of Partners.
To the great numbers of CCP Developers that do care and put yourselves on the line championing for us day in, day out. I hope this campaign reminds you that you aren’t alone and passionate Third Party Developers are still here and would love to work with you again.
My Vaguely Timeline-Esque Story
While I am primarily running on a Third Party Development platform, I’ve been around a while and developed connections and relationships in a wide variety of eve niche’s and mechanics.
- Currently the Lead Maintainer of the Alliance Auth project with a dozen developers contributing to a fully open source EVE Authentication and tooling platform
- Developer of AA Community Apps Market Manager, Relays, Alumni, Incursions, Drifters; contributor to Discord Bot, Corp Tools and more.
- Built EVEMeet, for organizing out of game events. This was shut down because of COVID
- EVE Partner for my current work on Alliance Auth and previously EVEMeet
- Nullbrain line Member in The Initiative [INIT.]
- Simple Farmers [FARMD] fanboy, taught me everything I know about gate camping and how to lose a super
- Rekking Crew super hunting
- Delve Dunks, a 10 person crew dropping dreadbombs in Delve trading 94 Dreads for 2.2T of 69 Supers (and more)
- IT Admin and helped run Tactical Supremacy [TIKLE] an AUTZ Alliance focused solely on AUTZ players and AUTZ content creation. Early pioneers of fozzie-sov warfare and citadel mechanics. A founding member of StainFraggin, later Legacy Coalition
- Highsec Incursions TLA#1 https://tlaincursions.com/, Level 4 Facwar missions, Level 5 Lowsec missions, C5 Magnetar’s in dreads, if you can make ISK I’ve tried it.
- Pandemic Legion (RIP), RKK before they tried to awox me and SNIGG after that
- Dustbunny <3 Dust 514
And before all of that, I rented in drone lands, from either Solar Fleet, XIX or whoever was “winning” at the time.
Git
For more information about the Alliance Auth project and the dedicated developer team
My projects
- Tactical Supremacy / aa-relays · GitLab
- Tactical Supremacy / AA Market Manager · GitLab
- Tactical Supremacy / aa-gdpr · GitLab
- Tactical Supremacy / AA Incursions · GitLab
- Tactical Supremacy / AA Drifters · GitLab
WIP/Betas
- Tactical Supremacy / aa-top · GitLab
- Tactical Supremacy / AA Bookmarks · GitLab
- Tactical Supremacy / AA Hunting · GitLab
Socials
Discord: arielrin
Twitter Github GitLab
AUTZ GMT+10