#* ━ beta post editor + xkit rewritten user

[covenate]

＃ｃｏｖｅｎａｔｅ，an independent and selective low activity harvey kinkle of archie horror comics. primarily portrayed as an original character written into the fear street trilogy universe. told by: vivian — twenty3, she/they pronouns.

⁽ ᵃᶠᶠⁱˡⁱᵃᵗᵉˢ ⁾ , brinaspells, url.

ｄｏｃｔｒｉｎｅ．　ｐｒｏｍｐｔｓ．　ｐｉｎｂｏａｒｄ．

[mythiecal]

＃ｍｙｔｈｉｅｃａｌ , an independent and selective low-activity multi-muse featuring characters based in various media. primarily portrayed as original characters with inspiration from various lore, mythology, and fables. told by: vivian --- twenty3, she/they pronouns.

⁽ ᵃᶠᶠⁱˡⁱᵃᵗᵉˢ ⁾ , url.

ｄｏｃｔｒｉｎｅ．　ｐｒｏｍｐｔｓ．　ｓｉｄｅｂｌｏｇ．

literature,

alice cullen, 19+ ( immortal ), she/her, bisexual. fc: taylor russel. twilight saga (anti-smeyers). canon divergent & headcanon based. secondary.

diana prince, 29+ ( immortal ), she/her, bisexual. fc: kate siegel. detective comics. canon divergent & headcanon based. secondary. * main relationship with @de2thletter's steve trevor.

gwendolyne stacy, 18 - 25, she/her, transfem, demiromantic pansexual. fc: hunter schafer. marvel comics. headcanon based. request.

isabella swan, 17 - 19, she/her, bisexual. fc: havana rose liu. twilight saga (anti-smeyers). canon divergent & headcanon based. secondary.

josephine mccoy, 19+ ( immortal ), she/her, pansexual. fc: savannah lee smith. archie horror. headcanon based. secondary.

film,

ariel tritonsdatter, 20, she/her, straight. fc: halle bailey. the little mermaid. canon divergent & headcanon based. secondary.

bárbara roberto, 20, she/her, straight. fc: jenna ortego. barbie. headcanon based. * main relationship with @de2thletter's ken carson.

harvey kinkle, 18, he/him, bisexual. fc: gavin casalegno. archie horror. canon divergent & headcanon based. secondary.

miles morales, 13 - 15, he/him, bisexual. fc: tbd. spider-verse trilogy. canon compliant & headcanon based. secondary.

television,

allison argent, 18 - 21, she/her, pansexual. fc: olivia rodrigo. teen wolf. canon divergent & headcanon based. secondary.

caroline perkins, 18 - 25, she/her, bisexual. fc: anya taylor-joy. stanger things. canon divergent & headcanon based. secondary. * written outside of st rpc.

jane hopper-byers, 11 - 14, she/they, bisexual. fc: millie bobbie brown. stanger things. something based. secondary. * written outside of st rpc.

rebecca harlowe, 17 - 23, she/they, biromantic demisexual. fc: whitney peak. teen wolf. headcanon based. secondary.

wally clark, 18, he/him, bisexual. fc: milo manheim. school spirits. headcanon based. secondary.

misc,

daphne blake, 18 - 23, she/her, bisexual. fc: julia lester. scooby-doo. headcanon based. secondary.

sasha mason, 18, she/her, pansexual. fc: halle bailey. bratz: rock angelz. headcanon based. secondary.

velma dinkley, 18 - 23, she/they, aromantic lesbian. fc: ariela barer. scooby-doo. headcanon based. secondary.

original,

henrik novak / bobby zukowski, 18 - 21, he/they, bisexual. fc: milo manheim. archie horror. headcanon based. * main relationship with nora's tbd oc. :)

loreno rodrigo, 18, she/they, pansexual. fc: giovanna grigio. archie horror. headcanon based. secondary.

treasa ó cuilinn, 20, she/her, pansexual. fc: emily alyn lind. multi-fandom. headcanon based. secondary.

[rohnnies]

＃ｒｏｈｎｎｉｅｓ，an independent and selective low activity veronica lodge of archie horror comics. primarily portrayed as an original character with inspiration from various lore and mythology. told by: vivian — twenty3, she/they pronouns.

⁽ ᵃᶠᶠⁱˡⁱᵃᵗᵉˢ ⁾ , behttys, juhggies, anticheryls, archiba1ds, url.

ｄｏｃｔｒｉｎｅ． ｐｒｏｍｐｔｓ． ｓｉｄｅｂｌｏｇ．

[spideranomaly]

#ｓｐｉｄｅｒａｎｏｍａｌｙ, an independent and selective low-activity miles morales of the spider-verse trilogy. primarily protrayed as an original character with inspiration from various spider-man adaptations. told by: vivian --- twenty3, she/they pronouns.

