jetpack

Currently listening to: Sorry I’m Here For Someone Else – Benson Boone

I’m sorry I’m here for someone else
It’s good to see your face
And I really hope you’re doing well
I hope you’re doing well
I’m sorry I’m here for someone else
I know you wish that I could stay
And talk at the bar all by ourselves
But I’m here for someone else

So far, I’m actually liking a lot of the updates made to Jetpack—it’s giving more functionality without too much fluff, which I appreciate.

The Pros:

1. First of all, I love that I can finally approve comments from my phone without accidentally hitting delete. Fat fingers and tiny buttons were not a good combo—this is a subtle but major win.
2. Also loving that I can now see comments that got wrongfully flagged as spam. I no longer have to wait till I go home to look.
3. Being able to see the stats is cool. That said, part of me does wish I could see who exactly viewed my post. But also… maybe I don’t want to know? It’s a toss-up between curiosity and anxiety.
4. It’s free (for personal use). Which, let’s be honest, is always a +.
5. It’s user-friendly.  It’s way more intuitive than when I was using HTML, CSS, JavaScript.

The Cons:

1. The scheduled posts thing? Infuriating. Sometimes I’ll set a date and time, only to come back later and see it “missed” the schedule completely. Ugh.
2. I don’t love that some blogs require you to log in to even view a post. If I’m already logged into Jetpack, shouldn’t that be enough?
3. I still use the classic editor. Yes, I know it’s ancient and Gutenberg is the latest, but I hate the blocks. Sometimes I just want a simple text box and the option to sneak in a little HTML when needed. I know the block editor has all these bells and whistles—and that it’s where the future’s headed—but sometimes simpler is better.
4. The add-ons are pricey. I get it—features cost money—but I’m gonna stick with the basics.