Minecraft Association not working.

[Eto]

user menu > minecraft assocation.
clearly doesn't come up w/ the tab anymore. Have heard this problem is occuring w/ other users aswell, please look into this. https://gyazo.com/e161d2b26299e75b1ebe4cac30e7e65e?token=5f82d20dd07922d13e5e9de3bed771d4

 

[1980]

same for me

 

[DEKU]

Same

 

[ZACK]

Same

 

[iNg]

ya trying to sell my 2013 account but can't link it D:

 

[Ajdin]

McAssoc is open source. You could technically host your own version of it on your own server: https://github.com/lukegb/mcassoc - it was on my todo list to not be depending on luke's private portfolio site since it probably has no failovers and isn't the safest thing to rely on for a important function of a site with 70k members.

The thing is made in .go which is an awful thing to work with. I already had a test version setup after a lot of fiddling and modification of the xenforo addon.

Another thing to look out for is migrating all members to your self hosted version. All McAssoc passwords will be invalid and everyone will most likely have to relink their account to ensure that everything is safe. Complicated? Yes, but definitely worth it. Depending on something else when you don't have to seems like a waste of reliability.

 

[Ajdin]

Mick MCAssoc is once again down.

 

[buildblox]

McAssoc is open source. You could technically host your own version of it on your own server: https://github.com/lukegb/mcassoc - it was on my todo list to not be depending on luke's private portfolio site since it probably has no failovers and isn't the safest thing to rely on for a important function of a site with 70k members.

The thing is made in .go which is an awful thing to work with. I already had a test version setup after a lot of fiddling and modification of the xenforo addon.

Another thing to look out for is migrating all members to your self hosted version. All McAssoc passwords will be invalid and everyone will most likely have to relink their account to ensure that everything is safe. Complicated? Yes, but definitely worth it. Depending on something else when you don't have to seems like a waste of reliability.

Did you manage to successfully implement it locally? I contacted Luke over IRC asking about it as there is no documentation whatsoever, but he doesn't appear to be active nor willing to continue development on the project.

 

[FisherGee]

yep same, the association is glitched or something, try to sell an account :I

 

[Ivain]

Considering the amount of developers on here, I'm sure one or more of them could find a way to rewrite the program in another language than .go (whatever scripting language that is), and then Lyphiard could read over it and whittle out the weaknesses.
Or, since it is a nightmare to read other people's code if they haven't written it to be readable by others, lyhpiard could do the same thing. I understand it might suck to have to divert him from whatever project he's currently working on, but making a functional and independent version of this system is essential.
I'm known as someone who seriously dislikes the account business, and honestly I wished it wasn't a thing, but right now it's still a very big part of the site's micro-economy, and losing people due to a third-party site being fucked could become a real problem in the long term.

 

[Shroomy]

same :/

 

[Ajdin]

Did you manage to successfully implement it locally? I contacted Luke over IRC asking about it as there is no documentation whatsoever, but he doesn't appear to be active nor willing to continue development on the project.

Yes. I got it working on our own server with the help of my developer at the time.

I also understand that there's no documentation. Why would there be detailed documentation? So everyone can setup their own copies of it?

 

[buildblox]

Yes. I got it working on our own server with the help of my developer at the time.

I also understand that there's no documentation. Why would there be detailed documentation? So everyone can setup their own copies of it?

I just find it tacky that a developer wouldn't give even rough directions to make the code locally accessible when the code is already open source and it's clear he's basically abandoned the project. It's just generally a good development practice to make it attainable.

EDIT: Scrap that, managed to get ahold of him. It's actually not as hard as I thought to set it up, I'm just concerned about the feasibility of implementing something like this.

Also, Eto, this should be fixed. Check again if you can't link your account.

 

[Ajdin]

I just find it tacky that a developer wouldn't give even rough directions to make the code locally accessible when the code is already open source and it's clear he's basically abandoned the project. It's just generally a good development practice to make it attainable.

EDIT: Scrap that, managed to get ahold of him. It's actually not as hard as I thought to set it up, I'm just concerned about the feasibility of implementing something like this.

Also, Eto, this should be fixed. Check again if you can't link your account.

The developer isn't inactive: https://github.com/lukegb/mcassoc/issues?q=is:issue+is:closed

Implementing it truly isn't hard so I'm not sure why you're concerned however I'd even consider getting a custom system done which uses the same method of verification (if budget allows).

 

[buildblox]

The developer isn't inactive: https://github.com/lukegb/mcassoc/issues?q=is:issue+is:closed

Implementing it truly isn't hard so I'm not sure why you're concerned however I'd even consider getting a custom system done which uses the same method of verification (if budget allows).

I was more referring to the lack of updates pushed through, though yes, it appears he is more active than I thought.

Considering it'd most probably require lol768 to edit a few lines to call to the local server instead of Luke's, I doubt it'd be a considerably expensive commission; the only problem I'm worried about is (as you mentioned) the fact that existing associated accounts won't be migrated over. So it's probably not extremely feasible to switch to a local server so far into the game.

 

[Ajdin]

I was more referring to the lack of updates pushed through, though yes, it appears he is more active than I thought.

Considering it'd most probably require lol768 to edit a few lines to call to the local server instead of Luke's, I doubt it'd be a considerably expensive commission; the only problem I'm worried about is (as you mentioned) the fact that existing associated accounts won't be migrated over. So it's probably not extremely feasible to switch to a local server so far into the game.

The current state of the addon should work just fine with a switch to a new server. The only thing that wouldn't work is the passwords. That's not a big deal. The system would just ask them to setup new ones.

Also, you don't need to commission anyone for this. It's literally editing URL's in 2-3 lines of code.

 

[buildblox]

The current state of the addon should work just fine with a switch to a new server. The only thing that wouldn't work is the passwords. That's not a big deal. The system would just ask them to setup new ones.

Also, you don't need to commission anyone for this. It's literally editing URL's in 2-3 lines of code.

It probably is a few lines, I haven't personally checked.

And are you sure that the switch from Luke's server to a local environment would be that seamless? I thought all associator data was stored on his server.

 

[Ajdin]

It probably is a few lines, I haven't personally checked.

And are you sure that the switch from Luke's server to a local environment would be that seamless? I thought all associator data was stored on his server.

All that the MCAssoc(server) does is give the user for a skin to upload to Minecraft.net. Once it's uploaded and set, MCAssoc verifies if the user has changed his skin and passes it on to MCM when MCM requests that data.

It has a username and password system for the sole purpose that if you want to use a single Minecraft account on multiple sites, you can do that without having to re-verify for each site individually.

The MCM database itself has all records of the verified accounts. The new self hosted version would technically only be overwriting that data. And if there's 1 Minecraft account on 2 different MCM accounts, It'll remove the Minecraft account from the oldest MCM linked account. All this data is stored on MCM, MCAssoc just tells MCM if the verification was done successfully.