𝘵𝘩𝘦 𝘴𝘱𝘪𝘥𝘦𝘳-𝘣𝘢𝘯𝘥 ⁽ ᵃᶠᶠⁱˡⁱᵃᵗᵉˢ ⁾ , url.

ｓｌｉｄｅｓ．　ｐｒｏｍｐｔｓ．

[rahorak-a]

© / # 𝗥𝗔𝗛𝗢𝗥𝗔𝗞, a study into : loving and being loved, being the chosen one, the fight for a better future, and martyrdom. / A private and selective, canon divergent Leona from Riot Games' League of Legends. First established April 15th, 2020 under the url Sunszenith. Re-established July 9th, 2022 with the current url.

Headcanon based, and putting special effort into making the muse a multi-dimensional person with flaws and virtues both. Above all, this Leona is kinder, gentler, and she does not wish to hunt the Lunari ━ on the contrary, she wishes to make peace with them. She is a defender, not an attacker.

Somewhat trigger heavy  (  Violence, war, death, possession, religion, blood and gore, sexual content and more applies.  ) 𝘽𝙍��𝙒𝙎𝙀 𝙊𝙉𝙇𝙔 𝙄𝙁 𝙔𝙊𝙐 𝘼𝙍𝙀 𝙊𝙁 𝘼𝙂𝙀 𝘼𝙉𝘿 𝘾𝙊𝙈𝙁𝙊𝙍𝙏𝘼𝘽𝙇𝙀 𝙒𝙄𝙏𝙃 𝙏𝙃𝙀 𝘼𝙁𝙊𝙍𝙀𝙈𝙀𝙉𝙏𝙄𝙊𝙉𝙀𝘿. Minors, dni.

Cherished by 🌿𝗥𝗨𝗡𝗔  /  25  / She/her / Scandinavian. Please read my rules before following and my dossier before interacting, both can be found on my carrd.

➤ㅤㅤ𝗖𝗔𝗥𝗥𝗗ㅤㅤ𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗟𝗜𝗡𝗞𝗦ㅤㅤ𝗔𝗥𝗧𝗪𝗢𝗥𝗞ㅤㅤ𝗕𝗟𝗢𝗚𝗥𝗢𝗟𝗟

✧ ✦ Personals are welcome here, but do not reblog my posts please. ✦ ✧

[rpschtuff]

What is going on with cutting posts?

You may have seen some posts floating around lately about the beta editor and trimming reblogs, and possibly found yourself extremely confused trying to figure out what this tangled web of editors, extensions, and add-ons even means. I’ve been on this site for years, and I still find the whole thing terribly confusing.

So this post is my effort to explain everything -- legacy vs beta, New XKit vs XKit Rewritten, editable reblogs vs trim reblogs -- everything. This also doubles as a tutorial for the various methods of cutting posts.

TL;DR

Tumblr is in the process of switching to a new post editor that some old users have opted into, while new users have been forced into it.

The old Editable Reblogs extension does not work with this new editor, requiring people to use a new extension called Trim Reblogs.

Trim Reblogs and Editable Reblogs are not compatible. If your partner uses Editable Reblogs, you cannot cut their posts properly using Trim Reblogs (unless you’re willing to do some tedious and frankly unreasonable workarounds).

The only way for everyone in the RPC to cut their posts properly and efficiently is if everyone moves to the new system and uses Trim Reblogs. Clinging to the old system with Editable Reblogs is actively creating issues for the people using the new system -- some of whom do not have a choice.

Cutting Posts

Cutting posts is the act of removing older replies on a thread when reblogging it. This goes by several other terms, including trimming replies/reblogs or any variation of that wording, but I will be referring to it as cutting posts to avoid confusion with the Trim Reblogs extension, which will be coming up a lot.

Typically, when cutting a post, you only keep your latest reply and the reply from your partner that immediately precedes it. This means that instead of a thread looking like this...

It would like this:

Or like this, depending on the method used:

In either case, the first post is gone while the second and third post remain.

Cutting posts is done so that threads aren’t all extremely long on the dashboard. When there’s three short replies like this sample, it’s not that bad. But imagine a thread with twenty replies where each is several paragraphs long. That would require people to scroll and scroll and scroll to get past it. And since the same thread would be reblogged multiple times, your dash might become the same posts, over and over and over again, with only one new addition at the end each time.

Cutting posts is extremely common Tumblr RP etiquette. Many people won’t follow you if you don’t regularly cut replies, due to how irritating the alternative is.

Copy and Paste (Outdated)

Once upon a time, you used to be able to cut replies without any kind of extensions. Unfortunately, those days are gone.

That method worked as follows. You would go to reblog as usual...

Copy and paste the last reply, putting it in a blockquote (or using any other formatting you like, really), then add your own reply underneath.

Then you can simply hover over the older replies and click the red X in order to remove them.

And this used to work. But now, the very first post in a thread cannot be deleted -- only later reblogs can. This means that the first post will always stay above the others, no matter how far along in the thread you are.

