sirreal

[bbrothertedd]

[blowery]

how i start work each morning

[staff]

Tumblr! They’re here. Communities are finally here. 

Communities are a new and easy way to connect with the people on Tumblr who get it. You can invite mutuals who share your obsessions to a private Community or start a public Community for the things you love and watch all the new friends pile in. Like a clown car, Communities can fit (almost) as many people in ‘em as you want.

Today, we’re hatching Communities out of their beta shell and launching them at your collective Tumblr experience—for you to enjoy and tinker with as we continue to build them out. We’re talking globally, on web, iOS, and Android. Buckle up, baby. We’re going to be so normal about this.

You can make a Community for just about anything. Art. Gravity Falls. Knitting. Your current D&D campaign. Photography. Obscure ships. The gay people in your phone. Music. Science. Fashion. Design. Baldur’s Gate 3. You’re the wielder of your own destiny. And, thanks to our delightful early testing users, there are already so many for you to join. Hazbin Hotel? Check. Arcane? Check. The Phandom? Check, check, check.

How do you get started? 

You can browse Communities over here. 

Find specific Communities by tapping the Communities tab at the top of the search results page.

Want to create your very own Community? Right this way, maestro.

Here’s a help doc for any questions you might have.

We’re excited to see what you do with this. Go forth, hang out, have fun.

[aristoteliancomplacency]

Guys.

Y’all.

I…

I just. I just… i have discovered something. And I have laughed too much. I have laughed every time I have tried to explain it to someone. I cannot get through this.

Look. Okay.

There are two things you need to know, here.

First: There’s a style of Greek pottery that was popular during the Hellenic period, for which most of the surviving examples are from southern Italy. We call them ‘fish plates’ because, well, they’re plates, and they’re decorated with fish (and other marine life).

Like this one, currently in the Met:

Or this one, currently in the Cleveland Museum of Art:

They’re very cool. We’re not 100% sure what they were for, because most of the surviving ones were found as grave goods, but that’s a different post.

The second thing you need to know is that when we (Classics/archaeology/whatever as a discipline) have a collection of artefacts, like vases, sculptures, paintings, etc. and we do not know the name of the artist, but we’re pretty sure one artist made X, Y and Z artefacts, we come up with a name for that artist. There are a whole bunch of things that could be the source for the name, e.g. where we found most of their work (The Dipylon Master) or the potter with whom they worked (the Amasis Painter), a favourite theme (The Athena Painter), the Museum that ended up with the most famous thing they did (The Berlin Painter) or a notable aspect of their style. Like, say, The Eyebrow Painter.

Guess what kind of pottery the Eyebrow Painter made?

[labs]

Communities closed beta is here

Hello again! We’re back with an update on Communities, a big idea we had last year that we’ve been working on steadily since then. We’re abnormally jazzed to announce that we’re beginning a “closed beta” phase of this new feature, which means many of you will get to play with it soon!

We want to build this whole thing together, with as much input from all of you as possible. We’ve read and re-read the feedback from our previous post, and we’ve been surveying and interviewing people about this idea for a few months now. But it’s time to open this up even more for hands-on testing.

We’ve already begun reaching out to most of you who interacted with our previous post, as promised, with a survey asking whether you’d be interested in helping (check your email!). Over the next couple of weeks, we’ll be using the results of that survey to narrow down who we’d like to help test Communities in these initial batches.

The process is looking a bit like this:

If you received a Communities survey email from [email protected] to your registered Tumblr email address, fill it out! If you’re interested in helping us in this beta test period, that’s your way of potentially getting early access. If you did not receive an email with the Communities survey, don’t fret! Communities will be rolling out to more people as we expand our testing. 

We’ll go through the results and choose a diverse range of community ideas to gather a wide array of feedback.

Selected testers will receive a second survey with more detailed questions about their proposed community. Very practical stuff, like the name, title, and description, whether it should be public or private, the About page contents, its own community guidelines, and more.

We will create the new Tumblr community on your behalf using the information supplied. We’re building the tools that will let people create and edit communities themselves, so eventually you’ll be able to change them without needing our help. But for now, we’re creating and editing them for you, as needed.

After we’ve created the community, you’ll be made its first admin. Everything from here on out is up to you – Tumblr staff won’t be in your community (unless you invite us, of course). You’ll be able to invite anyone on Tumblr to your community. However, your community will have a population cap to start, limiting how many people can be in it and invited, as a way of keeping this beta test somewhat contained and manageable for us. We’ll be able to raise that population cap for communities that are growing and if we want to test further in that direction.

