Blog

Facebook Account Access Issues

close up photography of smartphone icons

Over the years, I’ve helped a few people regain access to their Facebook accounts. Most all of those times were relatively easy since they were simply forgotten passwords. One was more complicated where a former social media consultant basically vanished and ghosted the business owners. The main challenge for me entailed getting copies of the business license and then a letter from the business owner. The hardest part (for me) was the waiting. It took me a fair bit of googling to track down a way to make the request, and then I had to wait for Facebook to respond. A few minutes of work that took weeks to complete due to slow communications.

So, now, I am working with someone whose account was compromised/taken over by someone else. Facebook’s knowledge base was a series of loops that accomplished nada. Frustrating. I then reached out to a friend who worked at Meta, who let me know that they’d risk termination if they tried to route me outside of the “normal channels”. So, as I value my friend, I opted to not push it. But, man, it’s frustrating. All of this to state that my experience with troubleshooting Meta issues has gone from clunky to infuriating.

So, when I read this article on Engadget, “How small claims court became Meta’s customer service hotline“, I groaned in recognition. I can see why people are using law suits to push Meta to act. I expect that they hope that this level of agrevation will deter people from seeking help and they just give up. However, I doubt that’s really going to be the case. Besides, I would expect that Customer Service Reps are much cheaper than attorneys. This seems to be the most expensive way to navigate this situation.

Since this article is posted on a major blog, I wonder if more people will seek Meta customer service via small claims court. Perhaps it will become painful enough for Meta to finally staff their customer service department adequately. Perhaps…

This strikes me as an element of Cory Doctrow’s “Enshittification”. In particular, the notion of “too big to care“. For so many folks, Facebook is an 800 pound gorilla. And they know it and are hard pressed to care.

A new (to me) Facebook Phishing Scam

scam alert letting text on black background

So, one of the accounts I manage got this message today:

A quick search of the message language confirmed to me that it’s a scam. The biggest clue was the “bio.site” link. Very phishy. The clunky sentence “Your Facebook page is scheduled for permanent deletion due to a post that has infringed upon our trademark rights” was another clue.

This article was pretty high up on the Google SERP and is pretty solid on it’s analysis and advice.

If you get one of these, first and foremost: don’t click the link! If you’re at all concerned, reach out to Facebook directly.

So, I filed it as spam and reported this account. My contempt for scammers is rich and deep, so I hope for some consequences. However, I recognize these folks will simply open another account when/if their accounts get locked. It is a rather annoying game of whack-a-mole. One that will probably continue to be a focus of mine for the foreseeable future.

Today’s Tech Annoyance

young ethnic male with laptop screaming

So, one of the things I do regularly is markup PDF documents. Every time I add text I get the notice below:

No, I don’t need to have someone sign this. I know how to set up e-signing, I’ve done it literally hundreds of times. Quit bugging me, Adobe! I know what I’m doing. Argh! Nagging me every few seconds is, *ahem* annoying.

Yeah, I know, first world problems, but geez, trust your users to know what they’re doing.

Today’s Podcast

an artificial intelligence illustration on the wall

One of my favorite things is listening to podcasts on my walks. During today’s walk (you can check that out on Strava, if you care) I listened to Saturday’s (June 8) Geekwire podcast: “How This Professor teaches AI and thinks about human creativity“. Featuring Léonard Boussioux, I appreciated his positive outlook on the potential that AI offers. I agree with those folks who think AI is in a hype-cycle. However, that doesn’t mean that there are no gains or innovations that will be coming out of this. I deeply believe this technology will be significantly transformative. However, I doubt it will be as destructive as some predict, nor as positive as others are thinking.

I also appreciate that they touched on the sustainability issues surrounding AI. Huge amounts of energy and water are part of this equation. These will be key elements for the efficacy of this technology.

I have a few ideas that I want to explore with AI tools. These tools will be critical ones to learn and master. I’m confident many jobs that will be replaced by AI, will create new roles on the other side of this equation.

They had a side discussion looking at the ethics of using AI to enhance photography, and what should be disclosed. Todd Bishop, one of Geekwire’s founders, used an AI tool to enhance (de-noise is the phrase they used) an image. When I first heard the situation, I thought that disclosing was unnecessary. Mainly, I don’t see any difference between “de-noising” and color-correcting, or cropping. As they went on and explored the issue, I shifted to thinking disclosure is the wisest course. As I respect the distrust many feel towards AI, so it makes sense to just be conscientious.

There’s so much that AI is challenging in our lives. I really appreciated this unique dive into it.

What do you think? Let me know in the comments.

Thinking About Code

a man and a woman using their laptop in a bar

My fellow blogger and online friend Bernie Michalik posted today “On futzing around with code“. A key thing for me was the reminder about how much I enjoy coding. To be clear, coding is most enjoyable when it WORKS. Over the years, I’ve had a lot of fun building programs, tweaking things, and exploring how it all works.

Currently, though, I struggle with coding. It is deeply frustrating when it doesn’t work. As I step back and look, I see it’s challenging some of my deepest insecurities. Computer programming is for “smart” people, and I have some deep insecurities around this. More things to work out, I see.

So, when the code doesn’t work, it rattles those old fears, those old pains. Then I get angry and frustrated quickly, driving me to quit my project. My stubborn streak often brings me back, and I never regret coming back and getting it to work (I guess two negatives do make a positive). Figuring out these bugs makes me feel like a wizard. It’s amazing! But the downs are awful.

I think when I decided to study web application development, with the goal of launching the next part of my career there, I put a huge amount of pressure on myself. That robbed much of the fun. If every time I’m building something, I’m focused on how this will help build a programming career. When I’m in a beginners mind, curious, having fun and not concerned about the end product, coding is still fun.

Reflecting on Bernie’s post, I think I need to dive back into code, but focus on having fun. Just enjoy the work, the journey.