So since cutting posts can’t be done normally, we have to rely on browser extensions. This is where things get complicated. And also where I need to explain the different editors.

Legacy vs Beta Editor

Every time you make or reblog a post, you are using Tumblr’s post editor to do so. This is the area where you type up your post, add images, etc. Tumblr has been using the same editor for several years now, and it’s called the legacy editor.

However, Tumblr has been slowly rolling out a new text editor, called the beta editor. You may remember the beta editor when it was first rolled out a couple years ago as a buggy, unstable mess -- that’s not the case anymore, and it’s no more buggy than the current editor. For text posts, it’s functionally pretty similar, and even has a few features that some of you might want, such as easy colored text and the ability to make posts non-rebloggable. (Photo and other posts are fairly different, and I know gif makers have some pretty understandable reservations and complaints about it, but I won’t be covering that here.)

Older users have the option to toggle between the legacy and beta editors at will, while new users (starting around November/December 2022) are locked into the beta editor and cannot switch back to legacy.

To check which editor you have, go to make a new text post and look in the top right corner.

If you see either of these:

You are using the legacy editor, with the option to switch between the two.

If you see this:

You are using the beta editor, with the option to switch between the two.

If you don’t see anything at all, you are using the beta editor, and cannot switch.

While the text interface of the two editors isn’t terribly different for roleplay purposes, the methods by which you need to trim reblogs are entirely different. Each requires a different extension -- specifically, a different version of XKit.

XKit

XKit is a browser extension designed to add features and functionality to Tumblr. It includes many quality of life features such as a mutual checker, better tag tracking, queue improvements, ad blocking, more detailed timestamps, and so much more. (It was preceded by a similar extension called Missing E, if you’ve been here long enough to remember that.) And among all of these many features is the ability to cut replies.

The original XKit is no longer in use, having stopped updates in 2015 and being entirely unusable now. However, a few new versions of XKit have popped up throughout the years.

New XKit & Editable Reblogs

A different team created New XKit as a successor to the original, a similar extension designed to restore many of the same features.

New XKit’s feature to cut posts is called Editable Reblogs. It works by adding a pencil button to the left of the post when you reblog.

Clicking that button will break the post’s formatting -- actually changing it to how Tumblr posts used to be formatted -- but allow it to be edited however you wish.

So in this instance, I could simply select the first reply and delete it before adding my new reply underneath.

Editable Reblogs is only available if you use the legacy editor. It does not work with the beta editor and does not even appear as an option.

XKit Rewritten & Trim Reblogs

In 2020, Tumblr began to roll out its updated dashboard, which is now permanently in effect for all users. While the new interface looks very similar, the code was actually entirely redone, and behind the scenes functions very differently from the older dashboard. As a result, some of New XKit’s features no longer work as intended -- though a few still do, such as Editable Reblogs.

In response, the New XKit team decided to similarly start from scratch and created XKit Rewritten, another iteration of the add-on with similar features once more. However, not all New XKit features are available on XKit Rewritten, and vice versa. Many people are running both extensions simultaneously to take advantage of features on both.

XKit Rewritten’s feature to cut posts is called Trim Reblogs, and it works completely differently than Editable Reblogs. With this, you first need to save the thread to your drafts with your reply already written.

You’ll see a scissors icon appear along the bottom of the post. Clicking that will open the trimming options, letting you select which previous reblogs to delete.

Clicking Trim will remove the selected reblogs.

You can then click post. You’ll note that this method preserves Tumblr’s formatting, as opposed to Editable Reblogs, which breaks it.

EDITED TO ADD: Apparently you don’t need to already have your reply written in your drafts anymore. You can save the post to your drafts without adding anything, use trim reblogs, then edit the post to add your reply. Either works fine.

This method does have two major issues, though. First, if the first post of a thread was created in the legacy editor, then the system gets really buggy and just doesn’t work.

This is what happened when I tried it out. Initially, it seemed to work as expected.

However, when I posted the reply, or simply refreshed my drafts, this happened.

Attempting to trim again simply caused this to repeat. There is no fix for this. This means that for this method to work, both you and your partners need to be using the beta editor.

EDITED TO ADD: You can fix this double posting by either using trim reblogs before adding your reply, or by adding your reply, using trim reblogs as intended, refreshing your drafts, editing the post, and clicking the red X to remove the first of the double postings. I have a better guide here.

The only other alternative is to move the thread to a fresh post when you reply, so that the new first post was made with the beta editor. Then you can cut future reblogs of the post using Trim Reblogs as normal.

However, the other major issue is that if your partner uses Editable Reblogs, you cannot use Trim Reblogs as intended. Let me show you why.

Say I want to reply to this post.

I’ll add my reply and save it to my drafts, as before.

You may have spotted the issue already. The first and second replies are now “combined” so that Tumblr sees them as a single post. We want the post to be interpreted like this, so that I can remove the oldest reply while still keeping the one immediately prior to mine.

