Literally gobsmacked. I honestly never thought I’d see a day where this was a feature!
A while back, just after the switch to oAuth, I had an item on here that needed to use the Twitter API, and I used my own app tokens, and let the user approve my app when signing in. Needless to say my Twitter account was banned, and my Twitter App access was revoked, so yeah, don’t do that!
Since then, I’ve had to leave instructions for users to create their own Twitter App, and use those details, but it’s an extra step which is a pain, and I get a few (2-3 a month) from people who genuinely have issues setting up the app (as they are doing it for the first time, can be a bit confusing you know?).
Anyway, I highly doubt my next item will be Twitter related. I love the API still, and use it a lot for my own internal apps, but they’ve made it tricky for people to sell or open source projects based around it.
I was skeptical too, I thought the display requirements were only meant for the more high class sites and for TV, but according to this discussion with a Twitter employee, they say it’s for everything. https://dev.twitter.com/discussions/15327
Yes, the display requirements apply to all scenarios in which Tweets and Twitter content are shown
This means all kind of widgets will need to be adjusted to coincide with the guidelines, but it’s not really a massive deal because all the jQuery or other JS based plugins will break when they switch to v1.1 of the API.
I must admit, the first caught my attention and thought it was funny. The fireman one, and all the copies were novel, but that wore off after a week or so. Now it’s been done to death and I can’t stand it. There’s something in our culture that means we feel the need to repeat something so many times until we’re all sick to death of it (Gangnam anyone?).
Saying that though, I just ignore them and get on with my life.
Also, remember that Twitter will soon be enforcing their rather strict display guidelines too, which means whenever you display a Tweet or a Timeline, it needs to adhere to their requirements.
More information about the display requirements can be found here: https://dev.twitter.com/terms/display-requirements and confirmation from a Twitter employee that it applies to ALL display is here: https://dev.twitter.com/discussions/15327
Key point to note is that they will provide warnings before revoking API access, which is a good thing, so at least you get warned there.
@INDUSTRYKIDZ There is a topic somewhere (possibly locked) that mentions all the updates authors and buyers have requested. I suggested they create a roadmap of them all to see what’s being considered, what’s being worked on etc.
Really we should just create a Trello board with all these, and people can join in and add cards in the appropriate headers.
It’s a shame because there are so many talented people here who are more than willing to pitch in a few hours to make the marketplaces better.
I’m not bashing Envato or anything, so don’t get me wrong, I would just love to see some more updates and not so many trival ones (like the change of the upload button, or the progress bars).
Don’t see that error at all, and I’m on iPhone 4S iOS 6.1.2
It’s slow as hell, then I see some numbers (black text on white background) and then it loads the navigation dropdown, with image background and 2 Percent Barber Shop logo.
I’d say it takes around 12 seconds to even begin loading the site, then an extra 4-5 seconds. This is on a 62mb down connection too, so nothing to do with my internet.
Hope this helps
Never going to happen, ever. I’ve personally seen this pop up in the forums a dozen times, and nothing ever comes from it. +1’ing it won’t help, requesting staff reply won’t help.
The only solution would be to include a link in your products download to a URL on your site, which the user would enter their email and license key and if not already on the system it will add them to a mailing list. That way you can target users who have bought a particular item.