hey folks, quick update to say you’ve probably noticed our new community icons.

these icons were lovingly crafted by @UrLogicFails@beehaw.org, who posted them a couple of days ago over in Creative. we took notice of them and obviously–because they’re our community icons now–really, really liked them.

thanks to his generosity in working things out with us, we’re pleased to announce we can use his icons under a Creative Commons license for the site! until further notice they’ll be our site icons, with credit to him on our sidebars. we’ll also be adding attribution to the community sidebars over the rest of day as time permits.

we’re also pleased to report that, thanks to your generosity, we’ve been able to reasonably compensate him for all 33 of the icons he’s made for the community! the agreed to rate is $5 per icon, for a total of $165 that’s been paid out to him as of today. this expense has been reflected on our Open Collective. (we’ve also agreed to, as possible, commission him for any future community icons until further notice, which will be subject to that same rate.)

hopefully you enjoy the new icons, and please thank UrLogicFails for the work here! thanks for using the site again folks!

  •  Librerian   ( @Librerian@beehaw.org ) 
    link
    fedilink
    English
    7
    edit-2
    1 year ago

    I agree to your points. Having every icon be the same colors (black and yellow) really makes it hard to distinguish the different communities at a glance. For instance, the Open Source Initiative keyhole logo/icon used as the logo for the Free and Open Source Software community is usually green, and having it be black on yellow background is actually in direct contradiction to the OSI Logo Usage Guidelines section 2.1 – “Never Stray from the Color Palette”, where an example of a yellow/red icon is present. So there are also such considerations that has to be taken. Also

    You may not remove or obfuscate either of the TM or ® symbols in the OSI Logo.

    So either way that icon has to be changed to be in compliance with the usage guidelines (@alyaza, @Gaywallet and @UrLogicFails ), since I believe the Beehaw-community does not want to infringe on such a point. I am also then not sure if @UrLogicFails can release the icon under a license as is done here, since the keyhole logo is trademarked (see the OSI Trademark Guidelines). See for instance how !opensource@lemmy.ml has solved this. They use the icon with the ® symbol as well as attributing the OSI in the sidebar:

    Community icon from opensource.org, but we are not affiliated with them.

    I think the color palette of the community icons shouldn’t be restricted to only black and yellow, that makes everything “scream” as that is usually a color combination used to express a warning or announcement. I’m no graphic designer by trade, but I think colors should be used as a distinguishing feature between the instances commmunities, and less dramatic colors, so to speak. Having the icons have a hexagon shape should be enough to recognize them as Beehaw-communities, even if they have different color schemes.

    • on this specific point (we’re tackling the other, will report back on that one later–the previous icon for that community was one i didn’t make so even if i wanted to i literally couldn’t speak on it like i can with most of our previous ones lol):

      I think the color palette of the community icons shouldn’t be restricted to only black and yellow, that makes everything “scream” as that is usually a color combination used to express a warning or announcement. I’m no graphic designer by trade, but I think colors should be used as a distinguishing feature between the instances commmunities, and less dramatic colors, so to speak. Having the icons have a hexagon shape should be enough to recognize them as Beehaw-communities, even if they have different color schemes.

      aesthetics are not really a big consideration for us in general, because we’re very much in function over form mode right now.

      but, when the subject needs to be broached, we want to do that right. in this case we have to account for a lot of things with aesthetics here, including but not limited to:

      • how our website is branded already and how to make it all mesh (bee theming has pretty specific associated colors);
      • how to make things work for all lemmy themes (there are several we have to make all the icons work with);
      • how to make them look good against each other (which is ultimately a consideration with no objective answers, so there’s no way to please everyone);
      • and how to make them as accessible and as unambiguous as possible for everybody within the constraints of those other points (which further limits the range of color choices we can work with; we also have to work with the accessibility limitations of the platform, which are numerous here to say the least.)

      all this to say: there’s really just not much wiggle room we have with the icons and their colors given those considerations, and there are other factors i’m no doubt failing to mention too. our previous icons were dichromatic black on white and very utilitarian/minimalist for a reason, and likewise these are pretty minimalist too.

      there’s also the consideration we’d now be asking someone to rip up all their work and basically start over, which we’re pretty hesitant to do–not only because we’ve already paid them, but because the simple reality is we can’t please everyone and i have no doubts we’d get similar critiques with more new icons and/or introduce new problems. at some point we just have to go with something and iterate on it, and as far as i’m concerned these kinds of critiques of the icons i can live with.

    •  alyaza [they/she]   ( @alyaza@beehaw.org ) OP
      link
      fedilink
      English
      6
      edit-2
      1 year ago

      So either way that icon has to be changed to be in compliance with the usage guidelines (@alyaza, @Gaywallet and @UrLogicFails ), since I believe the Beehaw-community does not want to infringe on such a point. I am also then not sure if @UrLogicFails can release the icon under a license as is done here, since the keyhole logo is trademarked (see the OSI Trademark Guidelines). See for instance how !opensource@lemmy.ml has solved this. They use the icon with the ® symbol as well as attributing the OSI in the sidebar:

      can now also speak on this point: we have an alternative in the works, ETA to its completion is tonight/tomorrow. given the short turnover we’re expecting here i think we’ll just leave the current icon in place for today–our backup and previous icon would infringe on the same principle in any case so it’s just trading one icon issue for another, lol.

    • And to add a little more: the icons contribute to making the Local timeline for Beehaw to become overly “busy”, since every post has a very stand-out yellow icon under it, usually signifying something important (hence why it should stand out). The icons become to prominent, especially considering the websites dark background color. I can see the appeal of being able to easily identify Beehaw-communities in Subscribed or All timelines, but to be quite honest, I find that the overly attention-seeking color choice of the icons clutter up the Local timeline to a point where they are more of a nuisance rather than conveying any kind of distinguishing information about the community. My Local timeline now looks like this:

      Image of the Local timeline for Beehaw to show how prominent the yellow icons are.

      Don’t get me wrong, I think they are beautifully designed, but the color choice is very much working against conveying any useful information at a glance (except what instance theyy belong to…). There is a reason that not all traffic signs have the same colors.

      • On the other hand, I think it’s really nice that they are distinctive from the logos on other instances. It tells you at a glance that you are clicking on a post from Beehaw.org and to abide by Beehaw’s mantra, whether you’re a user from another instance subscribed to a Beehaw community or a Beehaw user looking at your Subscribed feed.

      • We want to draw attention to the instance itself and that’s one of the only places we can do so in people’s feeds. I do a decent amount of graphic design and know far too much about visual theory (also a neurobiologist), I disagree that the color choice is wrong outside the scope of violating another licence.

    •  Gork   ( @Gork@beehaw.org ) 
      link
      fedilink
      English
      11 year ago

      You may not remove or obfuscate either of the TM or ® symbols in the OSI Logo.

      Ok completely unrelated. I always use the proper ™ or ® in whatever context it is required whether I’m writing for work or otherwise, even if I have absolutely no stake in the game at all, not working for any of the companies either. Because if I don’t then they can lose their trademark.

      For example. Suppose I am responding to a post about motor oils in a Reddit Beehaw post, and I mention a fully synthetic motor oil like Mobil 1™. I use their trademark, but I don’t use it, endorse it, nor work for Mobil™.

      Do I need to do this or is this just an obsessive compulsion of mine? Do other people do this? What’s the “right” level of mentioning trademarks without making it seem like I’m a corporate shill?

      • As far as I know, it’s not really true that those marks have to be included to protect a trademark. Definitely there’s no expectation that individuals should be using them in normal communications. Unless you actually work for the company and are told to include a mark on company branding, it’s really not something to ever worry about.