But Trim Reblogs can only see it like this.

When I go to trim reblogs, I can only remove the previous replies as an entire unit. I can’t remove just the oldest reply and keep the one immediately prior -- either it all stays or it all goes.

This is admittedly better than nothing. However, most people do want to keep their partner’s previous reply for reference, and just to have on their blog. This means a lot of people using Trim Reblogs simply don’t cut their partner’s posts at all.

You might be able to get around this issue by combining it with the outdated cut and paste method I described above. When saving to your drafts, paste your partner’s last reply above your own, using a blockquote or whatever formatting you like to separate the two.

You can then use Trim Reblogs to remove the first post, leaving only your copy pasted reply. The formatting is broken, but it’s at least workable.

However, this will only work if the very first post of the thread was made with the beta editor -- since people using Editable Reblogs have to be using the legacy editor, you’re likely to still run into issues on a lot of posts. Which can again be solved by moving the thread to a fresh post made with the beta editor, but at this point we’re stacking so many issues on top of each other that I really can’t blame you if you just don’t want to bother with any of them.

All of this brings me to...

It’s time for the RPC to collectively switch to the new system

I’ve stuck to the legacy editor myself due to the issues described above -- using Trim Reblogs when everyone else still uses Editable Reblogs is an enormous pain that I don’t want to deal with. Even as I make this post advocating for people to switch, I’m dreading actually doing it, because I know that most of my partners still use the old system and I will have nothing but headaches.

But the thing is, everyone refusing to switch is what’s creating the headaches in the first place. If we all moved to the new system together, these issues would simply disappear, and we would all be able to effortlessly cut our posts using Trim Reblogs without ever having to worry about it again.

The RPC needs to collectively make the switch, for two reasons.

First, Tumblr is going to switch everyone to beta eventually. Refusing to switch now is really just delaying the inevitable -- it’s not a question of if you’re going to be forced into the new system, but when. By switching now, you can go ahead and get used to it and start giving feedback to both Tumblr and the XKit Rewritten team if you find anything buggy or broken.

Second, as I said above, new users are locked into beta, with no option to switch back to legacy. Trim Reblogs is their only option for cutting posts -- and as long as most of their partners are using Editable Reblogs instead, they cannot cut their posts properly. Their only option is to use a series of increasingly ridiculous workarounds that most people won’t understand. The fact that it took me 1500 words just to explain everything should tell you how confusing the whole thing is -- you can’t be that surprised when a lot of people, upon realizing that they can’t cut posts without a whole lot of tedium, decide to just not bother cutting them at all. The best way for everyone to be able to cut their posts properly and efficiently is for everyone to be on the same system.

Yes, the beta editor is different. It has some weird quirks. It will be a bit of a learning curve to get used to a new system of replying to threads. But this is a change that’s going to happen eventually, and is a change that needs to happen for a lot of people to able to cut their posts properly.

(It’s also worth noting that -- assuming you still have the option to switch -- you may be able to toggle between the two systems during the adjustment period. I haven’t been able to test this yet, but I see no reason it wouldn’t work. Use Trim Reblogs whenever possible, and especially for the partners that have already made the switch. But when you get to a reply that it just won’t work for, toggle back to the legacy editor and use Editable Reblogs just for that thread. It’s a bit annoying, but it could be the middle ground needed to help people start making the switch. And once the majority of the RPC is on the new system, then this won’t be an issue anymore.)

[resovrceful]

COPY + PASTING GIFS IN BETA EDITOR

AND HOW TO AVOID THE IMAGE URL APPEARING BELOW THE GIF. i know that for a lot of roleplayers, storing loads of gifs on computers or external hard drives just isn’t feasible. what i’ve seen a lot of since the switch over to beta, is (particularly legacy) roleplayers complaining about the fact that when copy and pasting gifs for threads, there is a new link that shows up beneath the image once the post has been made. this tutorial explains how you can avoid saving your gifs, and not have the image url on your gifs in your new threads. 

before you even start copy and pasting gifs, as a gif maker it is my duty to remind you to check the rules of the maker, that you can use the gifs that way and for the themes the thread contains! gif makers spend hours upon hours producing their content, so please be polite and adhere to their rules. thank you!

in legacy editor, users were able to copy and paste gifs via the image url without much issue. when following that same process using the beta editor (which is now widely being rolled out), the following happens:

for some reason, we end up with the url sitting below the image of the gif, and it just kind of takes away from the thread. i for one find it distracting, and also doesn’t look particularly great to me. while this is only an issue on the dash/dash view of blogs, i’ve had a number of people express their discontent with it. in order to get your gifs looking how they did in legacy, while you are editing the post you will see a link button appear in the bottom left of the gif when you hover over it:

by clicking on that button, it pulls up the image url of the gif you’ve just pasted. you can delete that link, and the gif still remains on the post. just make sure once you delete the link you click done or else it won’t delete.

you can then save your post to your drafts (i recommend just to check it worked) and you’ll see that the link below the image has gone. 

like so! i know this tutorial is purely for the aesthetics of it all and not necessarily functional, but sometimes that’s how it is! if you do wish to look at other tutorials of how to use the beta editor, i’ve included some reference links below:

a short and easy workaround for reblogs with beta & xkit rewritten, by @heartxshaped-bruises​ how to use beta editor + trim reblogs, by @brekkersource  how to use xkit rewritten / trim reblogs on mobile, by @rpclefairy​  upload gifs to a page with the beta editor, by @spacejams  what is going on with cutting posts? by @rpschtuff​

[steadfvsthearts]

Tutorial: Cutting Posts in the Beta Editor

hello everyone !! i am certainly not the only person to write a tutorial like this, but i'd thought i'd try my hand at writing one. this tutorial covers how to cut your replies in the beta editor using xkit rewritten, as well as how to remove those pesky gif source links. read on for the tutorial !!

keywords: beta editor, xkit rewritten, cutting posts, trim reblogs written 12.09.2023.

Step 1: xkit rewritten

the beta editor requires a new browser extension completely different from the previous xkit ( the one that showed in your tumblr settings ) called xkit rewritten. if you have not done so already, go ahead and install xkit rewritten for chrome or firefox.

xkit rewritten shows in your browser task bar along with your other extensions. i like to pin mine to always show. it is through here that you control all the settings.

Step 2: enable "trim reblogs"

the setting in xkit rewritten that will enable you to cut posts is called "trim reblogs". to turn it on, click the extension icon. a menu will pop up where you can toggle on and off various settings. scroll until you see "trim reblogs" and toggle it on.

you can check this is properly enabled by going to your blog page and looking at any post you've made. at the bottom of the post with the editing, reblog, and like options, there should now be a scissors icon which is the trim reblogs option !!

Step 3: cutting/trimming replies

we are now ready to write and trim a reply !!

Step 3a: write and draft or queue/schedule your reply

write your reply below the other two previous replies.

you do not need to copy or paste anything from the previous replies. simply write your reply in the editing space and put in your gif or icon if desired. when you are done, draft or queue/schedule your post.

**note: as someone who doesn't draft replies first, i'm partial to scheduling the post for a few minutes in the future as a popup like the one below shows at the bottom of the screen when you do this. you can click this pop up to take you directly to the post in your queue which just cuts out having to manually navigate to your drafts or queue.

Step 3b: trim your post !!

navigate to your drafts or queue and find your post. scroll to the bottom of the post and click the scissors icon. this is the trim reblogs icon.

you will see the following pop up. the checked box is the reply that will be removed. classically, the first box is the one you want checked as you are removing your old reply.

make sure the correct reply is checked, then click trim !! you will now see the post has been trimmed to just the proper two replies.

that's all !! you are now ready to post.

**note: if you forget to draft or schedule your post, you can trim reblogs directly on the dash too !!

Bonus: getting rid of the gif source link

if you are seeing the source link show beneath your gif like above, there is an easy way to get rid of it! in the post editor, hover over the gif and click the link icon:

delete the text in this field and click done !! that's all !!

this concludes this tutorial !! one last note : if you are an android user, you are also able to use xkit rewritten to cut posts while mobile. for a more detailed tutorial on how to set that up, see here. please consider giving this a like and/reblog if you found it helpful !! happy rping !!

[giomagnetism]

idk if anyone’s made a post about XKit Rewritten for the New Twitter Users TM but imo the site is unlivable without it. there’s a firefox version or a chrome version (or if you’re checking for a different browser, make sure it’s posted by April Sylph, she’s the current developer). the settings are configured through your browser topbar with other extensions.

it allows you a bunch of personal tweaks to customize the dashboard, like built-in adblock, blocking individual posts, putting timestamps on posts, shortening long posts, simple accessibility options like enabling alt text on the bottom of images or pausing gifs and animated elements, and hiding a whole bunch of small annoyances:

[id: a screenshot of a list of customization preferences for XKit Rewritten’s “Tweaks” setting /end id]

some of these are also available through tumblr’s native Dashboard Settings, and there’s a blacklist function using “Filtered Tags” and “Filtered Post Content” under Account Settings.

the sticky “following / for you” banner they put at the top of the desktop can be removed through ublock origin (right-click, select “block element”, and highlight the whole banner and click).

i also use the old, very broken New XKit for Old Blue which reverts the dashboard’s color palette to its old lower-contrast version, but there are again native dashboard themes which you can adjust that with. i would recommend NOT using the beta post editor because it’s much buggier and harder to use but you can’t use the newer features (such as restricting reblogs or marking explicit content) without it. worse than that it gives you a wonderful redundant pop-up confirming you’ve reblogged a post, which can also be removed through ublock origin.

alt+r reblogs posts automatically, alt+q queues posts automatically. also turn off infinite scroll and best stuff first xoxo

[soulrph]

