#pheonix1023

[fialleril]

So - I was just reviewing your reformation AU snippets b/c I'm so excited about how happy it feels a lot of the time. I was wondering if you had any snippets about the clones trying to integrate in little tatooine that you could share. While both the deserting clones and the former slaves are escaping slavery they had very different contexts and experiences before that escape, and the clones don't have the same language or culture as those from tatooine - so it can't have gone perfectly smoothly

Sorry, friend, but I’m actually writing this fic mostly in order (with the occasional foray back to earlier bits when I realize I need to add a scene), and I haven’t gotten to the Clone Wars parts yet, so there are no snippets to share. (I’m still at about the mid-point of AOTC, roughly speaking, though there’s more characters and more going on in this universe, so it’s taking a bit longer.)

I can tell you what I’m thinking in broad terms, though. So the first of the freed clones in this ‘verse is gonna be my man Slick, who goes to Naboo mainly because there is no clone freedom trail established yet (he’s planning to start one), but Anakin is helping him get out, and the trail Anakin knows is the Tatooine trail that ends on Naboo.

(The part Slick doesn’t know the full details of is this: when Anakin learned about the Republic’s slave army, he was furious, and he nearly quit the Jedi on the spot. It was Padme and Shmi who convinced him not to - because if he left, who among the Jedi would be willing or able to help the clones escape? There would be a freedom trail for them eventually, because there always is wherever there is slavery. And they would need allies. So Anakin went back to the Order at the end of AOTC with the explicit goal of helping any clones who want to go AWOL.)

Once he’s on Naboo, Slick needs somewhere to go, so Anakin points him in the direction of Shmi, and Slick pretty quickly gets attached to her.

As more clones start coming to Naboo on the trail, though, they’re likely going to start establishing their own communities - probably near Little Tatooine, and there will frequently be movement between them, but I do think the clones will eventually have their own enclave.

[longlivefeedback]

Hey - so I saw chapter kudos were a no, and I get why, but I was wondering if there were any changes that were still in the works that would make it easier to comment from a mobile device. One reason I wanted something like a chapter kudos was b/c I read on my phone and its hard to type out a coherent comment and avoid hitting wrong buttons on my phone when I just want to say a quick "Love this chapter, thanks for the update" message.

We don’t know if ao3 has any changes in the works to improve commenting on mobile. This doesn’t necessarily mean they don’t, but we don’t know of any. While we’d love to see, for example, a native floating review box that could be hidden or made visible while reading on mobile, or native in-line commenting, we don’t have an answer yet as to whether these are something ao3 would ever be willing or able to pursue. However, on the user end of things, there are a few current suggestions and future directions we want to pursue.

Save a list of template comments in the notes app on your phone to copy-paste/modify after you read a story.

Open the fic in a second window or use the notes app on your phone to compose a comment while reading or copy-paste lines of the fic for reference.

Use bookmarks/recommendations as feedback. While many people don’t feel comfortable leaving a single word or sentence reply, creating a bookmark allows you to make it as-is, add a single word or tags (e.g., funny, sexy, domestic dog show au), or save it for easy access to leave a longer description or comment later. Read about how to create bookmarks-as-recs here, and how to tag bookmarks here.  

Userscripts. From what I can find, it is possible to use userscripts on android or jailbroken iOS devices. However, I don’t know if these actually work (for example, does the floaty review box hide the entire screen or even function on a mobile device), and I don’t have a way to test them myself. Here is a little more about what is available. If anyone has additional info on this, please let us know. 

Take part in the google doc in-line commenting project.

- Mod Rose

[athingofvikings]

pheonix1023 replied to your post “Hey, I saw you reblog that google docs post. Just want to give an...”

So - if you want to cloud store, storing a compressed file or otherwise unreadable thing to a private bit is probably safer in terms of ToS violations. Privately hosted entities are a better bet. Also - I think that as far as arguments against things being sex-trafficing related the fictional nature of fanfic is probably also a strong protection.

On the cloud-storage point, I’d agree, but then you have the problem of dealing with an encrypted file, and definitely can’t make use of the collaborative aspect that many fanfic writers make use of for working with beta readers and the like on Google Drive.  

And it being fictional is no protection.  Last summer, Barnes & Noble suspended the accounts of a number of erotica writers for TOS violations without warning, and, as I pointed out in the prior post, there have been orchestrated suspensions of fanfic accounts in the past on numerous platforms.  We may be producing fictional works, but don’t forget that the US Congress is in the pocket of Intellectual Property holders like the MPAA.  They detest transformative works and would dearly love to get rid of us if they could.  (Remember that these are the same organizations that tried to get SOPA and PIPA passed several years ago, and historically used such hyperbolic language as comparing the VCR to the Boston Strangler and the movie industry to an innocent female victim)