And throughout, we’ll be asking for feedback, both in some special communities for everyone in the closed beta, and via more surveys and the Support tickets we receive.

This closed beta version of Communities is far from finished, and that’s part of the reason we want to start opening it up to more of you for feedback. There are a lot of rough edges and known issues, but we think it’s far enough along that it’s usable enough for testing. We need feedback in order to feel like we’re building the right thing.

The very first public community is called “Communities Feedback” for this reason! We want everyone helping us test out communities to tell us about it, so people in this closed beta will be in there by default. We want to use that space to be more public and real-time about new pieces we’re building, bugs we’re fixing, things we know are broken, and answers to common questions. There is an additional, private community for community admins, to help shape how administrating and moderating these spaces will work. And if you don’t want to use those spaces, you can always use the “Feedback” category in our Support form.

Stay tuned for more, and keep an eye on that Communities Feedback space if you’d like to see how things are changing over time.

[labs]

Another idea: Communities on Tumblr

For a while now folks have asked us for better ways to connect with other people who share similar interests. We’re listening, and at Labs we’ve been looking into fulfilling that need, Tumblr style.

Introducing Communities, a new place to connect with others on Tumblr:

Here in Labs, we’re working on big ideas that could transform how Tumblr is used, while keeping that Tumblr vibe alive. You can see one of those ideas above. We’re calling it “Communities”, a new dedicated space on Tumblr for people to share and discuss all the content they love. Communities can cover topics like your favorite show, artist, movie, video game, your school, your board game group, friend group, big or small, whatever you want.

Each Community has their own semi-private safer space away from the regular dashboard where you can interact with other Tumblr users who share the same interests and passions as you. There are moderators and members (you!), rules, and privacy settings. Each community has its own feed of posts from members, separate from your Following and For You feeds. Interactions within community spaces stay there and replies will work more like a traditional comment section. Folks will be able to reblog posts into a community, but not out — at least not yet.

We’re very excited for you to try it, and help define the best path forward. What we have is a prototype to help us validate the idea, but there’s still plenty of questions that need answering. Over the next couple of weeks, we’ll be reaching out to people across Tumblr, and the internet at large, to try our prototype. Based on the feedback we get, we’ll iterate on the idea to see what resonates best with all of you on Tumblr.

If this sounds interesting, please like, reblog, or reply to this post, and we’ll invite you to beta test this feature when we roll it out to a wider Tumblr audience, as a little perk for following the Labs blog.

Stay tuned for more!

[aquariumpacific]

How we weigh an octopus!

[labs]

Hello again, Labs here with a recap of our test of Collections! We introduced this prototype back in September and then handed the feature to a handful of volunteers sourced from the notes on that post. Thank you again to all volunteers! 

We got so much useful feedback, and wanted to share some of that here, and reveal some next steps we’re taking. There are a couple of big projects cooking in Labs, and Collections has taken a backseat lately, but it is important to us to not leave y’all hanging. We very much want to build things with you here.

Our goal with the volunteer-based super-early phase of Collections was to see if those volunteers actually use the feature, watch what they come up with, and check whether anybody they invite to Tumblr signs up and becomes a regular user of the site. Turns out, nobody did sign up — it’s not as useful of an onboarding strategy as we thought it could be.

However, one piece of feedback we got is that Collections make great custom feeds, which people on Tumblr have been asking for a lot over the years. We hear you loud and clear: you want to supplement the standard Following / For You experience with more intentional control over feed content. That’s really important to us.

With that in mind, for those in the prototype, we’ve moved the Collections list to the left sidebar / mobile navigation as an expandable area like Account, for quick access. We like this better than putting them in the dashboard tab bar, but it’s still something we’re mulling over:

We also heard the need for more filtering options beyond just blogs and tags. What about only including a blog’s posts that use a certain tag, or excluding posts using a certain tag? Or list tags with a boolean AND operator (“posts tagged [tag] and [other tag]”), not just the OR operator we’re using now for sourcing tagged posts. Lots of ideas on how to further customize what shows up in the feed, and better define what the feed is “for”.

There were other fun, tangential bits of feedback, too, like the desire to make these Collections a collaborative feature, so that more than one person can help build a Collection. There were also several usability issues that came to the forefront, which we’ve addressed. And there were some well-articulated thoughts and questions about etiquette, such as how to seek a blog’s “permission” to be included in a Collection – that’s something we care a lot about, to help prevent this kind of feature from being a source of abuse.

Another piece of feedback we heard repeatedly is the desire for Collections of posts. This is not really what we intended with what we built, but it’s not too far afield either. We totally agree that having better, easier ways of collecting and curating individual posts would be useful, so we’re going to investigate that as a separate project.