Xkit Rewritten Nonny here! Something that’s really important to note is that you can run both New xKit and Rewritten at the same time, but anyone who still uses New for the editable reblogs (if you’re only using Rewritten) will also make it so that you cannot cut with Rewritten. The way Rewritten works is that it doesn’t allow you to actually edit their reblog, but it cuts all old trail items out with a single button. It’s a lot more user-friendly with less room for errors (and I know some RPers have occasionally expressed irritation about mutuals altering the formatting of their posts at times).

Lastly: the beta editor has way more features than the legacy editor anyway. It will apply dark mode if you use dark mode tumblr, it now has HTML capability, it allows access to reblog controls (don’t want people reblogging your headcanons? Reblog controls stops that), you can edit tags without having to delete the whole tag, and as far as I know they’re also rolling out draft auto save as well (that may also work with legacy, haven’t tested it but it was working with beta). The thing to consider is that eventually, the legacy editor will just be… gone. It uses old outdated code which means everything does have to be upgraded to new standards to keep up with said new standards, so frankly… the sooner you get used to it, the better off you’ll be. I know the creator is working on rewriting most of the modules the old xkit versions had, and is pretty quick to add new features as Tumblr changes things (remember the post footer change? Rewritten had a fix out to revert it within a day). I think a lot of people sleep on the features Rewritten actually has in the RPC without taking the time to actually look into/at it, and may end up in a lot of trouble if the older xkit versions just stop working entirely.

RPC RESOURCE THURSDAY!!

and another amazing cinnanon roll coming to the rescue with super solid info about key resources for the rpc!! i will be tagging these posts with "( rpc resource thurs. )" for those of you who want to read these and get all fancy and efficient! thank you, my wonderful angel!!!

[luckylewis]

consider this a speed-run of all things beta that may be causing legacy users issues. if there's anything else that needs explaining, i'll update this post! let's go beloveds. 🤭

🟠 BEFORE YOU SWITCH TO BETA.

if you've been previously using new xkit, you will need to download xkit rewritten. that can be found:

here for google chrome users.

here for mozailla firefox users.

once you've installed it, you can install whatever add ons are your preference from new xkit. the one that you'll need to install and enable to cut posts on beta is called trim reblogs and it looks like this:

🔴 SWITCHING TO BETA.

switching is pretty straightforward for any former legacy users and you only have to do it once.

step 1: new text post.

step 2: a pop up for the new editor will show in the top right corner. click lets go!

step 3: press let's go again.

step 4: voila, shiny new editor.

🟡 USING BETA.

for the most part, beta has condensed features of legacy to be more intuitive, which means you need to remember less keyboard shortcuts. once you've written anything in the editor itself, highlighting it will bring up this dropdown.

the list of functions in the vertical dropdown are for the following:

regular is tumblr's standard font.

bigger is, you guessed it, bigger.

i think u can figure what biggest is KSJGSHJ

quote is for if you want any part of your post to look like the quote function.

chat will turn your font into the chat format (typically used for text/sms threads!)

indented will put your paragraphs into a blockquote for those that prefer them.

bulleted list is how you create a bulletpoint list like this one you're reading.

numbered list is same as above but with (spoilers!) numbers. 😎

the list that goes horizontally is for the following:

s with a strikethrough allows you to strike through text.

b is for bolding (the keyboard shortcut still works for this).

i is for italicizing (the keyboard shortcut still works for this).

<s> is for small text (the keyboard shortcut no longer works)

the link symbol is for adding or removing links (will be utilicized further in the gif url section of this tutorial)

and the paint can symbol is for changing the font colour if that's something you want to do.

🟢 CUTTING POSTS WITH BETA.

for any of y'all that are like stark, we don't care ab this, we just wanna cut our damn posts. firstly, feel that. secondly, it needed it's own section so let's goooooo. once you get used to cutting posts on beta it becomes seamless.

there's two ways to do it.

the first one is: after drafting a reply.

the process for that is as follows:

step 1: draft your reply.

step 2: once the reply is drafted, locate the scissors symbol in the bottom row of functions.

step 3: click it and trim the post you want to be rid of, in this case for me it's my previous reply.

step 4: click trim! and hey presto, you have a cut post that's all pretty and ready for you to reply.

the second one is: after posting a reply.

step 1: go to reblog the post.

step 2: write a reply (a better one than this one SHGSHJ) and click reblog.

step 3: i know, i know, it looks like a triple reply but it only will for a second. just like step one, locate the scissors, click it, trim! your previous post and then it will be cut.

🟣 REMOVING THE URL FROM UNDER YOUR GIF IF YOU COPY AND PASTE ONE.

step 1: paste in your gif.

step 2: click the link button in the bottom left of the gif.

step 3: highlight or backspace and delete the url, click done.

step 4: no url under your gif.

⚪️ MISC ADDITIONS.

this is the button for read mores, for all u spicy legends.

this is to upload an image.

