26

For a long(ish?) while now, the flair page has said:

What about the old, non image based flair?

The earlier methods of sharing flair are deprecated and will go away eventually. Please use the simpler image flair from this point onward!

Are there still serious plans to remove it? I can understand the desire to have a simpler, image-based flair scheme, but why require it? Is the old system a burden to maintain?

The old system gives me flexibility to not waste space on a generic gravatar image that I don't care about, allowing me to display everything in a nice, compact, horizontal row. For example:

Horizontal, gravatar-less flair example

Improve this question
10
  • 9
    I find it amusing that you had to post that nice, compact horizontal row as an image.
    – Pops
    Commented May 14, 2012 at 11:33
  • 1
    @PopularDemand: Oh, I was well aware of the irony when I posted it. ;)
    – jamesdlin
    Commented May 14, 2012 at 11:36
  • 3
    Can I assume from the lack of answers that there are no serious plans to remove it after all?
    – jamesdlin
    Commented May 21, 2012 at 7:19
  • We shall find out. Hopefully we get a reply from the SE team, eh?
    – Richard J. Ross III
    Commented Mar 17, 2013 at 6:13
  • @RichardJ.RossIII: I think it's already gone.
    – Manishearth
    Commented Mar 17, 2013 at 14:02
  • @Manishearth even still, it'd be nice to see an official response on this.
    – Richard J. Ross III
    Commented Mar 17, 2013 at 14:04
  • @Manishearth: The old non-image based flair still works.
    – jamesdlin
    Commented Mar 17, 2013 at 19:55
  • @jamesdlin: Have a link to one?
    – Manishearth
    Commented Mar 17, 2013 at 19:56
  • 5
    @Manishearth: taenarum.com/software/about.html
    – jamesdlin
    Commented Mar 17, 2013 at 19:57
  • @jamesdlin: Interesting, thanks
    – Manishearth
    Commented Mar 17, 2013 at 19:58

1 Answer 1

Reset to default
1

I think the description on the flair page is pretty clear: there's no development planned for this, it might break without warning and probably won't be fixed if doing so is more effort than removing it entirely.

As I understand it, the code to support this is fairly trivial right now, but that won't necessarily always be true and like all deprecated features you can continue to use it at your own risk.

If you're especially concerned about this, you could probably write your own version. Of course, that could break too if you rely on profile-scraping - might want to use the API...

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .