following: 29
followed tags: 48
followed domains: 3
badges given: 1 of 1
hubskier for: 3817 days
I dabble in a lot of things. Mostly making. Sometimes breaking.
I made a thing: Hubski Reader
Not an expert by any means...but I would say I have about as much iOS knowledge now as I did Android knowledge when building the original. I have several good friends who do iOS dev and I can usually keep up with what they're talking about. I borrowed someone's macbook for a weekend a little while back and translated an android app I had been working on into iOS. I know that's a lot of disparate sources but I could hold my own on something on par with the current hubski app.
If I had a mac, and $99, and this had a chance of not getting rejected.... Legend tells of an upcoming API, which means at least the rejection might go away.
This is funny since I built the app near the end of a spree of contributing. Since then, I've returned to the shadows. I think I'm more of a reader than a commenter anyways. Glad to hear it helped someone though!
Ahh, Ingress. I played for a while but it kind of trailed off...wasn't super into the story behind it and I prefer geocaching for gamified running around places and discovering new things. Super clever crowdsourcing method though.
Your conception of a ball bouncing in a color cube is interesting. Because you are cycling by 10 among 256 choices, your R will always be odd and your G will always be even so you don't hit every color. Cycling by evens through evens maintains parity. However, your B will hit every value eventually. As for corners, we'd need R=255, G=0, and B=255 OR B=0. However, whenever R is 255, G is always 246, because these values move antiparallel to each other.
Honestly if it were to be supported I would much prefer arbitrary numbers of tags over one or two. Okay, maybe it should be limited to avoid an instagram-like hundred-tags-I'm-so-funny scenario, but the ability to tag posts with both general and specific tags would be nice, and many items fit under several specific tags. This is a nightmare in terms of the simplified non-repetitive tag display I'm advocating here on this same post. (Frankly, I like the simplified display better than arbitrary tag numbers.) Everything's a balancing act.
Perhaps a "what is this?" link next to community tag on the post submission page would be a good unobtrusive way to inform people of what Δ# means and how community tags work.
I like the simplicity of #@ as well, but it's understandable you'd be reticent to use it when better context about tag usage could be in its place. It's also harder to see, click, understand, and so on. The line of links reads almost as a continuous string of characters, which isn't helping the repetition issue. Maybe keep the spacing but remove the dots (" · ")? Or break the repetition with a new line for the personal and community tags? #@username ? #this.username (where this is literally the word "this")? I'm not sure I really like anything I've proposed, because each solution has some obvious drawbacks. Moving the personal tag up next to the username might add context.
Time Reversal
ACT ONE: Open on a small cafe, window facing the street. It is a gray day and clouds hang overhead. A dark-haired mustachioed man sits idly twirling a spoon in a cup of steaming hot tea. He sighs heavily and looks up, his eyes widening at what he sees.
Agreed. Showing a duplicate tag everywhere is kind of strange. Maybe the link can stay but be replaced by "@" or "personal" or ".username" or something like that. Any of those prefaced by a "#" might work too.
This is a lot of fun to play with. Do you mind if I mess with/steal the source?
Channeling Ogden Nash, not sure why. This just popped into my head. In the world of stars
There are no bars
Who hadn't had any good luck yet (?)