this is to post a song.

NEW FUNCTIONS BETA OFFERS:

editing tags: you no longer have to delete every tag that follows if you made a typo in one. siiiick.

auto saving drafts: a life saver (especially for this post!!) tumblr auto saves your post to your drafts as you type into it.

ANY OTHER Q'S:

feel free to hit me up and i'll help you if i can for anything specific!

this post will be updated with anything i forgot about.

[shins-rpc-sources]

A QUICK SUGGESTION FOR NEW BLOGS

for the umpteenth time, anyone who has made a blog on or after november 26th, 2022 is forced into using the beta text editor ( BTE ). this is problematic because that means the THE NEW XKIT is completely useless and that you'll have to use XKIT REWRITTEN to trim your posts and whatnot.

what i recommend you doing is stating in your pinned post the day you created your blog ( ex. 11 / 26 / 2022 ) followed by linking to this post via the month / day / year you established said blog. it lets people know that you're stuck using BTE.

another thing you can even do is just outright state in your pinned post something along the lines of "i'm a BTE user pls use BTE when interacting with me." because ... like ... idk about you guys but i go to my mutuals' blogs quite a lot and read their pinned posts / rules as well as reading their headcanons and stuff. but to each their own.

[theofficersacademy]

Happy July! Next month is our annual anniversary event, so this month will be relatively uneventful. Catch up on threads and relax.

Housekeeping

Current Month in TOA: Pegasus Moon (February)

New mission board tasks are available! You can find them [here]. Remember that at least one unaffiliated muse is required to complete certain prompts.

Tumblr's switch to the "Beta Editor" is scheduled to be complete by July 15th, resulting in users no long being able to access to Legacy Editor. Trimming beta threads requires downloading the XKit Rewritten extension. To create permanent titles for new threads, post an empty thread with just the title, save it to your drafts, and then delete the original. You can then write a new post from your reblog, and the title will be treated as a separate post when you’re trimming. If you move an older Legacy thread to a new Beta post, be sure to keep all thread tags the same and inform your partner about the switch.

A big shoutout to Ree for helming the vast majority of the Summer Arena, as well as a huge thank you to our volunteer Scorekeepers for their invaluable help!

Please don’t forget to leave feedback on our [feedback poll] for this month!

Event Incoming!

We will be holding our annual anniversary event next month! More information will be available later this month.

What to expect: Lore events in TOA are month-long events that typically split participants into multiple groups, each playing through a story campaign led by one of the mods. We place a high emphasis on making progress week-by-week, so these are our most energy-intensive events and require some commitment on your parts. Please keep this in mind if you decide to sign up. This event will incorporate combat, but narrative is the main focus. As always, make sure that your stats page is up to date.

Keep in mind that you still need to keep up with your activity during August, whether or not your muses are participating.

Important Reminders

Due to a concerning uptick in tensions surrounding shipping in TOA, this is a reminder that this group does not have any specific shipping rules.

It is not in the group's interest to enforce how certain ships are allowed to be viewed and discussed. We do not want to create an environment where "contrary" opinions are vilified and people fear retribution over disagreements. Please be respectful and considerate to your fellow members, and keep the following in mind:

1) When a ship is brought up that you don’t like, don’t engage. Just walk away. 2) If a ship is discussed that bothers you for whatever reason, whether it be personal, moral, or otherwise: politely ask the people involved to spoiler the ship or take it private. If this is something that comes up continuously or is being actively shipped within the group and you don’t want to see it, come to the mods with it and we will enforce a ship tag that you can blacklist.

3) The only shipping rules that we enforce involve the safety of our muns. Coercing someone into a specific ship, especially if that mun is a minor, is grounds for a strike or - if NSFW is involved - permanent expulsion from the group. The content of the ship otherwise does not matter to us as long as both muns have agreed to it.

4) Additionally, do not pick up a character or write with someone solely to ship with them. The mod team cannot enforce this, but we have received complaints lately about individuals who appear not to want to write with anyone unless they can ship with them. In general, this will not be well-received by the rest of the group and pressuring another person to ship with you will result in a strike, as outlined in point #3. Again, to reiterate, TOA has no shipping rules and conversations where any ship is talked about as if it’s better in any way, content-wise, morally, etc., should not happen.

Other

July Mun Birthdays: Boltz (3rd), Lucius (11th), Nic (14th), Heckles (24th), Leo (22nd), Jam (24th), Jae (31st)

July Muse Birthdays: Caspar (1st), Tana (5th), Caeldori (6th), Cordelia (7th), Kris (M) (15th), Odin (15th), Rutger (22nd), Forsyth (26th)

First-year mun anniversaries this month: Rosie (12th)

Second-year mun anniversaries this month: Tiff (9th), Red (12th), Vio (15th), Lucius (24th)

First-year muse anniversaries this month: Edain (2nd), Lyn (4th), Randal (12th), Marianne (12th), Leanne (17th), Roy (19th), Shigure (28th), Leonardo (29th)

