for me no preference either way, all look good.
nice work!
p.s. is there any plan to fix the maidsafe triangle in a similar way?
1 Like
If you can describe what is wrong with it and MAIDSAFE is happy for me to do so
@neo, itās described in an earlier post within this thread. Here is the post:
Same issue basically, things just donāt line up. You will see it immediately when you zoom in.
1 Like
try this for size
Its now the one pattern repeated and rotated to get the 3 sections
5 Likes
If you give it to the webservice of SVG Optimizer, it getās returned again as three pathās and depending on your settings, using less bytes, 808 => 451
But ā¦ Looking at the one at the moment still in Assets, it may be that the artifact was intentional? I.e. to highlight the edges. Reasoning: other planes join OK.
Do we know who created the triangle? Should consult him or her. Because otherwise it maybe would look like ING Bank and Microsoft open sourcing Rembrandt:
1 Like
nice job @neo. No matter how much i zoom in, iām not able to see even the smallest irregularities!
please, letās have that one replace the current version
2 Likes
I doubt that based on the fact that the āartifactā is not present on all three sections. When going through it the artifact was because of rounding to one decimal place
45 are formatting spaces
Some spaces in the 3 paths that are unnecessary
And they converted some of the path like a lineto position into a vertical - this save one number. And done a couple of times in one path, so 6 numbers saved. And a couple more like this.
I wanted to keep the points as all linetos and curves rather than use the shorthand verticals. Basically because there were maths/rounding errors before and this way its easier to see where the points are
Is it an issue?
2 Likes
āArtisticallyā those two highlighted edges could be seen as being in the right place, accentuating the element in front. Never mind, itās just that tiny bit of concern for the work of someone else. Who has done the design, does one know?
Of course not, just curiosity made me try it and I thought maybe point you there too - if you didnāt know about it already that isā¦
2 Likes
It also exactly matches the error/artifact that is introduced because only one decimal place is used in the points. When drawing lines at 30/60 degrees you need more than one decimal place (when max is 100) to prevent such occurrences.
Often the simplest explanation is the correct one. The reason why 2 sections display some gaps and not 3 is that the rounding goes the other way on the 3rd.
When viewed at normal size the artifact is unnoticeable and does not contribute to the artistic nature
Those 2 facts lead me to have a high confidence that it was not intentional and just an error.
Having said my opinion I would welcome the original designer being asked their intentions. It would be good to confirm or dismiss the idea of it being intentional. Of course the designer could say yes in order to cover the error.
At the end of the day it is MAIDSAFE that decides which is correct. After all the designer made it for MAIDSAFE and MAIDSAFE are the arbitrators.
Thanks for the link to the site. It could prove very useful.
Asking if it was an issue was a genuine question of discovery, in case it came across as anthing negative.
1 Like
I have done changes to these images (compared to the assets)
White on white below
13 Likes
I hope Iām not asking too soon, but are the eight logos @neo corrected and posted here in a state that neo and the community regard as ācompleteā?
It seems like things might be simpler in the long-run if the logos are sorted and on the MaidSafe Assets page before the pace of other community efforts pick up (e.g. MaidSafe Asia, a potential influx of new members, increased community design/development). (I know that community flyers, for example, were recently discussed in another thread.)
The most recent logo iterations from neo all look great to me, and I wasnāt able to spot any flaws with them. The only things I can think of are (as partly discussed before): adding title tags to the SVG code for the eight logos, and standardizing the sizing of all of them (Iām not sure if 100 base units was agreed upon or not via the earlier sizing poll/feedback).
2 Likes
Nick has my final copies. So I guess the assets page will be updated sometime.
With titles too. Sizing was loosely based on 100.
2 Likes
Good news! Providing Privacy, Security and Freedom | MaidSafe just got updated with the corrected logos posted by @neo 
11 Likes
@frabrunelle First, Happy (SAFE Network Forum) birthday!
Second, a couple of quick follow-up questions to (unintentionally) mark the occasion with:
- The logos on the Brand Assets page when comparing those in the ZIP file and those that are individually linked appear to be different. The file sizes are all different, and the SVG code is also different. Iām not sure if this was overlooked, or if there may be another reason Iām not aware of.
- Do you know if there are still any intentions to delete the older/error-containing safeicon.svg in the SAFE Browser repository? I ask, not to be a nag, but because I figured it may have been forgotten about.
2 Likes
Thank you 
I think itās because all the files on the maidsafe.net website (HTML files, CSS files, images, etc.) get automatically optimized during the build process (when the site gets deployed). For example, SVG files get optimized by SVGO.
The maidsafe.net website has many SVG files that are used on pages other than the Brand Assets page, so I donāt think we could simply disable this optimization step.
Maybe we could host the Assets files in a GitHub repo and embed them on Providing Privacy, Security and Freedom | MaidSafe using the GitHub link?
We removed safeicon.svg from the dev branch of MaidSafeās SAFE Browser repo about 2 months ago
See this pull request.
2 Likes
Glad to hear about the dev branch update. Thanks for that.
Also, the automatic optimization definitely seems to explain differences I saw. The SVGs in the ZIP file all seem to retain the code formatting @neo used. Yet the individually linked SVGs seem to have lost it. It seems sensible to me not to have them optimized this way, because the code is more difficult to read and understand without the intended formatting.
That sounds like a really good solution to me.
2 Likes