Maybe there are birds? Perhaps? I think there should be. I can just have a big ol' list of all the birds I got phots of, like Olive did, that'd be fun. But, umm, again with that file 1GB file limit... hmmm... If I want pictures of the birds I've seen, rather than just, you know, a plain text list (which sounds pretty boring to me) I'd need to compress them a bit. My photo sorting system tells me that I have... about 105 birds to cover. I can cull that a bit by only picking the best photo from each bird (I think I have over 800 photos of American Robins, I should clear most of them out) and also by saying that zoo birds don't count. That should make things much more manageable, but still a lot. Hmmm...
This option is I think the easiest and suckiest one. Like I could just compress the files down into a three kilobite jpg, but that wouldn't be any fun to look at and would hardly count as any kind of documentation, and if that's the case, then really, what's the point?
If we're being realistic, people wouldn't be coming here to see what a perfect photo of a great tailed grackle looks like. You have google for that, and a my setup is, frankly, not that stellar, so why not just eschew realisim all together? I could take the photos that I have and pass them through some sort of a filter, or something. Maybe render them as ascii art? With color? Would that be doable in markdown? Would it be super difficult? Could it be automatible in a reliable and consistant way? Who knows!!
Okay, so, a little update, it seems that colored ascii art in markdown could be rather difficult to pull off, mostly because it would require recoloring every individual letter, and if I were to do it at a rather small size of, say 64x64 characters, that would still take up a ton of space. Non-colored art is still an option, I think, but birding in monochrome is rather lame, no? This complicates things, somewhat, I think.
This could be fun, I'm telling you! Unfortunatley, this would mean basically the same issue as what I had before: lots of files to be stored / uploaded / take upo that precious gig. I could perhaps make this work by simplifying the birds in an extreeme way, by some (again) algorithmic representation of the birds that's super light on storage, but I don't really know what that'd be. Plus, as with the rest of this, continuing to stay motivated will be a challenge if every bird gets it's own little portrait, and if the solution means that it isn't going to happen, then that's not really much of a solution, is it?
At this point I'm not so what to do. Option two would require some rethinking, and option three requires some... well rethinking, but I haven't really thought it through once to begin with, so can I even rethink it at this point? Option one stays feasable, I suppose, but still lame as heck.
Well actually, hold on a second here. If I take a look at one of the photos that I took that I might want to upload from my phone, it is at 2.48MB. That same image downloaded after Discord's automatic comression is at 480Kb, which is actually much smaller than I thought it might be. I mean it doesn't hold up to a zoom-in, but again, that's with discord's automatic compression, I'm sure I could find something nicer online, right? Maybe? Either way, assuming I only upload, less than a hundred of these things after culling, which seems likely, then that should be perfectly reasonable, no? 100MB for the birds and 90% of the GB for everyone else? That's not so bad, right? Like what if I just... 
Hows that? CHIRST THAT BIRD'S BIG! Uhh, can I shrink it down? Make it a few pixels less... less everything? This is great news, actually, this makes me feel much better about file sizes. Okay, that's better. So that image is 120px across, and honestly, that's fine I think. Like it could go bigger I'm sure, but for the ammount of space that I want it to take up on the page, that's not bad. Okay, yeah, I can work with this. I should sleep first, but I can work with this.
Back to The Nest