Second-year muse anniversaries this month: Micaiah (4th), Pelleas (14th), Katarina (15th), Deirdre (17th)

Muses who have been in the group for a solid year will also be granted an Academy Brooch to put in their inventory. It doesn’t do anything. It just lets others know your character has been around the block. These characters are also granted a new opportunity to change houses if they wish to do so.

- The House Leaders

[lavishbylaw]

After reading several posts about the whole Legacy/Beta situation that Tumblr is forcing on its users, I've decided that my posts/threads will now be created with the Beta editor as of now. New users aren't able to use the OG(Legacy) editor at all and its confirmed that Tumblr will eventually force it on all users, old and new.

The best thing to do is to just integrate into using the Beta editor. As for trimming on Beta, I'll be using Xkit Rewritten's Trim Reblogs add-on. New Xkit's Editable Reblogs ( the pencil on the left side of the post ) does not and will not work on the Beta editor.

That being said, if you'd like me to move old threads over into Beta, let me know. If you, as my partner, still want to use Legacy editor, I'll use Legacy, too. But Tumblr will eventually take Legacy away.

The changes will be and are frustrating, but I'm trying to ease into it as best as I can. As long as I'm able to trim reblogs to keep thread posts as short as I can, then I'm good.

[keikakudori]

✖ How has Tumblr RP changed since you started?

the salty af munday meme

i feel like there's not a lot of fun in it these days for new people.

like, when i started in on tumblr rp waaaaay back in 2010 ( shut up I know I've been here a long time ), we didn't have great things like Xkit Rewritten or stuff like that, though i do remember i was using Missing E a lot back in the day before that was broken and then we got Xkit which led to NuXkit and then to Xkit Rewritten so i've been through a lot of tumblr changes and i think one of the things i see a lot is a lot of griping over things that aren't really such a big deal. tumblr adapts to the changes that staff throws down.

now, that's not to say i don't understand things; the recent issue with trimming reblogs that was going on a couple months ago was something i was on board with but now i've settled into using the beta editor and have been using it for a while now and it's really not that bad. would it be a pain in the ass to try writing without it? oh yeah, absolutely. it would be a tremendous pain in the ass. i probably wouldn't have bothered until the fix rolled in. but i'm honestly not that bothered by the beta editor so i suppose i'm just used to dealing with how staff will change this website in those ways.

but it does feel like there's this air of exclusivity going on. that if you don't know the right people, you can't really break into the rpc. i always do my best to be welcoming to people returning to the rpc or those who are trying to get into it. you never know what kinds of friends you'll make if you block people out and i'd love to see folks return to having fun and generally goofing around. like, i remember when gif wars were a thing. gif wars. if that doesn't date me as the kind of tumblr user i am, then i don't know what does.

i also feel like one of the most ridiculous things in the rpc these days is Sinday. fuck that, i'm not confining my horny to one day of the week. i'm gonna be horny on main and y'all can deal with it. people are horny! i am going to write spicy things and throw them on the dash! i'm not gong to hide that!

i absolutely miss things like follow forevers/bias lists and celebration of blog milestones. the concept that those were like -- bragging things or whatever is ridiculous. do you know how many new people i got to find to write with thanks to follow forever lists? i think i'm going to make one soon, a follow forever/milestone celebration post, because those were fun. you get to see these gorgeous lists and witness people saying NICE THINGS ABOUT PEOPLE THEY WRITE WITH. let's bring that back. those were always lovely. why can't we have those again? i want to see people gushing about their friends.

[rpclefairy]

Excuse me please,

I just saw your post about BTE and LTE and I'm confused. I currently use the LTE on firefox and I have the older version of xkit on here since that's what works for me with the control panel and everything. Is there a problem where posts I edit using LTE with xkit are not able to be edited by someone using the BTE and some other version of xkit? I'm not sure what all is going on.

this post explains everything!

but basically. tumblr introduced the beta editor as the editor that corresponds with the new post format that they implemented in 2018. they're still working on the editor itself so that's why it's called beta.

posts made with the legacy editor use the old code, which has a lot of glitches and errors.

because the coding of posts has been rewritten, xkit rewritten's trim reblogs feature does not work with posts made OR reblogged with the legacy editor (because it converts the post into the old code)

plus, to edit legacy posts you would use new xkit's editable reblogs. new xkit has not been updated or maintained in years, so it's causing a lot of glitches. most notoriously the glitch where drafts get posted when you try to save it.

new users no longer can toggle between beta and legacy, there's no toggle at all. and from what i've seen on the dash a lot of older accounts are beginning to lose the toggle as well, which means tumblr is retiring legacy posts altogether (as it was always planned)

the problem for us roleplayers is that if you make a post or reblog a post with the legacy editor, other people won't be able to cut their replies. so we all need to switch at the same time.

i hope that explains it! still check out that post, they include screenshots and it's easier to follow.