Design a favicon for LFGSS

Because if you're not viewing the HTML page which declares it's own favicon using the link element:
<link rel="shortcut icon" href="https://lfgss.microcosm.app/api/v1/files/3967bb6b279adca3d4b8a174c1021f3d642c32fc.png"/>

Then what the browser is going to do is look for:
https://www.lfgss.com/favicon.ico

And that redirects to:
https://www.lfgss.com/static/img/favico.png

Which is the default favicon for sites that haven't declared a custom one.

Viewing source isn't viewing a web page, it's viewing a text file... and as such, the browser uses the default path, and default favicon at that time.

I'd prefer the cap stripes if anything. Spoks are shit and have always been the subject of ridicule. I don't think it's a strong icon either. IMHO.

Not trying to get a photo of me as the icon, just think it could be better.

+1 for cap stripes.

the m was nondescript, i often overlooked it when looking in faves for lfgss.com
spok means something and is iconic, easy to spot

something like jacqui's avatar is pretty cool

right.

Because shoddy

Loving the spok

yeah that is kind of what I figured. It makes sense, but then why doesn't that /favicon.ico point to our spok?

I was a little confused why the net panel doesn't show the request for the file (even after deleting all of the favicons) but I guess developer tools Network panel != a packet sniffer.

Anyways, thanks.

why doesn't that /favicon.ico point to our spok

Why introduce another database query on every static file request for favicon.ico when older browsers will honour the yet issue the request for favicon.ico regardless (does it concurrently).

Answer: performance.

Is it really necessary to have the right favicon when you're viewing source?

No of course not. I didn't know that about how microcosm partitions microcosms. So all lfgss-specific static resources access the database?

EDIT: well not static I guess, but you know what I mean

Erm, no. But if it's a site-specific resource, then it will need to find out about the site it's on, and what the resource is.

Shared site resources are just your standard static files.

Ok, but by site specific you mean lfgss specific, yeah? So microcosm (the product) queries the db to access microcosms's (the sites [like lfgss, is that right?]) resources even if they seem static? So lfgss specific things are expensive (relatively) even if they don't seem like it.

That must be why long caching is so important. You are using cloudflare for some things, right?

You should read our code if you're interested. On github, called microweb.

One API, drives all sites, one Django codebase delivers all frontends, all shared files are just dumb static files, everything else is determined from what the API tells Django.

We use CloudFlare for DNS and SSL as much as the edge cache.

We're not yet using Railgun, but we may.

Can we maybe have a trispok? Because everyone knows they are better...

You didn't submit an entry in time.

Arrospok is the best worst wheel ever... Nice...

Now make it spin...

One API, drives all sites, one Django codebase delivers all frontends, all shared files are just dumb static files, everything else is determined from what the API tells Django

Mine is 13t so it's just, well... faster. But still late.

1 Attachment

arrospok rocks

looks like mouldy fruit

Spok works well
Has anyone mentioned chevrons?

I dunno are chevrons like magnets?

I quite like that miro.

Not sure it works when small though. Looks like some cold dying star.

Mine is 13t so it's just, well... faster.

I like that!