I live in Chicago and I'm nuts.
I like games, women, tits, vagina, porn, and tits. Oh, I forgot to say I like tits. So, if you're going to be a cuntloaf about nudity on Tumblr, then you're blogging on the wrong site. Nice to meet you. Now, take off your clothes and cough.
Feel free to ask me random things or maybe submit something. Google+
Looks like Tumblr has gotten around to making more of the post control buttons (delete, edit, etc) into icons!
This means that Missing e’s feature which created these icons is now making the new ones look wrong.
To fix this, go to the Missing e settings page (here’s how), click on the Dashboard Features tab, and under the section called Dashboard Tweaks, un-check the box next to the line that says “Replace text dashboard controls with icons (delete, edit, queue, publish)”.
In the next version, I’ll be fixing this so that the publish button and others that still don’t have icons will work when you turn that setting back on.
I’m sorry for the delay for the new version, but moving to NYC, starting a new job and getting / furnishing an apartment is pretty time-consuming.
Many Tumblr users and supporters of extensions like Missing e and XKit contacted Tumblr regarding their upcoming changes to their Terms of Service. Recently, a number of them have received a response from Tumblr similar to the one you’ll find below.
They have clarified their changes in a positive way. Although the new terms do give Tumblr a stronger position from which to come down on extension developers and users, they have made very clear statements indicating they will continue to allow Tumblr browser extensions!
Thanks so much for your support, folks! Continue using Tumblr browser extensions to your heart’s content!
Here’s the full text of the reply Tumblr has been sending to concerned extension users:
Thank you very much for taking the time to write us. Your feedback really does a tremendous amount to help us develop better policies for our community.
To answer your concern: We aren’t introducing any new policies regarding browser plug-ins.
Here’s some further clarification:
(1) The relevant language being updated appears in the draft Terms of Service under “Limitations on Automated Use”:
You may not do any of the following while accessing or using the Services: … (c) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through our currently available, published interfaces that are provided by Tumblr… (d) scrape the Services, and particularly scrape Content (as defined below) from the Services, without Tumblr’s express prior written consent
This is not a new restriction. You’ll find much harsher language in our current Terms of Service:
Subscriber shall abide by all copyright notices, information, and restrictions contained in any Content accessed through the Services. … Other than as expressly set forth in this Agreement, Subscriber may not copy, modify, publish, transmit, upload, participate in the transfer or sale of, reproduce (except as provided in this Section), create derivative works based on, distribute, perform, display, or in any way exploit, any of the Content, software, materials, or Services in whole or in part.
We think the updates go a long way towards making the terms fairer and easier to understand.
(2) Similar language is standard for just about any web product out there. You’ll find similar clauses in the legal terms for using Google, Facebook, Twitter, and Kickstarter, to name a few.
The language is important for websites because it ensures, legally, that things like phishing attacks, DoS attacks, and automated crawling/repurposing of content (read: splogs) aren’t allowed. The restrictions shouldn’t reach applications that are built on top of those services in ways that positively enhance those platforms or communities.
(3) Most importantly: We obviously don’t want to take any punitive action on your account unless you’re doing something really bad. Anyone saying that “your blog is going to be deleted for X” or “reblog this or your account will be suspended” is almost certainly a troll. Suspensions usually happen because of things like spam and impersonation, as discussed more in our new Community Guidelines. We try to apply all of these policies with a tremendous amount of care and fairness.
(4) If you’ve used a browser plug-in with Tumblr before, you’ve probably seen how we’re already enforcing this policy. Users are asked to acknowledge the added risks associated with unsupported plug-ins – namely around privacy and reliability – and to accept the extra provision that our Support team will be unable to assist with any issues that arise. That’s it, and you’re back to blogging!
(5) This also doesn’t mean anything new for developers. We already block plug-ins that we catch doing anything egregious – that is usually stealing passwords or injecting ads.
“Page scraping”, which is a way of circumventing our developer tools to do things Tumblr doesn’t support, is always a grey area. We have to talk to developers occasionally when they step over the line by, for example, mishandling user data (re: privacy or integrity), introducing behavior that poisons our community (e.g., mass-messaging and unfollow notifications), or interfering with paid or promotional features.
The bigger consideration is that, as long as a developer is hacking Tumblr rather than using our developer tools, there’s no guarantee that those hacks will keep working properly.
While we’ve always been within our rights to deny access to anyone making unsupported modifications to Tumblr, we do our best to err on the side of openness. The more enthusiastic developers and happy users, the better.
TL;DR: No plans to suspend accounts for using plug-ins, and our current policies on plug-ins aren’t changing.
We hope this was helpful. Please let us know if you have any more thoughts or questions!
If you are willing to help out, next time you get the error screen that tells you that you’ve hit the limit, I need a copy of the source code for that page. Here’s how to get it:
- Right-click on the error page and click “View Page Source”
- Right-click on the error page and click “View Page Source”
- Right-click on the error page and click “View Source”
The source code for that page will show up in a new window or tab.
When you are at this point, please let me know in the Missing e askbox and I’ll provide you with an e-mail address for you to send it to. Once you’ve got that, just copy and paste all of that source code into the email.
Thanks in advance!
It looks like Tumblr has made more progress improving your blogging experience. It now appears that they are allowing you to reblog yourself! However, their implementation appears not to allow you to reblog from a blog, back to that same blog.
I will be looking into whether or not there is anything I can do to improve on this limitation. Please be patient during this time.
Tumblr has not been idle working on their interface. Sometime earlier today or yesterday (not sure), they added the ability to upload images into the body of an answer post while responding to an ask from your inbox.
As a result, I removed the pre-existing tweak from Missing e. Missing e is still responsible for adding the + Upload photo button on new post pages (other than for text posts), however.
I don’t know that I can claim that I had any hand in this, but I like to feel that my persistence with Missing e is encouraging Tumblr to work on an interface that many felt had become stale.
It would be nice, though, if they could take the inspiration to work on their interface without implying I’m some sort of evil hacker.