With all of this in mind, we’ve split the work on Collections into two separate tracks:

Shaping this feature as a “customizable feeds” solution, away from an “invite others” tool.

Building a new thing for saving and curating static posts.

Stay tuned here on the Labs blog for updates on when/if we’ll be moving these Collections tracks of work to more people on Tumblr. (If you are one of the volunteers who helped us with Collections, you’ll still have access to it for the time being!)

Thanks for reading! And please reach out to us via Support, the replies here, or your reblogs, if you have any more feedback, as always.

[photomatt]

Tumblr Is Always Dying

The mainstream narrative has declared Tumblr dead for years. Last week, a leaked memo finally revealed the site’s plans to scale down its op

Elizabeth Minkel on the reports of Tumblr's death being greatly exaggerated.

[photomatt]

Have you considered a voluntary subscription for the site as a whole? It's the last social media site standing for me, I wouldn't mind paying per year for it.

Yes! We launched the Supporter badge which is 29.99/yr or 2.99/mo. You can also subscribe to ad-free which is a similar price. Subscribing, and encouraging as many people to also subscribe is the best way to support Tumblr. If you do it on the web we pay less to Apple/Google. Out of the 11.5M monthly active users of Tumblr, only about 27k have subscribed, or about 0.2%. If that were 10 or 20% we could run the site forever.

[photomatt]

Translation of Internalspeak to Externalspeak

A P2 post I made internally a month ago on October 5th about what's next for Tumblr leaked as a screenshot. This is super rare, so I'll try to translate what was said for y'all here. It was also incomplete, so here's the full thing.

We are at the point where after 600+ person-years of effort put into Tumblr since the acquisition in 2019, we have not gotten the expected results from our effort, which was to have its revenue and usage above its previous peaks. It is better to have loved and lost than never to have loved at all. (Hat tip.) It is better to have tried to summit the peak and failed than never to have tried at all. We have learned a ton on the journey, and honed skills we can use to approach other summits.

This is me saying we've worked on Tumblr for four years with ~200 people full-time, and spent well north of $100M above revenue trying to turn the site around, but it hasn't yet. That sucks, but I also want to recognized the effort of everyone who tried and gave their best.

As we talked about in the past, if it doesn’t work we’ll have a backup plan and set up the business so we don’t need to let anyone go, we’ll just need to reflect and decide where else we should concentrate our energy together. This plan is happening now: the majority of the 139 people in Bumblr will switch to other divisions. No plans for any switches in Happiness or T&S.

Bumblr is the internal team name for the product side of Tumblr, and the link was to our internal company directory which showed the ~140 people currently in that team. There are also other teams that work on Tumblr that aren't affected or changing, so this tries to say specifically who's impacted. "Happiness" is our term for customer support, and "T&S" means trust and safety, which is the team that works on fighting bots, spam, dealing with illegal stuff, etc. While Tumblr was burning cash, we managed the rest of the products and company to support and subsidize it because we thought that would turn it around.

We assume the first choice for everyone working on Tumblr is to continue working on Tumblr, but we’re going to give everyone an opportunity to have a “top three” ranked list of what other things around Automattic they would be interested in working on. To infuse some Tumblr mojo.

As we've been telling the Tumblr team for over a year, if we can't get revenue up we need to switch some portion of them to work on other things within Automattic that do generate revenue and can support their salaries. We offered a survey where people could rank stack choose what they would be interested in working on instead of Tumblr. The team has actually been performing really well in their work, which is why we aren't letting people go, they just haven't been getting results, which usually means we're working on the wrong things and we should try working on different things. We've also learned a ton working on Tumblr that I think will make our other products better.

The leak was actually incomplete, here's the rest of the post:

This survey will be posted early next week, alongside some 2-minute videos from WP.com, WooCommerce, Jetpack, Day One, Pocket Casts, WP VIP, .Org, Applied AI, Texts, self-serve advertising (Blaze), Newspack, Pressable, and Gravatar talking about why you should consider picking them as one of your choices. In the meantime, feel free to bounce around the products linked on Automattic.com to get a feel for them as a consumer and see what tickles your fancy. We’ll crunch through those preferences with what the opportunities for growth are in the various products and businesses, come back with a plan, get feedback on that, and then post the final plan. The switchovers will happen on December 31, so we start 2024 completely fresh. We are shifting from the mode of “surging” on Tumblr with tons of people to get it to exciting growth, to working on how we can run Tumblr in the most smooth and efficient manner. Pretty amazing things in the social and messaging space have been accomplished with small teams, so I’m actually quite curious to see a smaller and more focused Tumblr’s performance in 2024.

