anonrerising

Do people not understand that not every TFA is phone based? There is no mention anywhere of phone numbers so far, and I doubt that'll be mandatory.

Seems like a odd thing to fuss about when all they asked is to make sure you have a valid email attached.

And personally, with the account being sold for a stimulus check, I think it's overdue to give us a little more security.

Seriously, it's designed to allow for multiple dragons. Shit like this, I ignore it all, and others do as well. Great work losing out on buyers.

...

There is a user that's actually indirectly admitting to multi accounting in there. "I'd rather not have 2fa if it means that logging in under my main account with my main email will result in suspension or banning" seems a very strange wording to use otherwise.

ngl id love to see if 2fa unintentionally weeds out TOS-breaking activity. im sure the roundsey bot accounts will drop in significance if the people running the bots need to manage 2fa.

I absolutely hate when sites ask me for a mobile number, because I don't have one (well I do, but for emergencies) because I simply cannot really justify the expense.

That said, I *really* doubt that FR wants to be responsible for a bunch of users' numbers. Nor would they want to drive away a portion of their userbase who either cannot use numbers in 2FA or do not WANT to use numbers in 2FA.

And yeah, it does sound like there has been an issue lately with accounts being sold/items being taken, but even if that weren't an issue already? More security (as long as it isn't 'jumping through hoops everytime you want to log in') is always good. Remember the saying 'locking the barn door after the horses have escaped'? That is how most sites handle their security, in my experience, and I would far prefer a site that is proactive in giving security before major issues start popping up.

Threads locked and Aequorin confirming it will be email-only, with no additional info (read: phones) requested, so there's that. The codes-by-email method still seems unnecessary and annoying - I'm still in the camp of if you want the extra security great, if you want to save your account-security mental effort for RL crap like bank accounts, that should be an option - but better than getting phones involved. Still hoping they don't do captchas though.

