For Crying Out Loud, Own Your Content!
My account on LinkedIn earlier this week was frozen for 36 hours. It really hit home the need to have my content on a platform that I own and control first before sharing on social media.
A good reminder that you want to have a website with your own content on it before you post it on Social Media.
Earlier this week my LinkedIn account was frozen for 36 hours, without much explanation. After submitting my ID all I could do is wait for them to get through the queue ahead of me to get unlocked.
I had to reactivate my Twitter/X account to get to their support. Yes, I felt dirty for doing that.
Even then, it only helped to get on their radar, because they pretty much said they’d get to it when it came up in the order of complaints.
I’ll save the the whole customer service angle of this event for another day. But let me just say that LinkedIn’s support SUCKS.
What’s more. I pay a good amount for LinkedIn every month and I still got bad service.
It was a good reminder that we’re all using LinkedIn, Facebook, Instagram, etc. like we own our profiles and pages. We don’t. They are on rented/borrowed land that can be taken away at any second.
So What Should You Do?
Post first on your own site/blog, then share on social and even link back (in the comments) to the original.
Even shorten the URL so you can get some data to see who clicks on the source material.
Whatever you do, save your content somewhere safe. Don’t rely on these huge companies to give a crap about you and your content. You’re just a number to them on a P&L sheet.
Have any one else here been locked out of a social media account? How long did it take to get back on the platform. The comment section this time is open to everyone, not just paid subs.
The Latest From Entrepreneur’s Enigma
Web Jawn
Embrace, Extend, and Exploit: Meta’s plan for ActivityPub, Mastodon and the fediverse
An interesting take on Meta’s Threads.net federating with the greater fediverse. I’m on my own server, so I get to decide whether or not to connect to Threads. As of now I’m going to. Because there are people on Threads that I want to follow who are not on any other federated service and the Threads interface sucks.Report Finds X’s Community Notes Moderation System Fails To Address Harmful Misinformation
Are we even remotely surprised? I’m not. Thanks Elon! 😡
CapCut Adds New Features for Short Form Video Editing
CapCut, owned by ByteDance the parent company of TikTok, is a neat app and worth trying out. I was skeptical at first, especially with its ties to ByteDance and China, but I caved in and gave it a whirl. It’s really good.An Overview of the Evolving Generative AI Landscape [Infographic]
I love these types of infographics. It’s quite impressive the AI landscape after only a year of real growth.4 pillars of an effective SEO strategy
Good solid piece explaining to stick to the basics.
Rules targeting financial criminals will require new filings for startups and small businesses
More stuff to file for SMBs and Startups, but it’s to prevent fraud, so it’s for the best. Doesn’t seem to complex either.AI news to watch for in 2024
Some predictions from Technical.ly and what to watch out for in 2024 with AI.Digital inaccessibility: Blind and low-vision people have powerful technology but still face barriers to the digital world
I can’t even begin to imagine a world where I don’t have my sight. Technology is getting better, but not fast enough.A good post about how to deal with Meta’s Threads federating with the Fediverse.
Web Find
Lemmy is the fediverse’s answer to Reddit. I like the instance Lemmy.World the best, but because it’s federated you can join almost any server and interoperate with other Lemmy servers. What’s more you can engage with Lemmy via any other ActivityPub service like Mastodon and Pixelfed.
Here’s a tip, you can use Google etc. to search most of Lemmy’s instances.
Check it out!
—
That’s it for now. Until Next Week!
Always stay curious!
– Seth
