On the Cheerleader Bus
Casey:
I actually don't really mind Google Docs and I don't use Google Drive.
Casey:
I don't care for that.
Casey:
Google Docs and Sheets, it's all fine.
Casey:
But my favorite thing with favorite having no air quotes around it at all, my favorite thing is that every two to three or maybe four weeks I go to record ATP and it happens at about the same time every week.
Casey:
And Google Docs is like, hey, you've been signed out.
Casey:
Why?
Casey:
I don't want to be signed out.
Casey:
And I said, no, you've been signed out.
Casey:
You've got to do your password again.
Casey:
And it's always like right as I'm sitting down to record, which is just super fun.
John:
I wonder if that's another like whatever the hell the thing is where you get a customer in Google apps for whatever.
John:
Because I'm using the regular one and I can't remember the last time I signed in.
John:
Yeah, maybe.
John:
Always signed in like years ago.
Marco:
Yeah, that's how mine is.
Marco:
I've decided basically whenever I buy a new computer, which despite your jokes aside, only happens every few years, usually.
John:
What?
John:
I think you want to reevaluate that estimate.
John:
Laptops don't count as computers.
John:
Oh, they don't.
John:
I would partially agree with you, but not really.
John:
Whenever I buy a new desktop.
John:
And that includes desktop laptops.
John:
It's like whenever I buy a new car, which rarely happens, now I buy trucks and SUVs.
John:
Right, right.
John:
They don't count either.
John:
Mm-hmm.
Casey:
Marco, you seem to be going through Kobos like you go through computers, which is to say you're on number 17 at this point.
Marco:
I'm on Kobo number two.
Marco:
Everything was fine about it.
Marco:
However, I found the Sage, which was the first one I bought, to be a little bit big.
Marco:
It was a little bit large in the hand compared to my wonderful Kindle Oasis that I liked so much.
Marco:
Then I saw that they sell a model that's pretty much the exact dimensions of the Kindle Oasis and almost the same weight.
Marco:
It's called the Libra 2 and it's a very... Oh, and the other thing that happened in the meantime is I had to charge the Kindle Oasis and it's micro USB.
Casey:
Oh, that's not happy.
Casey:
Yep, that's the only mine is, and it is not happy at all.
Marco:
As far as, I think the new Paperwhite might be the only USB-C Kindle, oh, the big one, the Kindle Scribe now is too.
Marco:
But anyway, so I was like, I realized, once I realized that Kobo had one that was basically Kindle Oasis Dimensions,
Marco:
and has this and has the page turn buttons like the oasis i thought let me try that one so i ordered that one sure enough it's wonderful it's perfect it was so good that i sent back both kindles i'm like i'm done with kindle that's it this is better um the other thing that happened was i tried pocket and it's good i
Casey:
Oh, no.
Casey:
No!
Casey:
That's not good at all.
Marco:
No.
Marco:
I'm not using it for anything else other than Kindle.
Marco:
I mean, sorry, Kobo.
Marco:
That's going to take a while.
Marco:
Other than Kobo reading.
Marco:
But I got to say the experience of saving stuff to Pocket to read on a Kobo and then reading it on the Kobo is really good.
Marco:
And it kills me to say it because I have that old beef with Pocket and
Marco:
And I'm not going to use it for anything else.
Marco:
But the Kobo has a full-blown pocket client for the most part.
Marco:
Like, you know, it probably doesn't have every feature under the sun.
Marco:
It has what you expect.
Marco:
The list of your articles, you read them, you can page through them at the end and ask you whether you want to like archive, delete, whatever.
Marco:
It's really good.
Marco:
For my purposes of reading a mix of e-books and web articles, the Kobo is a better device.
Marco:
It's simple as that.
Marco:
The Instapaper has Kindle functionality.
Marco:
I made it a long time ago.
Marco:
As far as I can tell, it hasn't changed.
Marco:
It's fine, but it's way more clunky and limited compared to this.
Marco:
So for that purpose, I got to give it to Pocket on the Kobo.
Marco:
It is a better experience for reading web stuff on e-ink.
Marco:
Otherwise, I've been happily reading on it, and it's great.
Marco:
I do still have the issues that I brought up about the e-book availability.
Marco:
Another thing that I think is worth noting is that Amazon, by its sheer scale, has tons of useful information, just stuff like its reviews and recommendations.
Marco:
And the Kobo store, just by nature of being way, I think way smaller, like I think you can tell if you look at like review counts and everything, way smaller.
Marco:
You just don't get a lot of like the user ratings, the recommendations, like it's not nearly the scale of Amazon.
Marco:
obviously you can use stuff like goodreads um which i know kindles can log into goodreads now i i didn't try that so i don't know because i don't have an account there so i don't know like how how much integration there is there but i you know there is that anyway so i think the kindle is probably still the better device if you read a lot of ebooks first of all like just a lot and you need to make sure they're always available and easily available
Marco:
And they should be the cheapest.
Marco:
We'll get to that in a moment.
Marco:
And you also want to use their built-in recommendation engines and read reviews and stuff like that.
Marco:
The Kindle's still going to be better for that.
Marco:
For my purposes, I don't read that much stuff.
Marco:
And so that's less of a factor for me.
Marco:
But otherwise, I'm so happy with the Kobo.
Marco:
It's wonderful.
Marco:
The Kobo Libra is...
Marco:
Pretty much exactly the same feature set as the Kobo Sage, minus the Sage supports a stylus that you can use to take notes by drawing on the screen.
Marco:
It doesn't actually come with it.
Marco:
I never did that.
Marco:
If I was taking notes, I would probably use something even bigger.
Marco:
But anyway, so Libra 2, great device.
Marco:
And then some quick follow-up.
Marco:
A bunch of people pointed out that Kobo has a price match policy on e-books.
Marco:
Because one of the things I said was not only was their availability not always as good as Amazon, but they were sometimes more expensive.
Marco:
apparently they will price match amazon if you like you know fill out some claim or something like that in practice i'm probably never going to actually do that because i don't want to go through the hassle and speaking of hassle i bought the kobo the i bought the libra 2 the new one that's oasisized from amazon i strongly recommend if you're going to buy a kobo device buy it from amazon because the process of now returning the kobo sage
Marco:
It's a 30-day return window.
Marco:
No questions asked.
Marco:
Great.
Marco:
You have to do a web chat.
Marco:
It took 25 minutes of a web chat.
Marco:
And then they have to email you a return label.
Marco:
That takes two days.
Marco:
And so it was a very clunky return process.
Marco:
We are spoiled by how good of a retailer Amazon is for the customers.
Marco:
I know it's not great for the sellers, in part for reasons like this, but Amazon makes it so easy to get stuff.
Marco:
It arrives quickly, and if it doesn't work out or it's broken or there's a problem, you can return it really easily.
Marco:
not all retailers work that way and buying a kobo hardware device from kobo if you have to return it is miserable so i can strongly recommend buy your books from them fine don't buy your devices straight from them buy your devices from amazon and fortunately amazon seems to sell the entire kobo lineup of physical devices and cases and everything so it's it seems like there's a good reason to buy from them
Marco:
At least if you suspect there's even a chance you might be returning it.
Marco:
So definitely do that.
Marco:
The other thing is people kept recommending me that I try these DRM stripping tools to strip the DRM off of my Kindle eBooks and bring them into Kobo DRM free.
Marco:
I do not recommend this.
Marco:
And also, I couldn't get it to work on most of them.
Marco:
Apparently, there are new versions of Kindle DRM that these packages have not learned to crack yet.
Marco:
And because these were all relatively recent purchases running on a relatively recent device, they were all that new format.
Marco:
So I was only able to crack one, which looked like it was a different format.
Marco:
All of the other ones, I couldn't crack at all.
Marco:
So I just rebought the couple that I wanted to keep reading and sent the Kindles back to Amazon.
John:
One more thing on Kobo is some people have suggested that they have really good integration with your local library.
John:
So you can essentially borrow books from your library without doing anything else.
John:
You can do it all from the Kobo.
Marco:
Yeah, I didn't get a chance to try this yet because not only do I not have a library card because there isn't a library on the island I live on.
Marco:
But none of the nearby libraries issued online cards.
Marco:
I tried.
Marco:
If you go to the Libby or Overdrive, whichever one of those is the company, it's Overdrive.
Marco:
If you go to their site, they will link to all the participating libraries that do these electronic library cards that will work with their system.
Marco:
And it's pretty much every library except...
Marco:
Most of them require you to go in in person to get a library card.
Marco:
And I currently don't have one.
Marco:
So there's that.
Marco:
But that does sound like a really good option that I want to check out because you can get you can borrow both ebooks and audio books, which is pretty cool.
Marco:
That's that's a really cool feature.
Marco:
And I've never seen it in use before, but a lot of people wrote in.
Marco:
So, yeah.
Marco:
So tell me, how is it?
Casey:
I've only done it a couple of times and I'm doing this on a Kindle.
Casey:
Well, I should back up a half step.
Casey:
So when I say I'm doing this, what I mean is I am going on a computer to find the book I want to either put it on hold or check it out or what have you.
Casey:
And then there is an integration.
Casey:
It's so long since I've set it up.
Casey:
I have no idea what the setup process was like.
Casey:
But
Casey:
There's an integration where you can say basically, yes, I would like this on my Kindle, please.
Casey:
And then the next time your Kindle syncs, it will pull down that book and you can read it until the loan ends.
Casey:
And then it will replace the book with like a PDF that basically says Tough Nuts, your loan ended.
Casey:
And it all worked really, really well.
Marco:
Does it actually say Tough Nuts?
Casey:
No, no, that would be extremely inappropriate, but also hilarious.
Casey:
But nevertheless, it does work very well.
Casey:
But again, I'm not doing any of the browsing on the Kindle itself.
Casey:
And my limited understanding of the way the Kobo works is that you can do that step on the Kobo too.
Casey:
You can actually go browsing through Libby or Overdrive.
Casey:
Like you, I always forget which one is which, but it basically means the same thing to us in this context.
Casey:
You go browsing on Libby or Overdrive, what have you, I guess, and you can find the book you want and potentially even take out a loan right then and there, which is
Casey:
which is slick.
Casey:
But no, I strongly recommend it.
Casey:
I actually worked from a local library today.
Casey:
We're very, very lucky where I am that we have excellent libraries.
Casey:
Libraries are great.
Casey:
Like if you want to read a book and you want to read it once and potentially never again, you can go to a building.
Casey:
If you're not doing it on a Kindle, you can go to a building and you can borrow the book and then you can bring it back and somebody else can read it.
Casey:
It's a very novel idea.
Casey:
I strongly recommend checking it out.
Casey:
It's quite slick.
Casey:
All right, moving right along.
Casey:
Let us talk about breaking the fourth wall, particularly around video games.
Casey:
And I swear we talked about this last episode, but John, you put this in the show notes.
Casey:
So I guess we're either talking about it again or my memory is getting even worse.
Casey:
We hit it well.
John:
Which one of those do you think it is based on past history as in the last several years of this podcast where you seem to not remember anything that we've done on the previous episode?
Casey:
Well, but that's the thing.
Casey:
I feel like we did do this on a prior episode.
John:
Do you re-listen to episodes?
Casey:
No.
Casey:
I used to very early on.
John:
You totally should because that's why I know what we talked about because I listen back.
Casey:
Fair enough.
Casey:
All right.
Casey:
So I talked about in my head, but never talked about with you fine folks.
John:
Do you want me to tell you why this is in here?
Casey:
Oh, sure.
Casey:
Okay, go ahead.
John:
Because we did talk about this game and this thing last episode.
John:
So I can have credit.
John:
But we had some questions about it, and this answers one of the questions.
John:
That's why it's follow-up.
Casey:
Alright, so David writes, Metal Gear Solid did indeed include a system where Psycho Mantis would read your quote-unquote mind by using controller port 1.
Casey:
Switched to port 2 and he couldn't anticipate you anymore.
Casey:
That's a separate thing from the memory card trick.
John:
Yeah, because I was talking about the memory card thing where I would look in your memory card to see what other games you've played and say things that would freak you out.
John:
How does he know that?
John:
Ooh, is it because he's reading your memory card?
John:
But the person who wrote in said there was a thing about switching ports and I didn't remember that.
John:
So apparently those are two entirely separate things.
John:
Basically that...
John:
When they say anticipate your moves, like you'd be trying to beat the boss and had it programmed to be more difficult if your controller was put into port one or whatever.
John:
That's what it boils down to because, you know, it's software.
John:
It could also read your controller on port two if it wanted to, but that was what you were supposed to do is figure out that you had to change ports.
Casey:
Fourth wall breaking.
Casey:
That is very slick.
Casey:
And I have I played Metal Gear Solid.
Casey:
I loved it.
Casey:
And I have zero recollection of that whatsoever.
Casey:
Andrew Clark writes, I'm actually fairly perturbed of myself for not thinking of this because I loved this.
Casey:
Andrew Clark writes, there's a fantastic mind bending fourth wall breaking puzzle game for iOS called Black Box.
Casey:
I feel like all of us met the developer whose name is escaping me like many, many years ago, WWDC, and he was a super nice fellow.
Casey:
Black Box is amazing.
Casey:
If you've never played it, you absolutely should grab it.
Casey:
It is super, super fun and extremely clever in the puzzles that you have to solve.
Casey:
I cannot recommend it enough.
Casey:
I absolutely love this thing.
Casey:
So we'll put an App Store link in the show notes.
Casey:
You should check it out.
Casey:
David Kung writes, I enjoyed the discussion on HP 533 about the fool's errand and especially Metal Gear Solid and the memory card corruption fears of eternal darkness.
Casey:
My favorite memory of that was during the PlayStation 3 and Xbox 360 era playing Batman Arkham Asylum.
Casey:
Late in the game, Scarecrow doses Batman with fear gas, but it's subtle and the game looks like it's crashing.
Casey:
Since this was during the Red Ring of Death era, many people were fooled.
Casey:
I had a PS3, had been warned, and still thought the game had crashed and restarted my system before I realized I'd been had.
Casey:
Fortunately, the game realized people would do this in autosaves right before, but still, it was a memory I will never forget.
John:
That would be cruel if it didn't autosave and wiped all your progress because you thought your thing crashed.
John:
Then you got to the same point.
John:
It crashed again?
John:
What are the odds?
John:
Right.
Casey:
Michael Lecter writes, on the subject of 15-inch MacBook Airs and businesses wanting them, I'm of two minds on that.
Casey:
Our standard corporate setup for employees globally is a desk configuration with either dual 24 or 27-inch displays.
Casey:
We have 12,000 desks set up this way in multiple countries with plain-jane Dell Thunderbolt docking station.
Casey:
And unfortunately, the M1 or an M2 MacBook Air won't light up that second display where a MacBook Pro does.
Casey:
Needless to say, we don't buy Airs because end-users believe the Mac is broken when that second display doesn't light up or just mirrors their first one.
Casey:
It's seemingly an artificial limitation that Apple places on the airline to push pros in deeper-pocketed businesses to pony up several hundred more dollars and purchase a pro.
Marco:
So, okay, first of all, I don't think it's an intentional limitation.
Marco:
I think it's a real limitation.
Marco:
You know, Apple doesn't intentionally, you know, restrict product capabilities that would otherwise be technically very simple and reasonable to implement.
Marco:
So, you know, that's not really a thing.
Marco:
Right.
John:
Do you remember when we originally talked about this?
John:
Like when these things first came out and said they can only support one monitor?
John:
And I think we threw the question out there like, hey, what's the deal?
John:
Why do they only support one monitor?
John:
What is the limitations that's causing them?
John:
Is it a GPU limitation?
John:
Is it the video driver?
John:
Like what provides the limit?
John:
And I don't think we ever got a satisfactory answer.
John:
I generally agree that Apple doesn't sort of intentionally cripple things, but the fact that I don't actually know what the limitation is, where the limitation resides, is it the circuitry in the SOC?
John:
Is it a VRAM thing?
John:
I still say the jury's out on why this is the case.
John:
And even if it is a hardware thing, that still comes down to, hey, when they were designing the plain old M1 or plain old M2 and it comes time to design the video driving circuitry,
John:
That's a choice they make at that point to be that limited.
John:
Does it save power?
John:
Does it save money?
John:
Like, I don't actually understand this trade off.
John:
So I kind of understand the frustration because it seems like a regression because, you know, the Intel MacBook Air that everybody loved from 2011.
John:
couldn't that drive more than one display and that that's you know over a decade ago it does seem not great that uh that this otherwise amazingly capable computer has this limitation whether it's a even if it's a real limitation as in you know the hardware just can't do it i think that might have been a bad choice
Casey:
Matthew Kraft writes, two years ago, my wife and I each did extensive research before buying standing desks.
Casey:
She chose Fully, that's the one that I bought, and I went with the Uplift V2.
Casey:
When I assembled the desks, it immediately became apparent that they were from the same OEM.
Casey:
The control box, keypad, etc.
Casey:
were all essentially identical.
Casey:
This is not a big deal.
Casey:
We love our desks.
Casey:
And perhaps there are other components that differ between the two.
Casey:
I just thought it was hilarious because we spent so much time debating between the two options only to learn how truly similar they are.
Casey:
This is news to me.
Casey:
I can't say I'm surprised, but news to me if this is true.
John:
I mean, part of what you're choosing is the surface material, too, and the shape and details like that.
John:
So I can believe that the sort of mechanism underneath it is probably from some common manufacturer.
John:
But maybe you just like the, you know, the wood choices on one better than the other.
Casey:
And then Wade Tregascus writes, there is a downside to using the camera shutter to protect the sensor.
Casey:
Camera shutters are incredibly light because they have to move at incredible speeds and accelerations with as little jolting as possible.
Casey:
and that makes them extremely fragile.
Casey:
If the shutter is down when you're swapping lenses and your finger slips just a little bit, you can easily damage the shutter such that you can no longer take photos.
Casey:
What you want is a camera that doesn't use a mechanical shutter at all and instead has a more robust sensor shield that's purely for sensor protection and can be much tougher.
Casey:
Nikon is the first to start doing this with the Z9, but others will follow suit in time.
Casey:
P.S., there was a similar problem before the mirrorless era when you could bump the mirror and knock it out of alignment.
Casey:
That could cause the viewfinder to become a bit soft, or worse, cause the autofocus system to stop working properly.
John:
i have a hard time imagining my finger ever going so far inside the camera to touch the shutter like this like that's i'm so careful when i change lenses like my my fingers are gonna slip inside the camera body and i'm gonna touch where the sensor would be but the shutter is ah yeah anyway that's something to watch out for because yeah those the shutters are delicate but don't put your fingers inside your camera even by accident
Marco:
We are brought to you this week by Steam Clock, a design and development studio that believes apps should be more than ultra-fine.
Marco:
They work with growing companies to level up their customer-facing iOS and Android apps.
Marco:
Often, Steam Clock's customers have already taken a first crack at the problem and ended up with a really mediocre app.
Marco:
If your customers rate your app 3 out of 5 stars or worse, it might be time to contact Steam Clock.
Marco:
What all Steam Clock's clients have in common is that they care about great customer experiences and have the resources and will to fund a great app.
Marco:
Steam Clock's work comes mostly from referrals, but they believe ATP listeners, you all, you're wonderful, right?
Marco:
You're also likelier to care about quality and user experience.
Marco:
So if people say they heard about Steam Clock from ATP, that's a good signal they could be a good fit for the kind of work Steam Clock does.
Marco:
There are now 16 people strong with a bunch of talented designers, developers, and leadership that know how to ship great apps.
Marco:
Steam Clock can build apps using React Native and other cross-platform tools, but they're also very experienced at building out excellent Swift and Kotlin native apps and in helping companies evaluate the trade-offs of both approaches.
Marco:
So if your business is growing, your customers deserve a better app.
Marco:
Visit steamclock.com slash ATP.
Marco:
Get in touch with Steam Clock.
Marco:
That's also, there's some fun stuff on that page too.
Marco:
Nice little message for ATP listeners.
Marco:
So steamclock.com slash ATP.
Marco:
Once again, your customers deserve a better app.
Marco:
Visit Steam Clock, steamclock.com slash ATP.
Marco:
Thank you so much to Steam Clock for making the world better by making better apps and also for sponsoring our show.
Casey:
Apple is to release final cut pro and logic pro on the iPad.
Casey:
The time has finally come.
Casey:
Apple is trying to do something quote unquote professional on the iPad.
Casey:
So we'll put a link to the newsroom.
Casey:
Um,
Casey:
Press release in the show notes.
Casey:
And the bare bones version of it is these will be available in the App Store starting on Tuesday, May 23rd.
Casey:
Final Cut Pro and Logic Pro for iPad will each be available for $4.99 US per month or $50, basically $49, per year with a 1-1-3 trial.
Casey:
Final Cut Pro is compatible with the M1 chip iPad models or later, and Logic Pro will be available on the A12 Bionic chip iPad models or later.
Casey:
Final Cut Pro for iPad and Logic Pro for iPad both require iPadOS 16.4.
Casey:
With regard to Final Cut Pro, there's some interesting features that I called out that I thought were worth discussing.
Casey:
You can do live drawings, so users can draw and write directly on top of the video content using Apple Pencil.
Casey:
On the iPad Pro with an M2, the Apple Pencil Hover unlocks the ability for users to quickly skim and preview footage without ever touching the screen.
Casey:
So if you use Final Cut on a Mac, as you slide the cursor over the timeline, you're not clicking or anything, you're just moving laterally, then the timeline, you can see the video moving as you're scrolling left and right.
Casey:
And apparently using the hover thing on M2 iPad Pros, you can do the same thing, which is pretty cool.
Casey:
They also have some trick like circular control that apparently will also let you advance or rewind the playhead, which looked neat in the videos.
Casey:
But it was hard to tell because they only showed it very, very briefly.
Casey:
Then they have scene removal mask.
Casey:
With scene removal mask, creators can quickly remove or replace the background behind a subject in a clip without using a green screen.
Casey:
AutoCrop also adjusts footage for vertical square or other aspect ratios.
Casey:
And with voice isolation, background noise can easily be removed from the audio captured in the field.
Casey:
One thing I thought was very interesting, iPad users can go and export their Final Cut Pro projects to the Mac, but it was pretty clear that round tripping is not possible and going from Mac to iPad is no dice.
Casey:
So Jason over at Six Colors writes, Final Cut Pro for iPad seems to be a subset of the Mac version.
Casey:
You can start on iPad, move to Mac, but the migration won't work the other way.
Casey:
And a bunch of features from the Mac just aren't there on the iPad.
Casey:
The lack of feature parity is unfortunate, but perhaps a bit understandable.
Casey:
But as someone who rarely uses those pro-level features, it's also frustrating to realize that even my simple projects won't be portable in case I need to leave home and run off somewhere with an iPad.
Casey:
And then, like we said earlier, Final Cut Pro for iPad can go on a 12.9-inch iPad Pro, 5th or 6th gen, 11-inch, 3rd or 4th gen, iPad Air, 5th gen, and again, iPad OS 16.4 or later.
Casey:
Before we get to Logic Pro, any initial thoughts?
Casey:
Obviously, we haven't used it, but at a glance, this looked like a not-too-watered-down version of the quote-unquote real app.
Casey:
I mean, it looked pretty impressive in the very, very little that we've been shown so far.
Casey:
Marco, what did you think?
Marco:
I'm going to reserve my comments for talking about the two together.
Casey:
Okay, fair enough.
Casey:
John, any thoughts particularly about Final Cut?
John:
I mean, one of the differences we'll get to in a second is the feature parity with the desktop version.
John:
We go back to the same thing we went back with with Stage Manager.
John:
Why Stage Manager only on the M1?
John:
Oh, it needs virtual memory.
John:
But what about this thing that doesn't have virtual memory but can still run it?
John:
Apple never wants to tell you technically why the limitations are what they are.
Yeah.
John:
you know setting aside which ones it can run on i'm more willing to forget that but it's the feature parity it's the non it's the inability to round trip uh the m1 soc in the m1 ipads is fantastically more powerful than many many machines the final cut pro the current version of final cut pro ran on and still runs on the only thing that i can think of that it really lacks is ram because you you don't get to pick how much ram your ipad has and even the the biggest ipad does not have that much ram uh
John:
I think the max is six maybe, I don't remember off the top of my head.
John:
But the minimum you can get on a Mac is eight.
John:
I'm just, I don't quite understand why they wouldn't do round trip ability.
John:
Like maybe there are features that are too slow and those features would be locked out, but it really makes it, not that it makes it feel like toy final cut, cause that's not fair.
John:
It seems like it's pretty much the full final cut minus features here or there.
John:
But that just makes it so much less useful because what people want to do, like Jason said, is you have a Final Cut project and you need to go somewhere where you don't have your laptop or you want to work on something quickly and you just have your iPad.
John:
But you can't do that.
John:
It's just, oh, sorry, that's a Mac thing and I can't work on it here.
John:
I just, I find it, I find it hard to understand why they would have made that choice because it just locks out so much stuff.
John:
And especially since like, you know, iPads just get more powerful.
John:
I would say that again, the I'm on iPad is more than, should be more than powerful enough to work with the same projects as the Mac version of file cut.
John:
Now, maybe it's really bad at them.
John:
I don't know enough about video editing to know which features they locked out, or maybe it would be terribly slow, but by just saying, look, they're not even, the project format or whatever the file format is, they're not even the same thing.
John:
It's an export step to go to the Mac, and Final Cut on the iPad just can't open
John:
mac projects that's that is the most frustrating thing for me about this application i wish apple would have explained it maybe it will go away in the future again ipads continue to get more powerful but maybe it's not a power thing maybe there's something else about the projects like my most optimistic take on it is that the
John:
the project format on the iPad represents the future of the project format on the Mac and they just haven't gotten there.
John:
You know what I mean?
John:
Like that this is a newer, fancy rap and they've come up with a, a better format for the projects and that eventually the Mac version will support that better format.
John:
And then there'll be parody.
John:
Something like that could have happened, but yeah.
John:
I find that disappointing because it just makes it seem like, again, even though this is not fair, it makes it seem like the training wheels version or the mobile version.
John:
It's not as good or whatever.
John:
The good thing about it, though, is looking at the screenshots is that it's not, obviously, I mean, we didn't think it would be, but just to emphasize, it's not the Mac version of Final Cut shoved onto a small screen.
John:
Like, it is made for the iPad.
John:
It is made for the things the iPad can do, for touch, for the pencil, for pencil hover, like...
John:
All that stuff is great.
John:
I hope it works well.
John:
I hope when people who actually do video editing get it into their hands, they find it useful and find that it really does let them edit video in a way they couldn't on a Mac.
John:
That's what you want out of this.
John:
Speaking of Jason at Six Calls, he edits audio on the iPad.
John:
Because you can edit audio on an iPad in ways that you can't on a Mac.
John:
Like it's his workflow of using like multiple touch with fingers and everything.
John:
Like he's just like two finger tap to play pause and stuff like that and sliding things around with the pencil in his fingers.
John:
You just can't do that on a Mac because Macs don't have touch screens.
John:
Macs don't have pencils.
John:
They have different input devices, right?
John:
So it seems like Final Cut does that on the iPad, and I think that's great.
John:
Just disappointed about the file form.
John:
And the final thing, it's the same for Logic.
John:
It's the subscription pricing.
John:
Some people are disappointed by that.
John:
And I think the main reason, the main legitimate reason to get disappointed by subscription pricing for Final Cut and Logic is that they're made by Apple.
John:
And Apple has other ways to make money.
John:
So what people want is they say, hey, Apple, you make so much money on other things that you do.
John:
Can't you subsidize your pro applications and sell them for an affordable one-time price?
John:
even though your continued development of them costs money, pay for it with your iPhone profits, pay for it with the other stuff, pay for it with your services revenue or whatever.
John:
That's what people think.
John:
Cause they, you know, even if they're willing to believe like, well, developers need to be paid some regular amount of money to maintain an application.
John:
Apple doesn't because Apple's got money from all sorts of other stuff.
John:
And that makes some sense.
John:
But remember the Apple's also a platform vendor and they're already in this whole strategy tax situation where, um,
John:
We want people to buy our hardware products, and these software applications make our hardware products more valuable, but they also compete with third-party software products like Adobe Premiere.
John:
Obviously, there's fewer competitors in this market because it's kind of the high-end stuff or whatever, but whenever Apple makes an application,
John:
It competes with third party applications and Apple wants third party developers to develop for its platform.
John:
So it's this balancing act.
John:
How much does Apple compete with its third parties versus how much does it support them by making the APIs they need and so on and so forth.
John:
Already Apple has a tremendous advantage because these applications only work with an operating system that isn't even released yet.
John:
Third-party developers can't do that because they don't get to see the build as early.
John:
They don't know what the plans are.
John:
Yes, there are baities or whatever, but it's very difficult to exactly time your releases with the brand new version, especially since surely there's stuff in iPadOS 16.4 that is there specifically to support these applications.
John:
That is an advantage that you don't have as a third-party developer most of the time, unless maybe you're Microsoft or Adobe.
John:
So they have to Apple has to be careful.
John:
And the people will say Apple should subsidize it with their profits.
John:
What you're saying is Apple should even more unfairly take advantage of the fact that it is the platform owner to even more unfairly compete with the other third party applications that do this same task.
John:
Um, and I think that would be unwise.
John:
Um, I think Apple should try to have a somewhat sustainable business model for its pro applications.
John:
Cause the, the slam on Apple and its pro applications for years is that they kind of give up on them.
John:
Like what happened to aperture, right?
John:
Or, uh, what was that other one?
John:
Uh, shake or, you know, or is motion gone now to, I don't remember.
John:
Like, uh,
John:
At various times, Apple has acquired and developed pro-level applications and then just kind of said, eh, this is a tough business and we're kind of losing, so never mind.
John:
And that's disappointing for people who invest in those applications.
John:
We built our business around, you know, this one pro application and now it's gone.
John:
Or I put my giant photo library into Aperture and then Aperture goes away one day and it feels bad to have to make this terrible transition, right?
Yeah.
John:
So I don't know if $5 a month or $50 a year actually is sustainable in terms of how much does Apple, you know, how much does it cost Apple to continue developing these versus how much money they get from them.
John:
But I think the idea of a fairly low subscription price for these applications is fine.
John:
And I would not be surprised if these prices do not cover Apple's costs, but they come closer to covering the cost than a one-time fixed fee probably does.
John:
And the fact that there's monthly makes it way cheaper for somebody who just needs to edit video three months out of the year than if they had to buy the $100 Final Cut.
Marco:
More than that, just for reference, Final Cut is $300.
Marco:
Logic is $200.
Marco:
And these are $50 a year each for the iPad versions.
John:
i mean for the people who know well but i'm i need it all the time and it's smart it's like you know it's not like you're gonna buy that one copy of final cut and never buy another one like they do have major upgrades and you have to buy it again so they don't have paid upgrades in the mac app store no i know what i mean like in terms of like when you have to buy the new version like the old one stops being supported i don't know how often they do that with the pro applications but occasionally there's a new you can't just keep using you know final cut pro version 4 forever eventually you have to buy a new version
Marco:
well to be clear though i don't i mean i've i own both these applications on the mac i don't think they've done a version change since the mac app store versions came out yeah like i've been using the same version of logic for i don't know probably seven or eight years that i paid 200 for seven or eight years ago so you know if i if i had to pay for my mac version on this subscription plan which i
Marco:
frankly this is probably the future of the mac apps and maybe it would be a unified purchase in the future as well who knows maybe it's maybe the mac apps become catalyst apps which i'm a little nervous about that but you know that's honestly it wouldn't surprise me if that's the direction they go like maybe this just is logic pro 11 like they did with uh the new version of imovie eventually became the new version of foul cut kind of
Marco:
Yeah, yeah, like, you know, kind of a redo, you know, starting from the iPad version as the Catalyst version to become the new Mac version.
Marco:
Like, that wouldn't surprise me if that's what they do, and then maybe it would be unified purchase.
Marco:
Anyway, all that is to say, if you're, you know, I've been using the same version of Logic for many, many years, so I would be paying more under this subscription plan, but not by that much.
Marco:
And granted, I mean, for the amount of use, like, if you're using Logic or Final Cut,
Marco:
for more than four years, then not only are you getting your money's worth, but that you can probably afford it if you're using those programs for that long.
Marco:
You're probably doing something somewhat serious with your work.
John:
And that idea that they haven't been updated in a while, that's another thing.
John:
Subscription pricing, in theory, provides a revenue stream that will give the customer...
John:
a sustainable model for future updates that that that is not that you know that some there's there's money coming in all the time to fund the continued development of this application and you know if aperture had subscription pricing maybe they would have had enough critical mass to keep going but the way they were selling it apparently it wasn't a viable business for apple and they bailed out of it right so i think these prices seem low like if you've priced out
John:
you know adobe photoshop i believe it does not cost fifty dollars a year to get photoshop and yeah so so like these seem like good prices but i still think it should not be like free or one-time purchase of 30 bucks or one-time purchase of a hundred dollars or whatever uh just because this type of subscription pricing though it may be low and subsidized by other stuff i think still leaves enough
John:
leave space for third-party applications to continue to exist so i i have no complaints whatsoever with the pricing in fact i was shocked at how low it was and i love the fact that there is monthly because if i ever needed final cut pro for you know just to try something or whatever my previous option was pay a couple hundred dollars and then you know hope for the best and now i can pay five bucks and try it out so i give a thumbs up
Marco:
yeah i i too i would have like i would gladly have paid five dollars for a month of using it because i hardly ever use final cut i bought it because i thought i would use it more than i did i ended up hardly ever using it and there goes three hundred dollars you know um no i think the the pricing is is reasonable and and not unexpected it's you know the interesting thing i i believe this is apple's first subscription price software uh so that's that's interesting and
Marco:
In the sense that you're not paying for any kind of service behind this.
Marco:
You're literally just paying a subscription price to use the app.
Marco:
Like many apps are priced these days.
Marco:
But that is new to Apple.
Marco:
So that's interesting.
Marco:
But otherwise, I think it's fine.
John:
Do you think they'll apply the same rules about... Remember they had the whole thing when they first came out with subscription software where there was like these vague app store rules that you have to add substantial additional software on some regular basis to justify your subscription?
John:
I have a feeling that Apple is not going to hold itself to that standard.
Marco:
I don't even think they hold anybody that standard anymore.
Marco:
All the apps in the app store, you can crop photos for $3 a week.
Marco:
I don't think they're doing anything like that.
John:
When subscription pricing first came out, there was like, well, what about productivity app?
John:
Remember, it was like subscription if you have content drops or whatever.
John:
If you're adding new content to the app, people can subscribe to that.
John:
But if you have a productivity-style application...
John:
there was some vague wording about, well, if you just have a note-taking application, you need to justify the fact that, and I'm assuming that went away, like many of the worst App Store rules.
John:
But I just find it funny that even if that rule does still exist or did still exist,
John:
that's another example of how apple doesn't have to worry about that like they could in theory put uh final cut in the apps or for the ipad and just not update it for six years and still charge subscription pricing and no one's going to stop them because they own the platform well and to be fair i i don't know about final cut because i don't really use it much but logic is updated all the time like they actually do a really good job of updating logic on the mac it's never with anything that benefits me as a podcaster because logic is not made for the kind of use that i do at all
Marco:
And it never stopped reminding me of that at every single turn.
Marco:
But for actual musicians who are using it to compose music, which is what it's really for, there's constant updates to it.
Marco:
So I trust them to not abandon these things, at least on the Mac.
Marco:
On the iPad, we'll see.
Marco:
I mean, to me, I think the big story about these apps is...
Marco:
First of all, there's kind of the meta story of why did this drop now before WWDC?
Marco:
And the likely answer is it's going to be a pretty full WWDC of other stuff, which is very promising and very exciting.
Marco:
So that's, you know, I love like the May Apple drops of like stuff that gets kicked out of the keynote for space, generally speaking.
Marco:
They kind of release it now or in July or whatever.
Marco:
So that's always fun.
Marco:
The big story here is these are pretty serious professional apps being released on the iPad.
Marco:
Now, everyone has a hot take on this, I'm sure.
Marco:
There's the good thing in the sense that if you use an iPad for your work and you've run into limitations of the existing video and audio editing options that you had...
Marco:
this might help you.
Marco:
And that's great.
Marco:
This also might help Apple sell more iPad Pros, which will kind of reinforce the chicken and egg situation and make it better, make there a larger market for pro apps to be made on the iPad.
Marco:
So that's good too.
Marco:
However...
Marco:
Using the iPad Pro as a professional, doing the kind of things these apps do, which often involves moving files around, getting different assets together from different places, lots of data management, asset management, file management, downloads, moving stuff, converting stuff, integration with other tools...
Marco:
Those are all areas that the iPad OS is just not good at.
Marco:
Like, many of those things are not possible.
Marco:
Many of those things are possible, but clunky and kind of a hindrance to actually do.
Marco:
I see a lot of people saying they're really happy these apps exist.
Marco:
I have not seen a lot of people saying, I will use these apps on my iPad Pro to do my work.
Marco:
I don't think I've seen anybody saying they're going to use them.
Marco:
Obviously, I have a small sample size of the handful of people I follow on the social networks that we're going to talk about in a little bit.
Marco:
But I see a lot of like, oh, that's good for other people who use iPads.
Marco:
Not me, of course.
Marco:
No, no, not me.
Marco:
But other people, yeah, they'll use us like crazy.
John:
Well, I mean, so speaking of other people, though, we just got done talking about pricing.
John:
I do feel like that is one of the important...
John:
the upsides of these applications it's the person who currently is not editing video uh with final cut because they didn't have 300 to spend on it and maybe they don't even have a fancy mac uh but maybe they can swing an ipad in fact maybe they already have like an old m1 ipad pro right suddenly they realize you know what
John:
I can get Final Cut Pro.
John:
I've never even used it.
John:
I don't know how to use it, but it's an iPad app.
John:
I'm comfortable with an iPad.
John:
Let me give it a try.
John:
The new creators who may be like, you know, for the same way that, you know, I can't think of a good example, but like many times there's people who are in an industry using a technology stack and a software stack that is familiar to them.
John:
And they say you can't do real work in field X unless you do what I'm doing.
John:
And some kid comes up using much worse stuff on much worse hardware and much worse software using an application that the old fogies have never even heard of.
John:
And they become the next generation that does all that stuff.
John:
I'm sure there's an analogy of like how the original YouTubers did their stuff versus how the next generation of YouTubers did their stuff.
Marco:
five dollars a month to try out final cut on an ipad you might already have granted it's the pro ipad and they're expensive but you know maybe you got uh parents who are well off and they got you an ipad pro i mean my my kids one of my kids has an ipad pro or at least you know and you know give it a few years and and it'll probably run on most ipads that are available then you know even though right now you know the ipad pro is so like absurdly expensive i don't think a lot of people not not just kids i don't think a lot of people period buy the ipad pro now i don't know
John:
I mean, it is still limited, but it is less limited than convincing your parents to buy you a $300 software application, right?
John:
Whereas a $5 a month thing, you could swing that on your own income of a job, right?
John:
So I think that is important for Final Cut because it is not the leader in its industry.
John:
And so if you can get a new generation to try it out, like you see the people who are like, we know, those are the people who...
John:
Existing Final Cut users probably have some big, fancy, beefy Mac that they do their work on.
John:
It's some kid somewhere who's going to, you know, try this out for $5 a month and learn Final Cut.
John:
Or, like, they'll take a course in video editing and the course will give everybody iPads or something.
John:
You know, like...
John:
Not that I'm saying that's the killer app for this thing.
John:
I just think it's an additional upside to consider when thinking about who is going to use this.
John:
And as for the pro people who are saying, like, I think it's good that it exists, yeah, they might be like, oh, if I'm on the go with my iPad, I can try it or whatever.
John:
But I did immediately when I saw this, I thought about...
John:
All the fancy YouTubers, essentially, that I'm aware of that ever talk about their work, it's like, well, here's my SAN with my giant stack of storage that costs more than all of your cars combined, and here's how I connect to it with 10 gig Ethernet.
John:
It's like...
John:
the ipad does not have that kind of connectivity and for the idea of like oh i'm going to take it with me and do some editing on the plane how are you going to get the media files onto the ipad i guess it has thunderbolt but then you have to find some way to connect your ipad with a thunderbolt cable to your 10 gig san no
Marco:
No, that whole story, that's why I don't think the lack of round tripping is that big of a deal with the Mac version, because I don't think there's a lot of people who are going to be trying to round trip stuff between their iPad and their Mac who are doing Final Cut Pro projects.
John:
It's not sending the data back and forth that's bad.
John:
It's the fact that they're a different format, like that they're not even compatible.
John:
True.
Marco:
But it's also sending the data off.
Marco:
The ways to send large amounts of data to and from iOS devices are not great.
Marco:
The iPad's better than the phone in that regard, but it's not that much better.
Marco:
You have speed issues.
Marco:
You have interface issues.
Marco:
I don't think there's going to be a large market of people who are using these apps as satellites with the Mac apps trying to work concurrently on the same projects.
Marco:
I don't see that happening.
Marco:
I see this as the new market.
Marco:
So like what you're saying, this is going to be people who don't have the Mac apps, maybe don't even have a Mac, who want to try these out or want to amp up their ability to do stuff on their iPads.
Marco:
That's going to be what this is for.
Marco:
I can't see professional video editors taking an iPad on a plane and, oh, I'll just pop the project over here.
Marco:
No, that's not going to be a market.
John:
so that's why that's why i kind of miss out not apple not having this in the keynote because if it was in the keynote i think they would like try to show scenarios like this and i think they might explain like one of the things i wonder again i'm not a video editor but i know back in the bad old days uh proxy editing was essentially you couldn't edit and mess with in real time like the full resolution stuff and part of the revolution of uh you know
John:
oh, hardware gets better.
John:
Now you've got more memory and dedicated encoders.
John:
Like you can do non-proxy workflows where you're actually working with your own real video files and you can scrub them in real time and see the effects applied in real time and not wait for things to render.
John:
And it's like, wow, great.
John:
Look at all the new technology we have.
John:
But going to the iPad version, it's not like the iPad doesn't have that power.
John:
Again, M1 iPad is fantastically more powerful than most of the machines that have ever run Final Cut, right?
John:
But the iPad itself is so anemic in terms of IO that I do wonder if it uses a proxy workflow, not for computation or rendering reasons, but purely so they don't have to...
John:
find a way to bring the full-fledged media files to and from your ipad right that maybe it will you know there's some kind of oh well when you when you bring a project onto your ipad it will you know from from these full media files it will only work with the proxies just so you need to reduce bandwidth but that doesn't make sense either because if you can't bring them from the mac onto there they have to be created on the ipad to begin with so i don't know that i would have liked to see an apple try to i know there was that video they released showing people messing with it but they didn't really talk about
John:
you know here's what we think you could do you could you know they showed like you can use the ipad to record video with the amazing ipad camera and and it records in pro res which is great okay and now we're taking you know video of this guy skateboarding and then we get edited right here in real final cut and
John:
Is that really a common scenario?
John:
Again, for the kid in the bedroom, yes, sure, because it's an all-in-one amazing video editing station.
John:
But for anybody doing, quote-unquote, real video work, even YouTubers probably aren't if they can avoid it, unless it's they're just starting out, you know, capturing video with the iPad camera.
John:
So that leaves you with the question, how do I get the video onto this thing?
John:
How do I get the video off?
John:
Did I put the full video on it?
John:
Do I just do a proxy workflow and then have the real videos elsewhere?
John:
And how does it all come together?
John:
I don't know the answers to all those questions, but it just...
John:
I'm still stuck on the fact that it's a different format because I don't like thinking that this is the lesser final cut.
John:
I would want it to be full real final cut that works on full real final cut projects and whatever the limitations are caused by a small amount of RAM or whatever, throw up a dialogue and say, oh, on this project, because it's an 8K project and we just can't deal with them here.
John:
We can open the file and we can let you scrub through it, but I can't actually do the work because I don't have enough RAM, so put it back to your Mac.
John:
But it being a separate format,
John:
You know, I'm still crossing my fingers that this is just the new Final Cut format and the Mac version will catch up, but Apple hasn't said anything one way or the other, so it makes me think that this is, you know, Final Cut Pro Jr.
Marco:
Some of that I think is unavoidable, just because when you look at, you know, a lot of the stuff you were just mentioning, when you look at the actual needs of Final Cut Pro users in the field today...
Marco:
they scale up dramatically past what the iPad could do or what you could easily get into or onto or off of the iPad.
Marco:
So they can't really do everything that Final Cut Pro does on the Mac on the iPad.
Marco:
So there had to be some omissions and cuts and everything.
Marco:
The file format stuff, you know, that could be for other reasons.
Marco:
You know, it could be that this is the future format of Final Cut.
Marco:
It
John:
just has stuff that the ipad can't do well or won't handle well um you know so there's all sorts of plausible you know reasons for that it would be easier to make technical arguments if max didn't literally have m1 soc and like this is not an ipad soc it is a mac the m does not stand for ipad it's like it's like so you know i was like like again the only thing that it really has against it is
John:
just lower ram and i don't even know off the top of my head some of the the big ipads might even have eight and you can find final cut in eight which is you know not great but anyway apple didn't explain um so this this is an area to watch in the coming years assuming this application continues to be a thing ipads will get more powerful and eventually we'll be at the point where like the cheapest ipad pro you can get is more powerful than you know the macs that are running you know the minimum spec mac that you can run real final cut on today
Casey:
So in the interest of being completionists, we should probably have a little bit about Logic Pro specifically.
Casey:
Creators can make precision edits and draw detailed track automation with the Apple Pencil and connect a smart keyboard folio or magic keyboard to utilize key commands that speed up production.
Casey:
That's also true of Final Cut Pro.
Casey:
Logic Pro for iPad supports round-trip capabilities.
Casey:
Hey-oh!
Casey:
Making it easy to move projects between Logic Pro for Mac and the iPad.
Casey:
But then Jason Snell clarifies, except there's just one thing.
Casey:
Many logic users also use third party audio plugins.
Casey:
You may not know it, but iPadOS supports Apple's audio unit plugin format and has for a while now.
Casey:
But the only catch is that the maker of the plugins you rely on must make iPad versions available or your quote unquote round trip logic project really won't be.
Casey:
Some pro filter makers like FabFilter support the iPad.
Casey:
Others like Isotope seem to have not even heard of the iPad.
Casey:
Sad trombone.
Casey:
Sorry, Marco.
Casey:
Your mileage may vary.
Casey:
So full marks for supporting round trip in principle, but a bit of a bummer.
Casey:
And I guess it's at least partially beyond Apple's control, but a bit of a bummer that the plug-in story is lacking at this moment.
Marco:
Well, and this, I mean, again, like this is that this particular thing, you know, I actually don't use iZotope's plugins.
Marco:
I use the iZotope editor app because I find the use of plugins adds a lot of latency and burden to the actual logic editing process.
Marco:
So I just, I pre-process the files in iZotope's own app and then I import them into logic.
Marco:
But like...
Marco:
Again, trying to figure out how to do that kind of stuff on an iPad.
Marco:
Think about all the limitations that iPadOS will fight me on this.
Marco:
So first of all, my podcasting workflow.
Marco:
I use Audio Hijack Pro to record and do a bunch of other stuff.
Marco:
It broadcasts the live stream.
Marco:
It records a different backup format.
Marco:
It splits the format into different parts.
Marco:
I'm also recording the contents of our Zoom call.
Marco:
This is all stuff you literally cannot do on iPadOS.
Marco:
And then I take those files.
Marco:
I upload one by dragging and dropping to our CMS.
Marco:
You can do that on iPadOS.
Marco:
It's clunky, but you can do it.
Marco:
And then I run a command line script that I wrote, a bash script.
Casey:
What's that?
Casey:
What's that?
Casey:
I don't know.
Casey:
I don't understand.
Marco:
Oh, because meanwhile, in the background, my Dropbox app, which is actually Maestral, but my Dropbox client was running and got the files that the two of you put in the shared folder that we have.
Marco:
I run a shell script that I wrote in Bash that takes those files, puts them in the right directory that I actually run some stuff on, runs FFmpeg to convert a couple things between formats and sample rates and whatever else, then runs a custom app I wrote to line up the tracks...
Marco:
That I've never released and I'm probably not going to please don't ask it's it's sloppy you don't want it but anyway so it automatically syncs up the tracks runs them through my voice boost command line utility that I also haven't released that applies EQ and volume normalization to each of our voices based on a profile I've created for each of us.
Marco:
Then it gives me those WAV files that I can either import into iZotope if I need to do any kind of de-reverb, or in most cases I don't, so I just import them directly into Logic.
Marco:
Those files, by the way, are about a gig each, so a gig per person per ATP episode.
Marco:
Now imagine the process of trying to do that kind of workflow on an iPad, because on my Mac, it's running one shell script that I wrote eight years ago, and I've been reusing this entire time.
Marco:
You can do some of that with shortcuts.
Marco:
Some of those apps exist on the iPad, but it's a way, way smaller ecosystem, and the process of dealing with all these different files and different processes is much more clunky and much more cumbersome on an iPadOS.
Marco:
Some of these things aren't possible at all, like the application that records the output of another application that doesn't cooperate with it normally.
Marco:
So...
Marco:
So again, I think these apps will be good for people who have, first of all, very different needs than me.
Marco:
Obviously, Logic is not made for podcasting.
Marco:
Again, it never stops reminding me of that when I'm using it.
Marco:
But these are apps that people who use these have complicated workflows sometimes and complicated needs that iPadOS is going to keep getting in their way.
Marco:
So on one hand, I'm really glad that Apple did this.
Marco:
I was not expecting this.
Marco:
This came out of nowhere for me.
Marco:
It shows that this is a large amount of software effort that they put in here.
Marco:
And Apple does not put in large amounts of software effort for their applications these days.
Marco:
Like, when's the last time Apple made a really great first-party app?
Marco:
Not OS, not platform, app.
Marco:
They're few and far between these days.
Marco:
And so to do this kind of effort is unexpected and very, very good to see.
Marco:
That being said, it also does highlight for a lot of people and will highlight for a lot of people who try to use it the limitations of iPadOS for doing this kind of work where you're having to integrate stuff from a lot of different apps.
Marco:
You're having to pull in different files and different formats and use different tools to operate on them.
Marco:
That's not the strength of iPadOS at all.
Marco:
It fights you at every turn.
Marco:
So hopefully this is one part of a larger effort to maybe make iPadOS better at dealing with those things.
Marco:
And I know that's a tall order because we've seen over time it's very difficult to add power to iPadOS without making it confusing for the people who want it to be simple.
Marco:
And so that's going to be something that hopefully we'll see more of at WBDC.
Marco:
Maybe we'll see some kind of direction for iPadOS that is more than what it seemed like over the last year or so, which is basically half abandoned.
John:
I would rephrase that, though.
John:
You said we've seen that it is difficult to add more functionality without making it harder for the casual user.
John:
Mm-hmm.
John:
I think Apple has been unable to do that.
John:
I don't actually think it's difficult.
John:
What Apple has always been trying to do is to sort of strike a balance, to have their cake and eat it too.
John:
We want to add pro-level features, but we want to sort of make them accessible to casual users as well, which is an admirable goal, but they've been failing at that goal.
John:
If you want to add...
John:
pro-level features and not trip up casual people, it's real easy to hide them.
John:
It's real easy to have them all turned off by default, all completely invisible.
John:
That's not ideal.
John:
You don't want to do that.
John:
You don't want there to be this hidden underbelly or whatever, but you can do that.
John:
An example of that is the Unix stuff on macOS.
John:
it's there but if the casual user never even seems to know the terminal application exists it's in the utilities folder it's not even an application so they never even need to see it but so much functionality is under there for the advanced users who know where it is but it does not shove its head in you know shove you know it doesn't rear its head it's not in your face you don't have to know it exists at all to be a casual mac user
John:
Apple could have done stuff like that on iPadOS.
John:
They could have, you know, made it possible to have multiple audio streams and more generic file, complete file system access and all sorts of other things like, you know, a terminal, a command line, like all that stuff is under there and could be there in a way that does not impair the casual user.
John:
It's just that every time Apple has tried to do that, they've tried to not...
John:
buried away they've tried to integrate it to give an example of when they've succeeded cursor support an ipad os that is a more advanced feature that they surfaced in a way that does not interfere with casual users but also provides casual users with additional functionality it meets them where they're at you don't have to know every single detail of all the fancy stuff or whatever it is very ipad like it's friendly and you can sort of gradually work your way up to it an example where they've not done that is
John:
multitasking where they keep trying to have new paradigms and things to do and they're they have impaired the casual use and they've also been non-satisfactory so yeah the way i would phrase it is apple has thus far proven unwilling to just do the simple thing which is to hide all the advanced features away and and i you know like i said that's that's admirable i admire them for not
John:
taking the lousy way out which is ah we'll just hide it all under our terminal and you gotta do all this stuff from the command line but practically speaking it means that the stuff you were talking about just plain isn't possible for anyone like every time i see a 700 step shortcut it's like it's impressive in the way the house of cards is impressive but it's like come on like as as clunky as your shell script might be for someone who knows programming it's so much more tractable than a shortcut that scrolls for 17 pages
John:
yeah yeah also it's a really short show like it sounds like it's really complicated oh my god i run my files through a shell script it's really not that it's like it's like 20 lines it's not much if you did that in shortcuts it would not be 20 lines no definitely not nope it wouldn't be possible first of all as you pointed out like literally not possible due to sandboxing and restrictions and stuff like that but even if it was possible it would be so much more complicated yeah
Marco:
So anyway, I think this is this is overall a very promising story.
Marco:
Like, again, this shows a level of investment in the iPad platform that, frankly, I don't think anybody was expecting Apple to be doing right now.
Marco:
Like, I think everybody who uses the iPad to get pro stuff done, if there's any of those people left, they had kind of felt like Apple's, you know, Apple has one foot at the door with this platform like for pro use.
Marco:
I don't know a lot of people who are happily using iPads for pro use in this past year.
Marco:
I think Stage Manager really threw everyone for a loop, and the kind of built-up frustrations over time and Apple's lack of progress in this area, I think, turned a lot of people off and sent a lot of people back to or to the Mac to do pro-level work.
Marco:
And I don't know that this is enough to change that.
Marco:
Obviously, for people with certain needs, maybe it will be, but...
Marco:
It's a really good first step to show like, no, they're not giving up on the idea of a pro iPad workflow platform.
Marco:
And, you know, I don't know if it's going to work, but I'm really happy that they're doing it.
Marco:
I think this is healthy for them as a user of Logic every week for my work.
Marco:
I'm a little concerned that they're going to axe the Mac version and make this the new version via Catalyst.
Marco:
And maybe it will be even less suited to podcast work than it currently is for some reason.
Marco:
I don't know yet.
Marco:
Time will tell.
Marco:
But as just an Apple watcher in general, this is a cool surprise.
Marco:
Again, it shows investment that I wasn't expecting in the platforms and in their applications, frankly.
Marco:
So...
Marco:
I'm tentatively optimistic.
Marco:
I think it's a pretty cool thing overall.
Marco:
Hopefully, it doesn't bite anybody in the butt in the future in terms of what these apps are on the Mac, and we'll see what happens with the iPad.
John:
I think I would like a little bit more bottom-up on this.
John:
This is top-down stuff.
John:
Let's make the Pro applications for the iPad a similar top-down type of thing.
John:
We were always wondering about, asking for, speculating about Xcode for the iPad.
John:
Instead, we got Playgrounds, right?
John:
It
John:
That's top-down stuff.
John:
It's like here is the stuff that the user interacts with.
John:
We're bringing pro-level functionality to the iPad.
John:
You need bottom-up stuff as well, and they've added a little bit of that.
John:
They added virtual memory recently to the iPads that are capable of it.
John:
That's the type of bottom-up stuff that you need to support the top-down things, but there's a lot of bottom-up stuff that is lagging behind the top-down stuff.
John:
uh you know logic uh and final cut could surely benefit from a more sophisticated audio video underlying system in terms of interaction between other applications you know like final cut has the plug-in system that it uses with audio units uh not final cut uh logic does uh final cut i think has some integration with if not third-party stuff then like apple's compressor app is that still a thing apple's compressor app is a separate app
Marco:
It is, and I own it.
Marco:
I don't know if it will continue to be a thing.
Marco:
It's basically Apple's version of FFmpeg.
John:
Yeah, but that type of coordination is more difficult on iPadOS, you know, or even just like, you know, we can't do recording.
John:
The audio subsystem, the fact that Audio Hijack, nothing like Audio Hijack exists on the iPad and can't exist, and
John:
iPadOS itself seems to have limitations in terms of controlling multiple audio streams and multiple applications, let alone hijacking them or coordinating between them.
John:
That's the lower level stuff that lets the higher level applications actually achieve parity with the Mac ones, right?
John:
Because the Mac can do all those things.
John:
And now, you know, Apple can cheat like Apple's applications can use private APIs.
John:
Apple can put things in the OS only for them.
John:
Again, without an Apple presentation about the technical underpinnings, we don't know how much of that stuff they did.
John:
How much bottom up stuff did they have to do in 16.4 to make these two applications possible?
John:
And can that stuff benefit third party applications on iPad OS?
John:
They feel like now they're a little bit top heavy.
John:
And on that front, it's like it's great that they did these for the iPad, but it's all about the follow through.
John:
Right.
John:
You know, are they going to continue to update them?
John:
Is there is there some kind of target they need to hit in terms of usage to keep these teams together?
John:
Are these teams going to go off and do something else?
John:
Right.
John:
Are they really dedicated to this?
John:
In those ways, it would actually benefit the longevity of this software on both platforms for these to be the secret future Mac versions.
John:
Because then at least they have just, you know, everybody's working on the same project and they can try to improve it again, kind of like they did when they made the new version of iMovie, which had...
John:
which did such a bad job of covering the feature set of the previous version that Apple continued to ship the previous version.
John:
I forget what the numbers were.
John:
It was like iMovie 8 or something.
John:
It was kind of embarrassing, but Apple believed that the underpinnings of the new version of iMovie were important enough to get out there, and eventually the underpinnings of the new version of iMovie became the only version of iMovie, and I think they used...
John:
a lot of that technology and foundation for the future version of final cut which also was a disaster in its own way because it took away the features of the old version using you know hopefully apple learns from this but i i do worry about them spending what must have been years or you know however long to make these seemingly very good versions of mac applications on the ipad
John:
and then just kind of like forgetting about i'm going oh we tried that and it wasn't that great so never mind like it's like we talked about this with the pro max you know oh are they really uh you know dedicated to the mac pro are they going are they behind this machine are they going to update it pro software is the same thing they make these things they seem like they're really great they seem to support them and then some of them just kind of
John:
fade away or just like you know live on in undead form or get cancelled unceremoniously that's the life of the quote unquote pro user of Apple stuff both on the hardware and the software front so fingers crossed yeah and I think ultimately though like
Marco:
The odds of these becoming the new Mac apps also I think is so high in part because of that factor that Apple does not multitask well and Apple does not like to repeat work between platforms.
Marco:
I think we've seen over the last several years –
Marco:
Whenever Apple has a chance to unify something between macOS and iOS, they'll take it.
Marco:
And they don't want to keep making a Mac app if they have an iPad, an iOS app that they can just port over to the Mac and make it one unified app.
Marco:
And frankly, I mean, while I wish this was different, I also can't blame them.
Marco:
I mean, I don't like writing a Mac app either.
Marco:
Like I'm currently like trying to do everything in Swift UI.
Marco:
I'm like, you know, having to port everything over between, you know, all the UI kit stuff and all the NS everything stuff is terrible.
Marco:
And it feels like wasted effort.
Marco:
And so anyway, I think what we've seen from Apple is that they will unify when possible.
Marco:
And ultimately, as much as the transition kind of hurts in the meantime,
Marco:
you know, look at messages on the Mac.
Marco:
It was pretty rough at the beginning when it, when it became a catalyst app, but now it is a better app than the old, you know, app kit native version of messages, because now it has feature parity with the iOS version, which we were all using anyway.
Marco:
And this is a little bit different in the sense that these apps were the, you know, these pro apps are Mac apps first.
Marco:
And so, you know, we're not crying for feature parity on the Mac.
Marco:
However,
Marco:
This is going to allow Apple to, after maybe a bumpy intermediate period, to update them more often.
Marco:
If they can justify the effort to say, we're going to have one version of these apps that runs on all of our major platforms, that will help them justify having engineering time on them.
Marco:
And...
Marco:
while it would be great if apple could use their vast resources to work on both like in parallel tracks we know by this point we know apple will have to know they won't do that like they will they will half-ass one of them at least and if you're lucky it'll be just one
Marco:
if not both and so if they have less of a surface area that they have to work on odds are better they will keep it updated and keep moving forward so this is probably going to be the future of these apps in the mac at some point i don't know when they'll make the changeover probably soon and i think at that point we will have round tripping between them and we'll and the pros will all complain about all the stuff they're losing in the transition and
Marco:
It'll be bumpy for a while and we'll get through it.
Marco:
And at the end of the day, we'll have apps that are eventually good and updated.
John:
Can't wait for Final Cut Pro for watchOS.
Marco:
We are sponsored this week by Backblaze, unlimited computer backup for Macs, PCs, and businesses for just $7 a month.
Marco:
Backblaze is a wonderful cloud backup service.
Marco:
I have been using them for many, many years now.
Marco:
I so strongly recommend that everyone should have cloud backup.
Marco:
It's automatic.
Marco:
It runs in the background all the time.
Marco:
You don't even notice it running.
Marco:
You don't have to think about running it.
Marco:
You don't have to tell it to run.
Marco:
You don't have to have a certain drive connected to your computer or be in a certain location.
Marco:
It's just always running and it protects you from so many different hazards because it's not just like, you know, something on your desk sitting there in your office.
Marco:
So you don't have to worry about like fire, flood, theft, power surges, all that stuff.
Marco:
It's just cloud backup.
Marco:
It's automatic.
Marco:
It is wonderful.
Marco:
Backblaze has restored over 55 billion files for their customers, and they have so many ways you can restore files if you need to.
Marco:
So first of all, even if you have a data loss, suppose you're just like away from your home computer, you can access your files on their phone app or using a web browser.
Marco:
You can get your files right there wherever you are.
Marco:
So that's great, even if you haven't even had a loss.
Marco:
But suppose you've had a loss.
Marco:
You want to do a big restore.
Marco:
You can do it on the web interface.
Marco:
You can do it in the app.
Marco:
You can even have them send you a hard drive.
Marco:
If it's like a lot of data, you don't want to download over the internet.
Marco:
They can mail you a hard drive.
Marco:
You send it back within 30 days, you get a full refund on the cost of the drive.
Marco:
They also have now, you know, if you have concerns about maybe accidental deletion for an extra $2 a month, you can increase your retention history up to a year.
Marco:
So they have great features at Backblaze.
Marco:
I love cloud backup and Backblaze is by far the best one I've ever used.
Marco:
So don't be that person who forgot to back up their important files.
Marco:
Sign up for a 15-day free trial today with no credit card required at backblaze.com slash ATP.
Marco:
Start right now.
Marco:
Free trial once again.
Marco:
No credit card required.
Marco:
Go start.
Marco:
Back up your files.
Marco:
Backblaze.com slash ATP.
Marco:
By far the best cloud backup service I've used, and I so strongly recommend it.
Marco:
Please go use Backblaze.
Marco:
Save yourself.
Marco:
Backblaze.com slash ATP.
Marco:
Thank you so much to Backblaze for sponsoring our show.
Casey:
All right, so in the show notes for two or three weeks now, we've had a heading, Mastodon, Blue Sky, Twitter, etc.
Casey:
And I guess this was cued by an Ask ATP question from Stephen Wood.
Casey:
How are you guys finding Mastodon engagement compared to Twitter?
Casey:
I've stayed on Twitter but missed some of the people that have moved away, including yourselves.
Casey:
Just curious if you're enjoying it more.
Casey:
And it seemed to me that, John, you had thoughts that you wanted to share.
Casey:
Would you like to share some thoughts?
John:
Yeah.
John:
So Blue Sky, I believe we talked about it on this show ages and ages ago when I was talking about it as a...
John:
I think maybe when we were first talking about Mastodon, I said, well, there's this Project Blue Sky that Twitter started that is trying to make a decentralized, you know, Twitter-like service.
John:
And they're working on their own protocol and it's supposed to be all open and so on and so forth.
John:
And I don't know if that's going to come to anything.
John:
But in the meantime, we've got Mastodon, right?
John:
um i had signed up for the blue sky whatever it was like hey sign up here if you want to appear when we actually do anything i signed up for that you know months and months ago maybe years ago whenever the project first came out eventually my number did come up and they said hey blue sky is ready for you to check it out so i signed up for it this was months ago and uh got onto it uh and used the app on ios and i was like well this you know
John:
Here it is.
John:
That's kind of like Twitter.
John:
Uh, and it's on my phone and the app is not great and whatever.
John:
And I just ignored it for a while.
John:
Um, and mass.
John:
And of course we've talked about many past episodes that we were all on it.
John:
We're all doing sorts of all sorts of stuff.
John:
We've talked about the various applications on Twitter continues to, in its, uh, slow decline in functionality and enjoyment.
John:
Most of us are mostly off of it.
John:
Some people are still there.
John:
Um,
John:
But recently, in recent weeks, Blue Sky has seen, you know, a surge in awareness, let's say.
John:
I'm not saying a surge in popularity because Blue Sky is still invite only.
John:
And so the population of Blue Sky is being kept artificially limited by the number of invites, which is very small in the tens of thousands, I believe, as compared to the millions that are on Mastodon and the many, many more millions that are on Twitter.
John:
But it is in the public consciousness.
John:
And so I think it is worth talking about how these different platforms are shaping up.
John:
And my main thought on this topic is that the way these platform services, protocols, so on and so forth...
John:
are, you know, are developing has almost nothing to do with any of the technology on either one of them.
John:
The technology itself is interesting.
John:
We can talk about activity pub versus AT protocol and versus Twitter thing or whatever.
John:
But I really feel like that is not the story.
John:
And I think it is apt for social networks to not be driven by technology.
John:
It is entirely driven by social aspects.
John:
Who is going to each of these services?
John:
Why and what forces are moving them there?
John:
Because kind of like any empty building, the services are defined by who shows up.
John:
Who shows up?
John:
Who is there?
John:
What do they want to do?
John:
What do they do when they're there?
John:
And that really shapes...
John:
the services.
John:
So despite the fact that the, all the activity pub people in the blue sky, people are arguing back and forth about their technology stacks and stuff like that.
John:
That is not the story here.
John:
The story is entirely about the people that arrive.
John:
And in particular blue sky, you know, having been spawned off from Twitter, um,
John:
I believe it was started by Jack Dorsey, Twitter.
John:
It was maybe his baby or maybe the CTO who then became CEO's baby.
John:
And it got spun off of Twitter.
John:
So now it is not owned by them, I believe.
John:
But anyway, Blue Sky was backed by money from rich people.
John:
let's put it that way right i don't know if it's a venture capital thing or whatever but like jack dorsey's rich person they've got not a lot of money but millions of dollars right behind them to develop this protocol to hire a bunch of people who worked for a while with nothing to show for it who are still working on this protocol and have shipped this sort of prototype application there is no business model there is no money coming into this this is entirely a cost center that millions of dollars are being funneled into at this point right
John:
Mastodon is an open source project started by one person.
John:
So the sort of pedigree and origin of Mastodon versus Bluesty could not be more different.
John:
And I think that difference in origin actually does have a lot to do with who has shown up.
John:
Um, blue sky being the thing that was started by millionaires with millions of dollars poured into it has ended up attracting people who did not end up, uh, on Mastodon because now not because there's anything wrong with this.
John:
This is not a value judgment, but I'm just going to say this as, as what I believe to be a fact, rich people know other rich people.
John:
Like the circles that rich and powerful people travel in, they touch each other, right?
John:
You are more likely to know a senator if you are a rich person.
John:
This is just the way it is.
John:
And if you're a senator, you will know way more rich people than you will if you're not a senator, let's say.
John:
Same thing with celebrities, rich people, powerful people.
John:
Not that they're all one big happy family and they all know each other, but you will have occasion to be fewer degrees separated from them.
John:
The same way in a tech nerd circle that I may not know people who are like Rust programmers for Android or something, but they are way closer to me in my Apple Mac circle than they are to someone who is into rock climbing.
John:
Because just the social networking, like who knows who?
John:
I know this person knows it.
John:
How many degrees away are you from Kevin Bacon or whatever?
John:
Like literal Kevin Bacon is way closer to the rich people who funded Blue Sky than he is to most of the people who are on Mastodon.
John:
And I think not that that is the one and only explanation for why celebrities are on Blue Sky and not on Mastodon, but it has a surprisingly large amount to do with it.
John:
And I say that because having used both the services for almost their entire existence,
John:
Practically speaking, Mastodon has more people, has better applications, has more features.
John:
And despite the fact that they're arguing about, oh, but Mastodon makes you pick a server or whatever.
John:
A, that's not actually true anymore.
John:
Mastodon defaults to one application.
John:
B, Blue Sky gives you the exact same option.
John:
It says, do you want Blue Sky or some other thing?
John:
And there is no other thing you can pick right now.
John:
But that is not the difference.
John:
The difference isn't that your favorite senator tried to sign up for Mastodon and got scared away by the thing where it asked you to pick a server.
John:
That did not happen.
John:
Your senator did not ever try Mastodon.
John:
Your senator had never heard of Mastodon.
John:
Or if they did, they heard it once and ignored it.
John:
But when enough of their rich, powerful friends mentioned Blue Sky, that made them... The same way you're going to go try it if you hear something from a friend of a friend than if you just see it randomly on the internet.
John:
Like, oh, maybe that's something I should check out.
John:
If you're thinking about checking out Blue Sky, think about where you heard it from.
John:
How many degrees away from yourself did you hear about Blue Sky?
John:
And what made you check it out?
John:
It's because...
John:
You trust those two or three connections to say, maybe that's something that I might be interested in because a friend of a friend of a friend says, hey, Blue Sky, whatever.
John:
Maybe you want to check it out because you heard your favorite celebrities on Blue Sky.
John:
That is the degrees of separation.
John:
I am a fan of Tom Cruise.
John:
Tom Cruise is on Blue Sky.
John:
I don't know if he actually is or whatever.
John:
nothing to do with the actual services.
John:
Blue Sky is worse than Mastodon right now because it's younger.
John:
It is younger.
John:
They're just working on it.
John:
The protocol's not done.
John:
The client is bad.
John:
The client's not done.
John:
Like, it is very young compared to Mastodon.
John:
Mastodon has been around for literally years.
John:
Even though it's only had one person working on it, they've got a huge head start.
John:
But...
John:
There's the X factor.
John:
It's not an X factor.
John:
Celebrities are on Blue Sky.
John:
Celebrities are on Twitter.
John:
Fewer, not none, but fewer celebrities are on Mastodon.
John:
And right now, in the very, very early days of Mastodon, that is defining the big difference between these platforms.
John:
And I've seen a lot of people say, well, Blue Sky is more fun and Blue Sky is just better in this way.
John:
It's like...
John:
That may well be true, but I think it's because of the people that are on Blue Sky.
John:
It has nothing to do with the app, which I hate with a fiery passion.
John:
It has nothing to do with the protocol, which actually is very interesting and cool and has some advantages over the Mastodon protocol.
John:
And it's all to do with the people that are there.
John:
That's the game in social networking.
John:
It's network effects.
John:
It's who's there.
John:
You could call it marketing or whatever, but honestly, I don't think either Mastodon or Blue Sky have some sort of master marketing plan that is causing this to happen.
John:
It's happening more or less organically because of the seed of where these things came from, what their pedigree is, and who knows who and whatever.
John:
So that doesn't mean it's set in stone forever.
John:
Things can change real fast.
John:
It's early days in both of these services now.
John:
But if you're wondering what the difference is, technically speaking...
John:
That's not the answer.
John:
Practically speaking is who's there and do I want to be there?
John:
My favorite celebrity and or government person and or whatever is on the service and I want to be in there because I want to see their tweets.
John:
The big fun threads, reverends posting pictures of their butts and the hell thread and all that you're hearing about that because powerful people, people with big audiences.
John:
celebrities, they're all there.
John:
When AOC is posting funny things off the cuff on Blue Sky, it's because there's only, you know, 50,000 people there and she feels more comfortable.
John:
And why is she even there?
John:
Because, you know, connection to connection to connection.
John:
I really, what I'm rooting for right now is I really hope the Blue Sky apps will get better.
John:
There are third-party Blue Sky apps, but they're not any better in my experience than the first-party one.
John:
None of them preserve my timeline position, which is a deadly sin for me.
John:
But boy, if you're currently on Mastodon enjoying the wide selection of really good applications, including the one really good one that I use, Ivory, appreciate what you have.
John:
But you may be sad that your favorite celebrity is not there.
Casey:
I heard sometime in the last week or so.
Casey:
Somebody describe the two services approximately thusly.
Casey:
They said, if you were a Twitter person and then you decided to leave Twitter, but you really, you like Twitter, you still enjoy Twitter, then you're going to probably end up on Blue Sky because Blue Sky looks like Twitter, feels like Twitter.
Casey:
I just got an account in the last two or three days and I'm casually lurking and occasionally replying to things.
Casey:
Blue sky looks, feels, smells, walks, quacks like Twitter or Twitter of, you know, like a year ago.
Casey:
If you were on Twitter and wanted to leave Twitter, but you were kind of sick of Twitter, then Mastodon is for you.
Casey:
And, and I think that obviously there are exceptions and that's not a universal truth, but I think by and large, that's, that rings true for me.
Casey:
And I've been enjoying Mastodon quite a bit.
Casey:
I've been using ivory and it's excellent.
Casey:
I cannot begin to tell you how much I dislike the apps.
Casey:
Just like John had said, the web app for blue sky is not great.
Casey:
The mobile app it, well, I mean the web app and mobile app are both deeply impressive given that it hasn't been that long to my knowledge that they've been in development, but the,
Casey:
They are not great.
Casey:
The whole vibe on Blue Sky is very different than Mastodon.
Casey:
Mastodon's a bunch of nerds.
Casey:
It's good, and it's bad.
Casey:
It's a little of both, but it's a bunch of nerds.
Casey:
Blue Sky is not.
Casey:
Blue Sky is...
Casey:
It seems to me anyway to be a lot of people just kind of kicking the tires and kind of posting for the fun of it.
Casey:
Not necessarily in an angry like evil way like it used to be on Twitter, although I'm sure that's happening too, but more in a haha kind of way, which that probably doesn't seem like a strong distinction, but in my eyes it is.
Casey:
And it's not a bad vibe over at Blue Sky.
Casey:
It's just very, very, very different.
Casey:
And I agree with you, John, that I think it will continue to be very different because regular people seem to be embracing Blue Sky to the speed that they can, given that it's all invite only.
Casey:
whereas the nerds are embracing Mastodon.
Casey:
And I do agree that up until very, very recently, the onboarding process for Mastodon was gross.
Casey:
And I understand why it was the way it was.
Casey:
I get the decisions that were made to land there, but it was tough.
Casey:
It was gross.
John:
I wouldn't say it was gross, but part of it, it was derived from the fact that Mastodon is many years old.
John:
Because Mastodon is already decentralized.
John:
And so when you have a service that is already decentralized, you have to present that decentralization in some way.
John:
Otherwise, it's not really decentralized.
John:
Blue Sky doesn't have that problem.
John:
It's not actually yet decentralized, right?
John:
In the beginning, Mastodon wasn't decentralized either.
John:
When that guy put up his first server, there was only one because he was the guy who just made it.
John:
And there was no, you know, and so, but in, you know, they're like, look, MassDawn is many years old.
John:
We have a rich tapestry of instances for you to choose from because we're many years old.
John:
We're literally decentralized.
John:
Of course, that has to be in the application.
John:
So it's like a competitive advantage for Blue Sky to say, we only have one thing for you to choose from.
John:
But like I said, Blue Sky still puts up the screen that says, please choose your instance.
John:
And the choices are the one that exists and the one that exists.
John:
please enter like other underscore underscore and like it's just like and there is no other as far as i know there's literally nothing else but the ui is still there for it if we could fast forward seven years and blue sky still exists and it actually is decentralized they're going to have the exact same problem that mastodon has which is oh blue sky is decentralized and there are 27 instances which one do you want to pick will default to this one but you get to pick from other ones and so i you know i don't
John:
I don't buy that argument at all, even in the sort of like hurdle type thing, because I feel like if those same people who came to Blue Sky and are all having fun in the big threads, if those people all showed up on Mastodon, they would be having more fun because they'd be using Ivory, which is a way better client than...
John:
And they'd be posting all the same things.
John:
And because it's so few people now, it's not like all these people... These are the people who could, don't, but could survive without the algorithmic timeline.
John:
Mastodon doesn't have a big algorithmic timeline thing.
John:
Blue Sky has one bad algorithmic timeline called What's Hot that keeps changing all the time.
John:
But the numbers are so small that if all these people showed up on Mastodon, they'd be having all the same amounts of fun.
John:
The only thing they might get derailed complaining about is the lack of...
John:
quote tweets or whatever but like it's so new on blue sky it's like hey everybody check out this new thing and the reason i know this is because i remember hive do you remember hive this is the thing from like a few months ago that was done by like two kids or something yeah two million people signed up for it in like two days all right again blue sky has like 50 60 000 or something two million people signed up for hive you know what hive was like it was like the blue sky health threat
John:
It was a bunch of people from a specific community and the celebrities from the game were there and they were all posting and having fun and like, woo, isn't this a fun service?
John:
And then, of course, it all collapsed because it was run by two people or whatever, right?
John:
And that was centralized, you know, setting it aside.
John:
People can have this kind of fun if they all show up and it's like a flash mob.
John:
Everyone shows up at a particular location and they have all the fun.
John:
It's a question of whether they'll be able to stay there.
John:
I don't think Blue Sky is obviously probably not going to collapse like Hive did.
John:
But then again, Hive did have way more users for a brief moment before it went down the tubes.
John:
MassDom is just a more mature platform that these people could have come and have fun on.
John:
But then you get into the things that are actually different, as in what does MassDom want to be?
John:
What does Blue Sky want to be?
John:
they do have different aims there in terms of, you know, Blue Sky is big on, they do want to have different pluggable algorithms and pluggable moderation systems, things that are not sort of in the goal set of what Mastodon is doing.
John:
Blue Sky wants to be decentralized, but isn't,
John:
Blue Sky hasn't figured out their protocol to the degree that ActivityPub has.
John:
ActivityPub is an open, documented protocol supported by, you know, W3C or whatever.
John:
Blue Sky doesn't even have that protocol done yet, right?
John:
So these are two things that are in different stages of development.
John:
And the vibe is different on them because they're just doing different things.
John:
They're different ages.
John:
They're different stages.
John:
They're different populations of people.
John:
They're very, very different.
John:
But in the end, I think both of them do want to be like the best of Twitter.
John:
Like Marco was talking about when he finally came on board Mastodon, once he started using Ivory, which is essentially Tweetbot for Mastodon, it was like, oh, this is essentially Twitter.
John:
Because Twitter to me looks like Tweetbot.
John:
And now I have essentially Tweetbot for Mastodon.
John:
And I just slide right in like, you know, I love if you love Twitter, you're going to love Ivory on Mastodon.
John:
I think that is a totally valid statement.
John:
you can, we'll eventually be able to make the same statement of Blue Sky.
John:
I think they both want to be like the best Twitter ever was.
John:
They're just at different stages along the path to getting there, and they've taken a few different turns here and there.
Marco:
I mean, I would say, though, the crowd being different, like what Casey said earlier...
Marco:
That's a massive difference in what it's like to use these two services.
Marco:
I mean, you're right.
Marco:
The apps are very different.
Marco:
The Math.on apps are great.
Marco:
The BlueSky app is terrible.
Marco:
But if you'll forgive a quick story, in high school, I was in the drum section of the marching band.
Marco:
And there came a time when...
Marco:
A few of the drummers were asked to ride with the equipment that would go to the away games, but the equipment wouldn't fit on the bus with the rest of the band.
Marco:
It would fit in an empty section in the little half bus that the cheerleaders took.
Marco:
So for about a year, whenever there was an away game, like three of us drummers would ride in the back of the cheerleader bus.
Casey:
That would be so terrifying for me as a high schooler.
Casey:
Oh, my word.
Marco:
Yeah.
Marco:
So this sounds like it would be amazing.
Marco:
Like if you just hear it like, oh, my God, that must that.
Marco:
What a dream.
Marco:
And what it actually is, is kind of terrifying because you're these like three dudes who are completely invisible in this environment.
Marco:
And you think you think, oh, maybe they'll talk to us.
Marco:
No, no.
John:
You got to talk to them, Marco.
John:
You got to go make some friends.
Marco:
Yeah.
Marco:
Well, they spent the time talking to each other and we spent the time embarrassed to say a word.
Marco:
And it was very clear, oh, this is the cool kids up in front of us here.
Marco:
And then there's us.
Marco:
And we are probably better off not saying anything so we don't make asses of ourselves.
Marco:
And so we just didn't.
Marco:
that's kind of how it felt when i got to blue sky because i only got there recently like in like a few days ago and that's kind of how it felt like oh god this is okay first of all this is where all the cool people are not the nerds and believe me i love i love us nerds but it's like oh this is where the cool people from twitter went they didn't go to mastodon
John:
I'm going to say the popular people, not the cool people.
John:
Well, okay, fine.
John:
I'm going to draw that distinction.
Marco:
Okay, fair.
Marco:
This is where the popular people went, all right?
Marco:
And it was very clear.
Marco:
And it was also extremely clear right from the get-go, oh, this is where all the women and people of color went.
Marco:
Because that's something you don't see a lot of on Mastodon.
Marco:
Maybe that's just the circles that I'm in.
Marco:
The thing is with social networks...
Marco:
It's all about who you follow and your experience, your picture of the network is defined by who you have chosen to follow.
Marco:
And so you might have a picture of something like you might think the entire social network is person type X or is missing person type Y. But in reality, you just don't follow them or you do or you follow too many of this person or whatever.
Marco:
So it's hard for me to say with any certainty that this is this is the case.
Marco:
And obviously the numbers are very different.
Marco:
But Blue Sky seems at the moment to be way less white nerdy than white male nerdy, especially than who I have found on Mastodon.
Marco:
Now, again, part of that's my fault.
Marco:
I'm sure it's who I've chosen to follow.
Marco:
I did notice, though, you know, so for like the first couple days when it was only the popular kids, I was afraid to say anything.
Marco:
It's like it was just like being in that cheerleader bus.
Marco:
Like, I'm going to keep my mouth shut because I don't fit in here.
Marco:
Like.
Marco:
I am not qualified to speak in the presence of all these cool people.
Marco:
Excuse me, popular people.
Marco:
And it was exactly that same feeling again.
Marco:
And then what happened was I found a couple of people I knew.
Marco:
Then I started looking through their follower lists and their follower lists and their follower lists.
Marco:
And I found, first of all, a bunch of people who I actually know.
Marco:
And so I followed them.
Marco:
I also found a bunch of new people of much greater diversity than what I've been finding in my crowds on Mastodon.
Marco:
And I kind of found, oh, here's where the nerds are.
Marco:
The cool nerds, still.
Marco:
Excuse me, the popular nerds.
Marco:
But the cool people... The nerds, nonetheless.
Marco:
Like, okay, I'm starting to find my people.
Marco:
They're starting to be there.
Marco:
That's a good sign.
Marco:
And so now I'm kind of making it my own.
Marco:
And the app does suck.
Marco:
And there's not a lot of people there.
Marco:
But...
Marco:
The people who are there, it seems to have a level of appeal and broad appeal that is more broad than what Mastodon has attracted so far.
Marco:
And part of that is the people on Twitter who are getting it.
Marco:
Part of it is the influence of the celebrities and the rich people, as John was saying.
Marco:
Part of that is just that this is where people are going.
Marco:
And it's hard to...
Marco:
It's hard to nail down what gives something traction, what makes something popular or cool socially in different groups of people.
Marco:
It's a hard thing to pin down or control or predict or explain, but there is traction there.
Marco:
And so what I think we are heading towards is...
Marco:
hopefully a future where both of these networks will continue to exist and be healthy.
Marco:
Blue Sky, again, it's super early days.
Marco:
They're going to have a lot of challenges ahead of them, especially once things get messy.
Marco:
You know, right now they're really small and it's invite only.
Marco:
Well, at some point they're going to either die or they're going to get bigger.
Marco:
And when they get bigger, they're going to have bigger problems to deal with.
Marco:
Just like we were saying with Mastodon a few months ago, they're going to have to deal with abuse and Nazis and harassment and racism and all these threats.
Marco:
They're going to have to deal with all the stuff that makes it hard to run social networks and hard to moderate.
Marco:
Jack Dorsey does not have a great track record in that area.
John:
Well, I mean, the protocol has some ideas in that area, which are different than the Mastinine ideas.
John:
But in theory, people might say, oh, they're ignoring the issue.
John:
They're not ignoring it.
John:
They're just way, way farther behind on what they think their path is to dealing with it.
John:
Will their path be successful?
John:
There's reason to doubt, again, based on what they've done in the past.
John:
Maybe they learn from their mistakes.
John:
They have some interesting ideas that have not existed.
John:
been tried in the same way so that's part of what's interesting but when you're invite only 50 000 people you can get away with stuff that you cannot get away with when you're you know multi-instance 10 million people so we'll we'll see how that turns out but i i do think a lot of the things you're experiencing are more explicable than just like oh it's just the people you follow because mastodon is more mature because there are multiple instances and because it is decentralized uh
John:
It has allowed, by design, and I would say it's a good thing that it has allowed, communities to form surrounding certain sets of values.
John:
That's what decentralization provides.
John:
You can have an instance with a set of rules that you find comfortable and acceptable.
John:
This is where you want to be.
John:
These are the people you want to be with.
John:
There's lots of different instances with lots of different sets of rules.
John:
People disagree about the rules, but that's what's great about being decentralized.
John:
Because Mastodon was inherently a nerdy thing and was founded many, many years ago, the seed, sort of the seed of the communities, was a bunch of weird nerds.
John:
That seems to have been the seed of many Mastodon communities.
John:
But the Mastodon communities have had years to grow and...
John:
And develop their own cultures and their own sort of values and their own moderation rules and their own moderation systems.
John:
And communities have already had time to grow and then fizzle out and die on Mastodon multiple times over, like stars coming into existence and then fading away or supernovaing, right?
John:
That's happened many times over in Mastodon.
John:
What that meant was that when new people show up to Mastodon, it's like you showing up on the cheerleader bus again.
John:
There is an established community there, and you're not a part of it.
John:
There are multiple established communities.
John:
And I think a lot of what has happened on Mastodon is people would show up, especially people who did not fit into the same mold as the seed communities, and...
John:
And they felt like this is not a place for me.
John:
And granted, Mastodon has multiple places, but you can't try them all.
John:
Maybe you try one place and it doesn't feel like the place to you.
John:
And maybe you're like, that's it.
John:
Like, that's your impression of Mastodon.
John:
Like, you don't know if there are other short buses with different groups of people who are talking about computer stuff where you're like, the short buses with the cheerleaders, that is not the place for me.
John:
And so you just bail on that.
John:
So I have heard from many people of color who have come to Mastodon and said, it's not welcoming me because they would come into a community and they would say, my concerns as a black person seem to fall on deaf ears in this community because what they tell me is, oh, in this community, here's our set of rules and here's the way we deal with things.
John:
And I'm telling them as a black person, those rules don't work for me because reasons X, Y, and Z, and they're not hearing me.
John:
And that person bounces off Mastodon.
John:
It was like, well, you didn't try all of so many other communities.
John:
Like, what am I going to do?
John:
Try every single community and figure out if I can find the one that fits with me.
John:
So that is the strengths and the weaknesses of decentralization.
John:
It allows sub communities to form, but the weakness is sub communities form.
Yeah.
John:
And they're their own rules.
John:
And there's no way you can have, you know, a universal view of every Mastodon community and know exactly where you should go and where you'll become.
John:
But maybe there isn't a Mastodon community that works the way you would like it to be.
John:
Oh, you should form your own.
John:
That is way harder than just signing up for one simple thing.
John:
blue sky doesn't have that problem invite only seated by you know fancy people who invite other fancy people like again the invite system you know makes it hard-coded dictates essentially you will be it's not just open to everyone the the seed round of people invite other people who invite other people and it's people who you know or whatever and it's small enough that it doesn't matter and so then when when somebody shows up there and says i felt unwelcome
John:
in the one mastodon community that i tried when i show up here it's a bunch of celebrities and a bunch of people you know posting and i don't i don't know if this is my community but i feel like i have just as much right to be here as anyone else because it's just a bunch of invite only people like it's early days and that is an advantage of being young and not having established communities of not being decentralized
John:
But if Blue Sky wants to travel that road seven years from now, if it really is decentralized and if the decentralization really does have like algorithmic, you know, plug-in algorithms and plug-in moderation systems in different instances, it'll be in exactly the same situation as Macedon, just with different seed groups.
John:
So then maybe at that point, maybe a nerdy person shows up to Blue Sky and they feel like, oh, I can't find my community here because all these communities are talking about, you know, things that I'm not interested in or whatever.
John:
Yeah.
John:
What we want to see as we like in the whole people who promote the idea of no more centralized social networks, because we've tried that many times and they all suck eventually.
John:
What we want is for there to be lots of different communities and everyone to be able to find a place where they feel comfortable.
John:
We're so far from that.
John:
It's not even funny, right?
John:
We don't even know if that's a feasible thing that could even happen.
John:
Because the closest things we have, people keep comparing it to email, but there's not really any culture in email.
John:
Your inbox doesn't really affect other people's.
John:
In fact, they shouldn't really cross over with each other.
John:
So email is federated, and it is decentralized, and you can choose your provider, but honestly, it does not really change your experience that much.
John:
Whereas social networking totally does.
John:
And I think any kind of bridging between Blue Sky versus ActivityPub versus AT Protocol versus whatever...
John:
is going to be extremely tricky and very unlikely to happen.
John:
And so currently I'm in the terrible position that I do not like of, you know, previously I was still checking Twitter, but spending most of my time and energy in Mastodon.
John:
Now I'm still checking Twitter and, and still spending most of my time and energy in Mastodon, but now I'm also checking blue sky.
John:
And it's like, this is, this is untenable.
John:
I'm checking three places.
John:
I never left Twitter and now I'm not leaving Mastodon and now I'm blue skies too.
John:
So,
John:
And three places to check.
John:
It's just too many.
John:
But the problem is the reason I didn't leave Twitter was there was people still on Twitter who weren't on Mastodon and I was still getting value from them.
John:
And I, you know, I, I try to put most of my energy into Mastodon, but I'm like, but then I still want to read what people say on Twitter.
John:
Now there's blue sky and a blue sky.
John:
Unfortunately, uh,
John:
it's not just like I want to read people who are over there.
John:
I also want to participate a little bit over there.
John:
So it's like, Oh, this, this cannot, I cannot scale like this.
John:
I cannot be continuing to check three places.
John:
So I think there will be some sort of, I'm hoping there will eventually be some sort of consolidation and resolution.
John:
Um,
John:
i'm excited by the fact that people are trying lots of different things i'm excited by different protocols and different apps i'm not excited by checking three different places so i will i will uh live in this world for as long as i can but i would it's not that i want one thing to win but that's the beauty of decentralized things and open protocols is if an actual open protocol and decentralized thing wins
John:
You just need the one.
John:
We don't need seven competing versions of web technology.
John:
We've got the web, we've got HTTP, we've got HTML, we've got CSS.
John:
We don't need, oh, well, you use HTTP, well, I use Gopher.
John:
Like, no, we don't need that.
John:
Just the web is fine.
John:
We just need the one web.
John:
I think that will also be true of if this type of decentralized social network can work at all, which just remains to be seen, we only need one.
John:
It just needs to be
John:
at least as good as the web in terms of being open and the platform that nobody owns.
John:
And despite the fact that W3C is populated by Apple, Microsoft, Google, like, oh, it's the web is corporate controlled or whatever.
John:
It's not ideal, but it's the best we have ever had.
John:
I love the web if...
John:
tweet like social networking could get to the same level of openness and decentralization as the web i would call that a big win but you don't have seven webs despite the web three idiocy uh you just have the one so i would like i would like us eventually to come together now what was the web it was a thing started by one person
John:
I'm not saying that means that Mastodon is going to win because it was started by one person and so is the web.
John:
It doesn't mean that at all.
John:
All I'm saying is that you don't have to have millions of dollars funding you.
John:
Although technically that one person did kind of have millions of dollars behind them.
John:
I mean, he was using a next to do it for crying out loud.
John:
Nobody, no person in their bedroom has a $10,000 next cube to develop their funny idea of how to publish scientific papers so that other people can read them.
John:
But I, I want there to be one of these things.
John:
I,
John:
And I want the one thing to be good.
John:
And I want there to be a lot of third party applications for it.
John:
Right now I have three things.
John:
And one of them is hopefully going down the tubes, which is Twitter.
John:
And the other two are intriguing, but at very different places in their life.
John:
And I'm checking all three of them.
Marco:
Yeah.
Marco:
And I think when you look at the protocols and everything, yeah, they're different.
Marco:
I don't anticipate the servers like, you know, Twitter is Twitter has isolated itself because of its leader and his decision making.
Marco:
They have isolated themselves so that they're off on an island.
Marco:
They have nowhere to go but down.
Marco:
Whatever you think of their current state, the age of Twitter getting better or bigger is done.
Marco:
Twitter is only ever going to stay the same or go down from where it is now.
Marco:
So that problem will slowly solve itself.
Marco:
So then you have Mastodon and whatever else comes along.
Marco:
Mastodon, I think, has enough mass and enough usage.
Marco:
It's not going anywhere.
Marco:
It's not going away for the foreseeable future.
Marco:
It's here.
Marco:
So let's take a look at Blue Sky now.
Marco:
I think if you look at these two, the amount of traction Blue Sky has is strong.
Marco:
It's very, very strong.
Marco:
So it is probably going to be here for a while too.
Marco:
Hopefully, I don't know enough about the protocols to know on the server side how complicated and possible it would be for following to work across servers, say, between AT protocol and ActivityPub.
Marco:
I don't think that's going to really become a thing at the server side, but that can probably become a thing on the client side.
Marco:
So what I expect is that in the near future, or maybe even already, I don't even know, like, whatever people are doing in test flights and stuff, I think it is probably pretty reasonable to expect there to be unified client apps where you can log in to your MassOn account and log in to your BlueSky account and follow, using both protocols, see the tweets and post the tweets in one app.
Marco:
That will probably come soon if it isn't here yet, and I think that will solve a lot of these problems for us.
John:
Will it solve them?
John:
I mean, I think, sure, you can make that happen.
John:
It's great that you can do that because Twitter explicitly, by the way, didn't allow that at all because they're a centralized company and they just said no.
John:
But it doesn't solve the problem for me because, yeah, that can be implemented from a technical perspective, but you can't reply to one.
John:
You can't have a unified conversation in that context because...
John:
like if threads can only take place on one platform you can't have a thread with mixing people from two different platforms like it's insanity like you would never be able to keep track of who can see what and who's replying to what and i'm replying there i'm applying even if you try to duplicate all your replies to the like it just it just doesn't work although in all fairness that's a problem on mastodon too
John:
No, but in my experience in Mastodon, it works pretty well because Mastodon is designed for everyone to have the same conversation in the same thread.
John:
I see threads all the time in Mastodon.
John:
That's the whole point of it.
John:
People from different instances, they're all participating in the same thread because they can all see the same things in the same thread.
John:
It's not true when you're crossing between Mastodon and Blue Sky.
Marco:
Well, in practice, there's a lot of things that subtly break on Mastodon when you cross instance boundaries.
Marco:
It shouldn't, but it does.
John:
There are rough edges there, but like the basic model of like every thread I've ever participated in Mastodon has people from different instances and they're all more or less seeing the same thing.
John:
Yes, there are rough edges.
John:
Yes, there's annoyances and that some of that is client stuff.
John:
Some of that is protocol stuff.
John:
Blue Sky hasn't even come close to dealing with any of those issues.
John:
They're so they don't even have their basic single instance functionality down yet, let alone their multi instance because they're going to have to deal with all the same stuff.
John:
Right.
John:
But across Blue Sky and Mastodon, a unified client can exist and would save me swapping apps.
John:
But combining them into a single chronological timeline, for instance, like a unified timeline across services, I don't think is tenable.
John:
I don't think it will ever be tenable.
John:
And honestly, who would want to do that?
John:
The only people would be like super nerds who are like, I'm across all social networks or whatever.
John:
Even the most, as they say, extremely online people, they just want to be extremely online in one thing.
John:
So I don't...
John:
I don't think it's kind of like saying I have a single application that lets me browse Gopher sites and websites.
John:
And I can combine all the comments on this YouTube article with the people who are commenting on Gopher and the people who are commenting on the web.
John:
No.
John:
Like, yes, you could do that, technically speaking.
John:
There's nothing stopping you.
John:
Gopher is an open protocol.
John:
HTTP is an open protocol.
John:
You could make it work.
John:
But the people who are only using Gopher would only see the Gopher comments.
John:
The people only see the web comments.
John:
And it would make no sense to either one of them because they don't know if some people can see both of them.
John:
I am not optimistic about that kind of scenario.
John:
I would, I prefer there to be for this to be, you know, the platform nobody owns is not 17 platforms.
John:
Nobody owns.
John:
We just need one platform.
John:
Nobody owns that covers the problem space.
John:
Um,
John:
And that has a viable path forward for continuing to advance.
John:
And the web, it's been a bumpy road.
John:
If you look at the, how has the web advanced as the platform that nobody owns, but nevertheless is massively influenced by trillion dollar corporations.
John:
It has not been smooth, but it has mostly worked.
John:
And I can say it has worked way better than Twitter has worked.
John:
So that's all I'm saying is like,
John:
you know, if, if we could get half as good as the web, I think that would be great.
John:
I just don't, I wish I could think of a third one.
John:
Go for the web.
John:
Uh, I guess use net.
John:
I mean, we have like the phone system.
John:
Yeah.
John:
That's a social network in a way.
John:
Kind of, but like, but yeah, like that's, that's more, that's more peer to peer, even though we have party lines and stuff.
John:
Anyway, I, I'm not, I don't, I don't see a future in which, uh, blue sky and Rastodon both thrive as in like a decade from now.
John:
And if we are in that situation, I mean, it's kind of like, you know, we were in that place where I was like, oh, there's Facebook and there's Twitter and there's the web.
John:
And it's like, yeah, kind of, I guess.
John:
But these these centralized social networks have burned us all so many times.
John:
They've burned the people invested in them.
John:
They burned the people who worked them.
John:
They burned all the users of them.
John:
And everyone who thinks like Facebook will live forever.
John:
uh it won't i hope uh but it's lasted much longer than the previous one so there is kind of a lengthening of the timelines we are still in the friendster phase of non-twitter you know twitter-like services and in the friendster phase a lot of names came and went uh no one remembers them i
John:
So we're not even at MySpace yet.
John:
Like Mastodon is not MySpace and Blue Sky is not MySpace.
John:
One of them might become MySpace, but I don't think either one of them is Facebook either.
John:
And again, that's an analogy with the centralized systems.
John:
I want the web.
John:
I want the web for Twitter-like social networking because I think Twitter-like social networking is a valuable form.
John:
Email is valuable.
John:
The web itself is valuable.
John:
you know instant messaging in the form of whatsapp and i message all that is valuable this form small message like the way twitter that that thing that the twitter established that is useful and valuable and apparently very hard to do well i hope we i hope we come up with a better way to do that that is not owned and controlled by a small group of people who make terrible decisions
Marco:
Just before I move on, the unified client app thing, maybe we won't see a unified timeline.
Marco:
Maybe we will start with the way that multiple accounts show up in an app.
Marco:
Maybe you can have multiple account types, and you can have the same interface, but you have to switch between the two accounts.
Marco:
Fine.
Marco:
That's probably how we start, and I don't think that's necessarily a bad thing, because there's a lot of feature overlap, and that's probably pretty straightforward.
Marco:
Ultimately,
Marco:
My biggest concern with Blue Sky is the same concern I have with Mastodon.
Marco:
I don't know how these things are going to scale in either the technological sense or the financial sense or the moderation sense.
Marco:
Those are the three big areas.
Marco:
And Mastodon is way ahead of Blue Sky in its scale, and they've had a long time to work out some of those things.
Marco:
Looking at the realities of how ActivityPub works, the realities of running large instances or having people with large followings, ActivityPub does not seem to scale very well.
Marco:
It seems like it's holding up okay under the existing scale of Mastodon most of the time.
Marco:
That's a lot of qualifiers.
Marco:
Mastodon does not feel like something that has a lot of headroom in its design in terms of technical scaling.
Marco:
Blue Sky, obviously a way smaller scale currently, but because there are so many Twitter people designing it and running it, Twitter, for all of its faults, and even though it had a rough start, scaled really well to a scale that none of these other services can even dream of.
John:
Eventually.
John:
This is what we talked about when we talked about Mastodon.
John:
Early Twitter was very much like Mastodon and absolutely did not scale, and they basically redid it.
Marco:
Yeah, and granted, it had a rough early time, but that's ancient history now.
Marco:
Modern Twitter scaled really well, really impressively.
Marco:
Everything was extremely fast, extremely reliable, hardly ever had any downtime, hardly ever had delays and stuff showing up.
Marco:
That is not how Mastodon is right now, and it's at a fraction of the scale, and so I'm concerned about Mastodon's and ActivityPub's ability to scale, and in some of the protocol arguments, they've actually, like the people who were attacking the AT protocol on tentacle means, like it seems like the AT protocol, again, I don't know much about it yet, but it seems like they have taken scaling in a different way that is probably
Marco:
probably more likely to scale better.
Marco:
And I would trust the people who are building Blue Sky to know that stuff better at the scale that we're talking about with possibly becoming a Twitter-like replacement.
Marco:
I would trust those people to know how to do that better than ActivityPub does it.
John:
Well, so the thing about, well, Mastodon, interestingly, uses very similar technology stack to early Twitter, which is kind of why we know it's not going to scale well.
John:
But because it's decentralized, there's always the out of like, well, an individual instance can never get that big or whatever.
John:
But anyway, I will point out that Mastodon is only one order of magnitude away from Twitter scale.
John:
which granted order of magnitude is a lot they're at 10 million twitter is a couple hundred million right this is one order of magnitude away and that may be sufficient you know with decentralization they could potentially get there blue sky looks like they have a better handle on scaling at least a better idea of how scaling will work but you don't know until you actually try it right and they're they're like because we have to see them actually do it um
John:
The other thing about Twitter, Twitter started off, you know, like a Ruby application that didn't scale with, you know, a bad database back in.
John:
And then they fixed it all and redid it all with the addition of millions and millions and millions of dollars.
John:
Right.
John:
Don't forget that.
John:
It's not like the person who wrote the original implementation of Twitter gave it a second try and it worked out.
John:
No.
John:
They have many employees, tons of money.
John:
A lot of that was VC, but eventually they found a business model that did actually produce many millions of dollars in revenue.
John:
Not enough to make them a gangbuster successful corporation, which is why they sold to that idiot.
John:
But still, that is an ingredient that is absent from both Mastodon and Blue Sky.
John:
Because Blue Sky, yeah, they got millions of dollars poured into them, but nothing like the amount of money Twitter had poured into it.
John:
And also, Twitter eventually found a way to have revenue, and Blue Sky is not a glimmer in their eye.
John:
Yeah.
John:
Uh, the, the decentralization as your ultimate out to scaling is not entirely valid, but if you just want to scale a little bit more and you can be like hand wave, hand wave, as long as we have more instances instead of bigger instances.
John:
And as long as our bigger instance scales up, like when I look at activity, Bob, I think of someone looking at the web in the nineties and saying, Oh, this will never scale.
John:
and they were right http 1.0 with apache or whatever ncsa web server ncsa httpd that wouldn't have scaled to the current scale of the web but somehow through the starting off with that janky technology through a very bumpy path we got to where we are today where the web is as they say web scale and it's not because the people who originally made it had the forethought to make something that was scalable
John:
because they didn't they just made something that they thought worked or whatever and it had to be revised and it had to be improved and lots of other third parties had to come up with ideas and you know a company funded by something else entirely which is google figured out how to search the web and made bazillions of dollars has now contributed to the advancement of the web by you know coming up with the new versions of http that are in turn more efficient and making browsers that are efficient and like
John:
activity pub looks way more like the early web than blue sky does now blue sky is like well why do we repeat the same mistakes the people making blue sky understand how to scale and they have some interesting ideas about how this could be done well but the thing about interesting ideas is they're interesting because like oh i don't think anyone's tried that before and that's kind of a danger zone where it's like you know it's the worst is better thing
John:
We've done the thing where you start off with something simple and unscalable and figure out how to make it bigger.
John:
The ones where you start out with something that is novel and interesting and scale better than anything came before it, it happens.
John:
It can be done.
John:
But even in the best case scenarios, which I'm thinking of this because part of what they're doing with the data model and everything is a little bit like Git, not really, but like they use some of the same terminology as in terms of having a repository, the approvably correct repository with transactions committed to it.
John:
You squinted, it might look like a database, it might look like Git or whatever.
John:
Git is a good example.
John:
It is a very interesting model for dealing with change management and fantastically successful, partially because of its pedigree, kind of like perhaps Blue Sky maybe one day.
John:
But Git is not universally better than all the centralized services that came before it.
John:
Git does not scale as easily as some of the centralized ones due to the way it's designed.
John:
If you have a single repository with millions and millions of files doing anything, Git all of a sudden starts slowing down.
John:
And the answer to that from Git perspective is don't do that.
John:
Don't have a repository with millions and millions of files.
John:
Have fewer smaller repositories, use Git modules, do this, do that, do the other thing.
John:
It's not to say that Git is bad.
John:
It's just that like as novel and interesting as Git was and it brought all this value with, you know, again, the fact that it was novel and it did have features other things didn't have.
John:
It's not universally better.
John:
So I don't know how Blue Sky is going to turn out.
John:
Again, they're not done making Blue Sky.
John:
They're still working on the basics of the protocol.
John:
They're just getting around to figuring out how blocking works for crying out loud.
John:
Like they're in very early days.
John:
And I do like a lot of the ideas they have in particular, the fact that when you change instances, you bring your posts with you.
John:
Uh, although the way they do that seems a little janky, but anyway, uh, I applaud the efforts in these areas, but I do right now.
John:
I kind of feel like activity pub for all its warts is following a path that looks familiar to me that where you start out primitive and not great and having scaling problems and you eventually figure them out.
John:
And blue sky, uh,
John:
The reason I signed up for it when they first came out, it was like these people have thought hard about the problems.
John:
These people are not just coming in blind and saying, oh, I'll just get something simple working and I'm sure it'll all work out.
John:
They're not doing that.
John:
They're saying, we know here are the hard problems to solve and we have some ideas about how to solve them and we're going to come in and we're going to start off on third base.
John:
And I was like, yes, these guys get it.
John:
They're going to do it.
John:
I'm rooting for them.
John:
I just don't actually know if they're going to do it.
John:
And so it seems like a higher risk factor where he seems unfamiliar.
John:
And the fact that Jack Dorsey is involved doesn't really make me that excited anyway.
John:
I do appreciate his millions of dollars.
John:
I don't appreciate his personal involvement in any way.
John:
The good thing is he's been distracted and has gone off it to deal with N-O-S-T-R, Noster, Noster.
John:
He's involved with that too?
John:
Yeah, what is that?
John:
Oh yeah, he's given up on, not he's given up on Blue Sky, but that's his new darling, is that.
John:
Oh God.
John:
And that...
John:
I know even less about, and it seems like their goals are different.
John:
When I read the AT protocol thing, I felt like, yeah, they're thinking about the hard problems.
John:
When I read about the, the Noster stuff, I was like, you're thinking about different problems and I'm not really interested in, I'm not really interested in what you're doing.
John:
Even if you succeed, it doesn't sound cool.
John:
Whereas I read the AT protocol thing and I said, if you succeed, yeah, that'll be a thing I'd want to use.
John:
So we'll see how this shakes out.
John:
I don't need another app.
Yeah.
John:
And I check four places.
John:
I did sign up for Noster twice.
Casey:
Oh, my word.
John:
Accidentally.
John:
Because that's how it works.
John:
It's confusing.
John:
Anyway, more updates on Noster in 2045.
John:
Stay tuned.
John:
Oh, my word.
Marco:
To me, those scaling questions, that's the biggest thing.
Marco:
Who knows how this is going to end up, but what Blue Sky is going through now, this is the easy fun phase.
Marco:
You have only the cool people.
Marco:
You have a small number of people.
Marco:
You don't have a lot of scaling challenges.
Marco:
You're spending someone else's money.
Marco:
You're not thinking about how to make money later.
Marco:
That's the stakes there and now.
Marco:
It gets so much worse after this.
Marco:
You tell people, oh, it gets better with some different kind of things.
Marco:
When it comes to running a social network, it gets worse.
Marco:
Everything just gets worse over time running a social network.
Casey:
What do you even know about that, Marco?
Marco:
So they're going to have to start facing these tough problems.
Marco:
And the new cool darling phase we're in now is going to end.
Marco:
And they're going to face how do you pay for this?
Marco:
What does that do to the openness and the protocol and the client and everything else?
Marco:
They're going to face how do we deal with Nazis and blocking and everything else.
Marco:
They're just starting to deal with that now.
Marco:
That's going to quickly ramp up.
Marco:
The fun part will be how do you deal with technical scaling?
Marco:
Because that at least is a little less controversial.
Marco:
But the harder problems of how do you pay for this and how do you handle moderation?
Marco:
I don't see any evidence that... As smart as Blue Sky is on the technical side, I don't see any evidence that they're going to have an easier time solving those other problems than any other big social network has in the past.
Marco:
I do think it is...
Marco:
It is where a lot of people are, and it's where a lot of people are going, and it's pulling people off of Twitter who never made it to Mastodon.
Marco:
It was delightful.
Marco:
As I was going through and following people on Blue Sky, reading other people's follower lists, I was finding people that I've missed these last few months that I haven't been on Twitter because they never came to Mastodon.
Marco:
They've just been on Twitter.
Marco:
And so...
Marco:
Macedon didn't bring everyone over who I wanted to follow so I'm happy that this other place is attracting them so that I can see their stuff and I can keep contact with them and keep following them and have them keep following me without having to go back to Twitter where I really don't want to go so I like that part of it but again the challenges have yet to come and the technical side is one thing but the messy problems are not technical and
Marco:
So far, we have no idea where Blue Sky is going to land on that.
Marco:
Mastodon does an okay job of that stuff.
Marco:
Not even a great job.
Marco:
Blue Sky is a question mark.
Marco:
So, we'll see.
Marco:
Anyway, thanks to our sponsors this week, Steam Clock and Backblaze.
Marco:
And thanks to our members who support us directly.
Marco:
You can join us at atp.fm slash join.
Marco:
And we will talk to you next week.
Marco:
Now the show is over.
Marco:
They didn't even mean to begin.
Marco:
Cause it was accidental.
Marco:
Oh, it was accidental.
Marco:
John didn't do any research.
Marco:
Marco and Casey wouldn't let him.
Marco:
Cause it was accidental.
John:
Oh, it was accidental.
John:
And you can find the show notes at ATP.FM.
John:
And if you're into Twitter...
Marco:
You can follow them at C-A-S-E-Y-L-I-S-S, so that's Casey Liss, M-A-R-C-O-A-R-M-N-T-M-A-R-C-O-R-M-N-T-M-A-R-C-O-R-M-N-S-I-R-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-
Marco:
I've been fighting SwiftUI so much.
Marco:
It's been good though.
Marco:
It's been like, I talked about it a little bit under the radar this week.
Casey:
Yeah, I was listening to that earlier today.
Marco:
Like my, my main pattern has been, I'll run into a problem.
Marco:
I will explode my solution in complexity trying to solve the problem.
Marco:
You, then I will find a really simple way around the problem and I'll delete all the complexity.
Marco:
And so I'm left with like a one liner saying, you know, some modifier or some, some weird little technique or, Oh, this state should have been a binding, you know, like something like that.
Marco:
And, and I'll fix the problem.
Marco:
It'll be glorious.
Yeah.
Casey:
I ran into this earlier this week.
Casey:
I was working on tapping on like a person's picture or a movie poster or what have you and zooming in and taking up basically the whole screen.
Casey:
And I was like, oh, God, I'm going to have to do like geometry readers up and down and inside now, which is my there's probably one or two geometry readers in call sheet right now.
Casey:
But there's very, very few.
Casey:
There's not a lot of them.
Marco:
Hey, for the record, I know there's a lot of people who are like geometry readers, make it hacky or whatever.
Marco:
I think geometry readers are fine.
Marco:
There are ways to use them very easily, very well, very cleanly.
Marco:
They are totally fine.
Marco:
I do not hesitate to use a geometry reader if I have to.
John:
I would hesitate a little bit.
John:
It's not because they're bad.
John:
It's just that very often when you use a geometry reader, there's a cleaner way to do it without one.
John:
Sometimes there's not.
John:
Sometimes you got to use it.
John:
That's why it's there.
John:
It's there for you to use it, right?
John:
So don't be afraid to use it when you have to use it.
John:
But...
John:
not going to say in every instance, but in many, many of the instances that I started out using Geometry Reader, I came back later and realized, oh, there's actually a way to do this without Geometry Readers that is cleaner.
John:
Sure.
John:
And that feels too good to get rid of them.
John:
And the problem is, because, well, this actually gets into something that I've been thinking about when I hear you talking about SwiftUI, and you Casey as well, with the complaints about it.
John:
Geometry Reader can be thought of as a lower level of abstraction than the rest of SwiftUI.
John:
Because it's like, look, when you've got to drop down a level,
John:
uh here you can get it the raw geometry uh and it's kind of a weird clunky way to do it where this thing exists and its whole point is like i just i'm not a thing i just exist to extract these numbers for you that you're gonna find really handy so use them for something and you do and it may solve your problem right i what i found is that a lot of the
John:
Difficulty in Swift UI when people say, oh, if it does what you want, you're fine.
John:
But if you want to do something fancier, you have a problem.
John:
It's because Swift UI doesn't have enough layers.
John:
Like it's not built on everything that's cool in Swift UI is not built on slightly less cool pieces that are built on slightly less cool.
John:
Like, you know, the sort of the layer of abstraction.
John:
A good API or a mature API will say, here you can do the easy thing.
John:
Drop down one level.
John:
Here is another whole world that is also really nice, has public APIs, is well thought out, but the pieces are just a little bit lower level.
John:
And guess what?
John:
Every one of those pieces, it was built on other pieces that are also really nice, also with a really nice public API.
John:
In fact, you can write your whole application on this level if you wanted.
John:
And it's all beautiful and it's just documented and it works in a sensible way.
John:
and like that all the way down that makes it so easy to do whatever you want because if you're doing everything at the very top level it's beautiful and if you want to do one custom thing peek underneath the covers and there is another layer underneath that that is also beautiful it's not underneath there is pipes and wires and like sparks are flying everywhere and everything's made of oatmeal that's not what you want like oh i gotta start swizzling cymbals and i'm and i'm like i'm you know doing stuff with uh with unsafe pointers and like
John:
Like that's not what we're talking about.
John:
We're talking about when you open up one box inside is another beautifully wrapped box with documentation and tests and everything.
John:
Right.
John:
And Swift UI is not that.
John:
And it's not because Swift UI is the model is wrong or it's inherently wrong.
John:
It's just that that's not like sometimes there are levels of pieces you can see.
John:
piece x of swifty y is built on pieces y and z but very often it's like this is the top level thing and underneath it is no user serviceable parts as the the saying used to go on the stairs do not do not look and and it's and i feel that so much when i'm using it especially since i spend a lot of time at app kit as well which does have user serviceable parts underneath lots of stuff and
John:
You know, if you go all the way down, there's like a hierarchy.
John:
NS view is a class you can use and understand and was designed and is documented for humans to use.
John:
And it underlies so much stuff.
John:
So it's like, I hope I never have to drop down to NS view.
John:
I hope I can use it at this level.
John:
You know, I want to use NS table view and whatever.
John:
I don't know what the collection view is called in NS land.
John:
But there's like five layers, and every single one of those layers is a public API that is supported that you can use.
John:
And you just need to drop down until you can solve your problem.
John:
Whereas SwiftUI is so often one layer, and there's no reason it has to be.
John:
And Geometry Reader is an example of that.
John:
It's not that everything is built on Geometry Reader, but it's kind of like they made a fake layer.
John:
It's like, well, underneath the scenes, Geometry Reader isn't what we're building on, but you know what Geometry Reader is built on?
John:
that's underneath all these other pieces but you can't see that part and so like i started off saying you should feel kind of bad for using geometry reader because there may be a simpler way to do it which is true but the main reason i'm saying that is because geometry reader is not really the next layer down in abstraction geometry reader is just like
John:
them poking up a little thing as like an apology of like, no user serviceable parts, but if you just want the dimensions, this thing will give them to you.
John:
Good luck.
John:
And then you run away.
John:
Uh, so I, I, I don't know how best to phrase that.
John:
I think I used to have a better term for this.
John:
I used to talk about all the time when I would make frameworks and my jobby jobs is that you have to have, you have to be built on layers and layers.
John:
And each one of those layers is a perfectly serviceable top layer.
John:
Like that's the beauty of it.
John:
Whether you start from top down or bottom up, uh,
John:
It can't just be one amorphous blob and you can't say this is the interface and everything else is internals.
John:
Great frameworks, great APIs are you can use them at whatever level you want to use them.
John:
And every level is designed.
John:
Every level is thought out.
John:
Every level is documented.
John:
And that makes for an experience that everybody loves.
John:
And I feel like SwiftUI can get there.
John:
as long as the people making it have that philosophy.
John:
Because right now it seems like people making SwiftUI have the philosophy of like, oh, if you're having that problem, just tell me and I'll add another parameter to the top level API.
John:
That is not a scalable solution.
John:
We appreciate it.
John:
Sometimes you should.
John:
Sometimes the top level API is too poor.
John:
It is too...
John:
It doesn't have enough features.
John:
It should have another parameter or there should be another method.
John:
But sometimes the solution is stop adding stuff to the top level.
John:
Show me what's underneath it.
John:
Oh, there's nothing underneath it.
John:
You need to build something underneath it.
John:
Like whatever the next, it's still Swift UI.
John:
It's just like, just like, you know, NS view is part of app kit.
John:
And so is NS table view.
John:
They are part of the same family, but they are different levels in the hierarchy.
John:
Swift UI needs that as well.
Casey:
Yeah.
Casey:
It's just funny because, you know, the thing I was running into is, you know, the zooming stuff that we got sidetracked from.
Casey:
And I thought, OK, well, we need to use geometry readers and figure out where I am in the screen.
Casey:
And then I have to, like, do some crazy math in order to move the frame of that view and blah, blah, blah.
Casey:
And then by sheer circumstance, I stumbled on a matched geometry effect, which is a view modifier that basically you put this on two different views and then say, okay, I want to go from one view to the other and magic happens.
Casey:
And it's not perfect, but it's good enough.
Casey:
And the conversation that you guys were having on Under the Radar was very, very relevant because I know...
Casey:
And if you look closely, and I probably shouldn't say this out loud because other people notice now, but I know that the animation for the zooming of the images is not 100% correct.
Casey:
But you know what?
Casey:
It's close enough.
Casey:
And I have other things I should be working on than making that pixel perfect.
Casey:
I want it to be pixel perfect.
Casey:
I will hopefully one day make it pixel perfect.
Casey:
It's been in the back of my head.
Casey:
Underscore talks a lot about this.
Casey:
It's just like...
Casey:
My subconscious brain has been chewing on it a lot over the last 48 hours trying to figure out how to make it pixel perfect.
Casey:
But ultimately, now is not the time to make it pixel perfect.
Casey:
It is serviceable as it is, and that's better than nothing.
Casey:
And that's what I plan to ship, at least for now.
Casey:
But yeah, this week's under the radar.
Casey:
They're all good.
Casey:
But this week's certainly struck home for me as I'm trying to figure out, okay, what juice is worth the squeeze and what isn't.
Marco:
So how close are you, I think, to shipping 1.0?
Casey:
uh so i was saying to you privately before the show and and i think it's very true i need underscores uh sailboat emoji no new features sailboat emoji you know his little sheet uh that he uh he'll put up from time to time he'll probably send you a pdf if you ask him he probably he probably will in fact knowing him it'll probably be in my inbox by the time i wake up but um
Casey:
So I have 13 issues in GitHub at the moment, but I have labeled all but two of them as not right now.
Casey:
Here's a list of things I want to do eventually, but not right now.
Casey:
And there's only two things left for right now.
Casey:
One of them is to see about improving...
Casey:
The way I do layouts such that there's some very, very small shifts as images are loaded and things of that nature.
Casey:
And the UI will shift around a little bit.
Casey:
It's a little bit annoying, but not devastating.
Casey:
And I'd like to at least spend a few minutes to see if I can improve that.
Casey:
And then the other thing I need to do is properly implement my paywall, which is to say I'm going to do the whole dance of, you know, you get some number of searches for free.
Casey:
I haven't figured out what that number is yet.
Casey:
And then subsequent to that, you're going to have to pay in order to do anything else.
Casey:
And so I was looking into...
Casey:
What is it?
Casey:
Oh, NS Ubiquitous Key Value Store, which I've never used before.
Casey:
I'm using CloudKit for stuff in this app.
Casey:
And I've used a teeny bit of CloudKit in Masquerade.
Casey:
And I'm using a fair bit of CloudKit in this app.
Casey:
But I've never used the Ubiquitous Key Value Store.
Casey:
And I was thinking about using that to store basically how many searches you've done.
Marco:
It's so much better than any other iCloud thing.
Casey:
I actually quite like the CloudKit fake database thing.
Casey:
I've written a pretty good facade in front of that that I'm pretty happy with.
Casey:
But I've heard horror stories about some of the stuff that preceded it.
Casey:
Like core data for iCloud I've heard was a nightmare from the moment it launched and is still a nightmare today.
Marco:
Yeah, the key value store was one of the original three iCloud methods.
Marco:
It was core data, that, and I believe the document-based... You mean CloudKit, not iCloud, right?
Marco:
No, I mean iCloud.
Marco:
When iCloud first launched as an API, it was three things.
Marco:
It was iCloud core data, which was a disaster and is, I believe, totally discontinued.
Marco:
There was also this key value store and, I believe, a document thing.
Marco:
This is the only thing that has survived
Casey:
But to John's point, the thing I'm talking about, the thing I just said I have a facade in front of, that is definitely 100% cloud kit.
Casey:
Yep, yep, yep.
Casey:
But I've never used the key value store before, and so I need to take a quick look at that.
Casey:
It doesn't look to be particularly complicated.
Casey:
It looks to be pretty straightforward.
Casey:
Knock on wood.
Marco:
No.
Marco:
It's really simple.
Marco:
It's very similar to just using NS user defaults or user defaults.
Marco:
It's very, very similar to that.
Marco:
You'll see.
Marco:
You have to watch for some notification when you get new data.
Marco:
That's about it.
Marco:
It's very simple, very old, and I have found... That's what I use for Overcast's login account thing, and it's been fine.
Marco:
I've never had a problem attributable to that.
Marco:
And I could be wrong.
Marco:
I don't think...
Marco:
that requires the user to have iCloud Drive enabled.
Marco:
Remember, I hit that problem when I was looking at CloudKit, where CloudKit's database and everything does not work for users who have iCloud Drive disabled.
Marco:
That's where it stores its data.
Marco:
As far as I know, the key value store does not have that restriction, I don't think.
Marco:
I should probably test that.
Marco:
But I think anybody with an iCloud account at all signed into the device, I think can do that.
Marco:
The downside is that you are limited in terms of like, it only allows a certain number of records and they have to each be a certain size or smaller.
Marco:
But for what you're talking about, it'd be totally fine.
Casey:
Yep.
Casey:
And so I need to do that.
Casey:
So the two items are, you know, take away the shiftiness.
Casey:
That's with an F. Take away the shiftiness and set a total limit of free lookups.
John:
Lookups, would you say?
Casey:
Yeah, that's right.
John:
Is it a total per day, per week, or total all time?
Casey:
Honestly, I hadn't thought too much about it, but my current thinking is all time.
Casey:
So you'll get, and again, I don't know what the number would be, but you'll get 10 searches or something like that.
Casey:
Maybe it'll be five, maybe it'll be 50.
Casey:
I don't know.
John:
I'm kind of in favor of per unit time, but we'll see.
Marco:
Have you decided what price you're going to charge for the premium?
Casey:
Uh, no, I don't, I don't know.
Casey:
It's all over the place, right?
Casey:
Cause the feedback I've gotten, which has generally been very, very good.
Casey:
Uh, but some people are like, Oh my God, take my money.
Casey:
I'll give you infinite money for this, which of course, you know, is being, they're, they're being facetious.
Casey:
But the point is, you know, they would potentially pay like $10 a month, which I think is, is too much.
Casey:
Um, and I've, and I've heard people say, you know, I'll pay one or $2 a month and, and for a while or for a month, I think that's completely reasonable for a year.
Casey:
That's not enough.
Casey:
Um,
Casey:
So I'm thinking, as we discussed when we first had the conversation about what is now Call Sheet, I'm currently thinking somewhere to the order of $8 a year.
Casey:
And the other thing I am having really complicated thoughts about is whether or not I should offer a lifetime unlock for something to the order of like $40 or $50.
Marco:
No, don't.
Marco:
Don't do anything lifetime.
Marco:
Trust me.
Marco:
You will regret it.
Casey:
Well, that's the thing.
Casey:
I don't know.
Casey:
And I was talking to our friend Ryan Jones, and he had extremely strong feelings about how I should do the lifetime thing.
Casey:
And he made some pretty compelling arguments, which I'm not in a position to try to verbalize here in the heat of the moment.
Casey:
But suffice to say, his arguments were very compelling.
Casey:
So I'm not sure what I'm going to do.
Casey:
Yeah.
Marco:
Here's what happens.
Marco:
Your lifetime customers will be the fewest.
Marco:
You'll make the least money overall in total from them, and they will be your biggest pains in the butt because the entitlement they will have makes it not worth it.
Marco:
Trust me, you do not want those customers, and you won't get many anyway, so it doesn't matter.
Marco:
Focus on your subscription price that everybody else will pay.
Marco:
That's your product.
Marco:
I think $1 a month or up to $10 a year I think you could easily do.
Casey:
Yeah.
Casey:
So, I mean, again, this is all current thinking, but knock on wood, if I can't, you know, I'm only going to, I'm going to time box, which is a very corporate thing to say, but I'm going to time box the taking away the shiftiness to like, you know, a day or something like that.
Casey:
You know, just give myself a little time to see if I can improve it.
Casey:
But if I can't, oh, well.
Casey:
And then I think the task for the remainder of this week, what little is left and next week is getting the paywall squared away.
Casey:
I need to rejigger the actual paywall screen itself because it looks like garbage right now.
Casey:
I need to rejigger that.
Casey:
I need to actually track how many searches you've done and so on and then put up a paywall when you've hit your limit.
Casey:
But hypothetically, you know, as early as about, you know, a week, week and a half from now, I might be pushing the first build to, you know, App Store review.
Casey:
Hopefully, maybe.
Casey:
Famous last words.
John:
You've got to factor in time to get rejected because your paywall screen doesn't comply with whatever they want.
Casey:
Yep, that's true.
Casey:
And this is my first time doing subscriptions, so surely I'll get some sort of issue with that.
Casey:
Who knows?
Casey:
But one way or another, that is the hope.
Casey:
So given that I told you I think it'll be a week to a week and a half, that means it'll be about three to four weeks before I push it to the App Store.
Casey:
Because you always multiply by two is my lesson I learned over my many years in corporate America.
Casey:
Whatever I think it'll be, it'll be twice as long.