(Does anyone remember if there were security questions in FR's account signup process? I always used to just give nonsense answers to those, since they seem to make things less secure if you're honest, with the reasoning that they're only for password retrieval and I'm good with pw management, so I wouldn't need them. But lots of those old signups now ask the security questions about 'suspicious logins', aka new devices or whatever.)

where did xaz or aeq say they were using codes-by-email? all theyve said is that theyre using email for authentication. it could easily be an email with a straightforward login link.

the leaps in this DW and FR thread are unreal. why does the FR community always make assumptions and then get furiously mad at something that doesn't even exist yet.

Codes by email/links are basically the same thing all's said and done. And in all honesty, codes work easier with certain email services. My hope is a combo of clickable link with the code embedded and a code that could be entered.

Neither is worth the drama.

People, they are trying to protect you, and in all honesty, I'm betting there will be ways to help folks regain account access if someone needs help. They don't want to lock people out of their accounts. They want to make sure there's an account to return to.

Does anyone know if FR still has issues with outlook/hotmail? I'd assume not if they're deciding to roll this out, but. You know.

Shadow MG (finally) - Swirl/Marbled opacity changed - Flair manes (rip)

I actually can't tell the difference with swirl/marbled but man. not really a fan of new flair at all

ayrt

Like the other anon said, I don't see any practical difference between codes and links - I haven't encountered the latter much, but they're both the same in terms of hassle imo.

In more general terms, there invariably exists speculation, feedback on possibilities, and yes, complaints, because if you wait until after big changes/policies like this are implemented, it's pretty much too late. (Mind, I do understand that in all likelihood it's too late now - we wouldn't be being told to shore up our emails in the 'next few days' if the coding weren't almost ready to go on the site's end, and moreover the devs are going to do what they want whether people like it or not...which isn't unreasonable, because hey, their site.

But neither is there anything unreasonable about civilly expressing opinions/concerns about how all this may impact your use of FR. (And from what I saw, most if not all of those posts were from people who've had genuine problems with various types of 2fa on other sites, unless you think those are all just fairy stories being invented for scaremongering purposes.

The vein of '2fa isn't a big deal because I never have an issue with it' smugness, on the other hand, strikes me as a bit impolite towards those who have detailed exactly why there might be issues - whether due to disabilities, devices, mail providers, IPs, etc.

I may never have had issues with 2fa, other than a Uplay account getting hacked and adding it once, but I know it's a thing.

But FR needed to do something, and it's a damned if you do, damned if you don't area.

Also, that locked thread was not going to stay civil. It already was going into wierd speculation and bickering.

Filled in a square because Obelisk Flair was fixed and folks are NOT happy.

(i was expecting the glitch genes to be fixed, but eh, close enough; I myself am a little irked bc two of my G1 projects aren't as appealing now.)

oh no, i loved old flair on obelisks, it does looks less wow now

I'm more appalled by the fact staff did not say anything about the manes being bugged AT ALL. Coal flair was one of my favorite things on this website and now it's ruined because I had no fucking idea it was a bug. Good job staff!!!! 10/10 communication!!!!

Classic staff: https://i.imgur.com/blGP7QE.png

https://www1.flightrising.com/forums/frd/3088549/7#post_49889833

"
I'm sorry to those disappointed by the change.

I was working on copying over bugs from the locked gene post to the master post today, and grabbed some of the easier fixes to upload when I encountered them. So in a round-about way, the list being updated is why these fixes were being implemented.

The master gene error list is nearly finished and will be posted soon. It's something that we agree will be helpful in both communicating errors to players, as well as getting them queued up for fixes as staff.

Again, our apologies to those who enjoyed the bugged versions and apologies that those versions stayed up long enough to fall in love with. It's something we hope to negate with the posting of this list.

I think I will focus on just getting the list finished (it has taken longer than anticipated due to there being over a hundred pages to compile and check.) and not working on fixes simultaneously so we have the communication before the changes. "

:/ Thanks, Undel.

Someone said they went through and checked to see if anyone had reported flare/flair as a bug, and nobody did.

That, and the banner/showcase for flaunt/flare had the "bugged" Obelisks featured.

Really just feels like staff changing it for no reason at all, lol. I mean, if they were going for uniformity, they would've gotten rid of the sparkles on Obelisk manes too, right? I mean, Tundras, Imps, Skydancers and Pearlcatchers don't have that.

"That, and the banner/showcase for flaunt/flare had the "bugged" Obelisks featured."

THIS.

ALL OF THIS.

It is honestly insulting that Undel thinks people will believe this bullshit.

DA- Same, i was actually going to buy a g1 i've had my eye one for a few days now because of how well flair worked for her secondary as an obie (i loved what it did for baby obies manes) and now i have to settle for either...lord, i think either morph, noxtide, rosette or eel, if i want the same effect. None of which really match the primary i had picked out (leopard) that much. Bee works better tbh but i really wasn't planning on buying a gem gene. =/

i just really loved the accent colors flair had in their manes before. i'm so sad, ugh.

And yet:

Buttercup Stitched Snapper baby.
Latte Stained Gaoler male (adult).
Lead Koi Tundra baby.

They're still so broken that the genes actually BREAK THE IMAGE, but they're not fixed...

But they do a complete overhaul of Flair for an entire breed....

I got curious and did some digging and I ending up finding it it by looking in the last 5 pages of the old error tracker. We shouldn't need to dig though. Didn't they promise us an official list? I don't think this was widely known at all.

https://www1.flightrising.com/forums/bug/1012680/312#post_48849688
https://www1.flightrising.com/forums/bug/1012680/309#post_48652160

someone in the thread linked to dreamclaws' obe flaunt/flair reference guide, which has saved pics of each color for before/after comparison.

https://www1.flightrising.com/forums/gde/3072525/1

it's definitely jarring for some colors :/ i'm sure some of my own scries/projects are busted now. i do hope they revert the changes, and release a gene error list soon ;-;

The sad thing about this whole ordeal is that there are gene errors that have been around for over FIVE YEARS and they chose to "fix" flair obies. Just unbelievable.

Sadly, this is why I am now going to take a new stance:

New genes/breeds: Don't buy them for at least a year because staff doesn't communicate.

BINGO

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: Pyyro

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

Re: https://www1.flightrising.com/forums/frd/3088380/1

More Obe errors fixed

Re: https://www1.flightrising.com/forums/frd/3088380/1

The anon that replied before

no subject

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

no subject

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed

Re: More Obe errors fixed