What followed were a bunch of comments that actually caused us to update the survey, other teams around Automattic posted videos pitching Tumblr folks to work on them, we did the survey, and then posted a first draft of where people could go actually just this week. (Which is maybe why the leak happened, perhaps someone didn't like the proposed changes first draft.) As a reminder, there still are no people switching, it's just planning for what will happen on December 31st, 2023.

As I mentioned this was posted on October 5th, a few weeks before we announced the acquisition of Texts on the 24th, which actually didn't leak. I do appreciate whoever shared the screenshot trimmed it down to not prematurely break the Texts news.

So now you have the full post I made, it also got 45 comments which I'm not going to share out of respect to the privacy of colleagues, but you can imagine it generated a vigorous debate internally and a lot of discussion about how to make sure we're setting up Tumblr for success in this next chapter, a lot of tech discussion about maintenance, libraries, open source, and how small teams can move faster than big teams, if they have the right environment. I'll take further questions in the Asks.

[photomatt]

Tumblr Q&A

There's some press and publications like Verge asking What's going on with Tumblr. I'm going to answer questions using the "ask" feature of Tumblr here, so everyone can see the answers. You must be logged in to ask, but use the AMA button at the top of my blog or this link.

[pdlcomics]

help with stuff

[surrelevate]

Weaponized incompetence

[caramiaaddio]

Visit Original Link

all this talk about goncharov but i dont see anybody posting the soundtrack??? like how are you gonna talk about this movie without the music

[caramiaaddio]

okay well people have asked so uh. I put it on spotify? dunno when itll show up but its there and also heres the sheet music???

[caramiaaddio]

Okay for everybody asking…it’s on spotify now! Plus apple music and youtube! Thank you all for liking my music so much!

[javascript]

Tumblr.js is back!

Hello Tumblr—your friendly neighborhood Tumblr web developers here. It’s been a while!

Remember the official JavaScript client library for the Tumblr API? tumblr.js? Well, we’ve picked it up, brushed it off, and released a new version of tumblr.js for you.

Having an official JavaScript client library for the Tumblr API means that you can interact with Tumblr in wild and wonderful ways. And we know as well as anybody how important it is to foster that kind of creativity.

Moving forward, this kind of creativity is something we’re committed to supporting. We’d love to hear about how you’re using it to build cool stuff here on Tumblr!

Some highlights:

NPF post creation is now supported via the createPost method.

The bundled TypeScript type declarations have been vastly improved and are generated from source.

Some deprecated dependencies with known vulnerabilities have been removed.

Intrigued? Have a look at the changelog or read on for more details.

Migrating

v4 includes breaking changes, so if you’re ready to upgrade to from a previous release, there are a few things to keep in mind:

The callback API has been deprecated and is expected to be removed in a future version. Please migrate to the promise API.

There is no need to use returnPromises (the method or the option). A promise will be returned when no callback is provided.

createPost is a new method for NPF posts.

Legacy post creation methods have been deprecated.

createLegacyPost is a new method with the same behavior as createPost in previous versions (rename createPost to createLegacyPost to maintain existing behavior).

The legacy post creation helpers like createPhotoPost have been removed. Use createLegacyPost(blogName, { type: 'photo' }).

See the changelog for detailed release notes.

What’s in store for the future?

We'll continue to maintain tumblr.js, but we’d like to hear from you. What do you want? How can we provide the tools for you to continue making cool stuff that makes Tumblr great?

Let us know right here or file an issue on GitHub.

Some questions for you:

We’d like to improve types to make API methods easier to use. What methods are most important to you?

Are there API methods that you miss?

Tumblr.js is a Node.js library, would you use it in the browser to build web applications?

[elparra]

wait, NPF creation is now supported in the js library, does that mean that the official web extension will soon adopt NPF too? Or is it totally unrelated?

[surrelevate]

No, the official web extension is its own thing. Not related, sorry!

[javascript]

Tumblr.js is back!

Hello Tumblr—your friendly neighborhood Tumblr web developers here. It’s been a while!

Remember the official JavaScript client library for the Tumblr API? tumblr.js? Well, we’ve picked it up, brushed it off, and released a new version of tumblr.js for you.

Having an official JavaScript client library for the Tumblr API means that you can interact with Tumblr in wild and wonderful ways. And we know as well as anybody how important it is to foster that kind of creativity.

Moving forward, this kind of creativity is something we’re committed to supporting. We’d love to hear about how you’re using it to build cool stuff here on Tumblr!

Some highlights:

NPF post creation is now supported via the createPost method.

The bundled TypeScript type declarations have been vastly improved and are generated from source.

Some deprecated dependencies with known vulnerabilities have been removed.

Intrigued? Have a look at the changelog or read on for more details.

Migrating

v4 includes breaking changes, so if you’re ready to upgrade to from a previous release, there are a few things to keep in mind:

The callback API has been deprecated and is expected to be removed in a future version. Please migrate to the promise API.

There is no need to use returnPromises (the method or the option). A promise will be returned when no callback is provided.

createPost is a new method for NPF posts.

Legacy post creation methods have been deprecated.

createLegacyPost is a new method with the same behavior as createPost in previous versions (rename createPost to createLegacyPost to maintain existing behavior).

The legacy post creation helpers like createPhotoPost have been removed. Use createLegacyPost(blogName, { type: 'photo' }).

See the changelog for detailed release notes.

What’s in store for the future?

We'll continue to maintain tumblr.js, but we’d like to hear from you. What do you want? How can we provide the tools for you to continue making cool stuff that makes Tumblr great?

Let us know right here or file an issue on GitHub.

Some questions for you:

We’d like to improve types to make API methods easier to use. What methods are most important to you?

Are there API methods that you miss?

Tumblr.js is a Node.js library, would you use it in the browser to build web applications?

[tribow]

I don't get the discourse around supporting Tumblr.

Like if you give money to Tumblr you are supporting all of their bad decisions!!!

Okay, but then how do they keep the site alive? Ads? How many people are clicking on ads here? Tumblr hasn't been scraping every tiny piece of data they can get to sell it like Facebook does either. Should they start doing that? Or should they sell more ad space even though they're already known to be a site that isn't all the great for advertisers.

This is the only two routes I can think of for attempting to stay sustainable without the use of getting money directly from their users.

Someone's gotta pay to maintain this site and also pay all employees working to do so. This isn't a one man job you need a whole team for this. Tumblr costs quite a bit to maintain.

Is it wrong to pay for an online service you frequently use? I mean, let's imagine every Tumblr user magically unite to protest against all the changes to Tumblr they disagree with by making sure Tumblr gets no financial support. What would happen? Who is paying Tumblr's staff to listen to the demands of its community? Does anyone know how long that could take? Would that really save the site or would that send it straight to its doom?

To change topic a bit. Is financially supporting a company indicative of you agreeing with what they are doing? Is it not entirely possoble to critique a company in spite of your support? There's still things like review bombing and disrupting customer service. Besides, without being a paying customer you wouldn't have much of anything to threaten Tumblr with. If majority of the userbased was supporting with money it would be very scary for Tumblr if a ton of people really pulled out.

I....

I don't know it just seems to me that people want to protest to Tumblr staff by just....doing nothing and continueing to use Tumblr. What does that do??? Do YOU want to become the product??? Tumblr could axe Tumblr Live right now all of those people complaining wouldn't give Tumblr a dime for it. These devs are fairly communicative. They have several blogs dedicated to development, there's devs with their own blogs who respond to the community and even post surveys for suggestions to other staff, they did a Q&A in Tumblr Live (annoyingly), and have been fairly transparent in clearly communicating their plans while keeping it very open to criticism.

I can't really say that about many other companies. Tumblr staff gives its users SO MANY avenues to communicate. It's almost too open. The staff can get harassed very easily (I'm sure some do). Are the people complaining about this site not using these avenues to get staff's attention? I don't see how not giving them money will get their attention. If anything it would make them more desparate to get money from us through other means than something as inoffensive as merch.

This is a website that you are using. Is it wrong to compensate those maintaining/providing this service as you use it? If it is wrong, then what are the alternatives? Am I just stupid am I missing something?

[surrelevate]

Nailed it.

[vaspider]

is crab day not a bad idea? i assumed it was just paying tumblr to do things we didn't want. i don't mean to be so negative but i genuinely don't understand S:

so part of the reason that tumblr is doing this is because they want to look good to advertisers and get money. tumblr is like 30 million in debt.

the idea is that if we can in fact demonstrate that they can get the money they need out of us by giving us things like crabs and check marks, they don't need to do that other bullshit

is it a great idea? idk, but i already buy shit like that.

[bohdank]

The short answer is yes. Every dollar that you are willing to spend on Tumblr brings us closer to the user-led monetization model that no other social networking company has managed to achieve so far.

The tragedy of commons, however, is the main challenge for the user-led monetization.

There is an expectation that other users will bear the financial burden of supporting the platform. But other users expect the same in return. In the end, only a small portion of users pay for the experience.

As a consequence, social networks can’t generate sufficient revenue directly from users, making advertising the primary viable option.