❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

How AI Fuels the Web Security Goldrush

25 October 2026 at 11:39

AI has quickly become a key tool for the modern web. Developers, web hosts, and site owners are adopting it to reduce costs, increase efficiency, and serve customers (we can debate the merits of the last one).

AI is also taking a lead role in security research, with people and organizations analyzing code for vulnerabilities. That makes sense, as an AI model can find potential issues faster than a human. It’s also a tool developers can use while building – making the web safer for everyone.

We’re already seeing the fruits of this virtual labor. Recent WordPress security releases have found and patched issues with AI’s help. The WordPress plugin directory’s “Protect the Shire” initiative looks to catch plugin security holes before they are released to the public.

That’s all impressive. However, it feels like we’re only in the beginning stages of AI-assisted security. So, what does it mean for web professionals? And will this brave new world make our jobs easier? Or could it all backfire on us?

Let’s attempt to answer these and a few other important questions.

AI Makes the Connections Humans Can’t

It stands to reason that AI can identify common patterns of vulnerable code. Training a model on PHP or JavaScript documentation should mean it “knows” which functions are potentially dangerous.

The more surprising feature is AI’s ability to make seemingly unrelated connections. By itself, a particular code snippet may not be problematic. But combine it with another (or two or three more), and you might get a different result.

Think of it as one of those futuristic scenes in your favorite crime drama. You know the drill: a character uses a computer to track down a criminal at light speed and zero obstacles. AI isn’t quite that fast, but a few hours of scanning does the job.

We’ve seen cases where such detective work found vulnerabilities that existed for years. Humans reviewing the same code the old-fashioned way didn’t see the connection. A large language model (LLM) puts the puzzle together with relatively little effort.

AI is demonstrating its value for this type of work. That’s good, because malicious actors are using the same tools to do the reverse. We’ll need tools to identify problems as soon as possible.

AI excels at identifying security flaws that humans miss.

Battling Information Overload

Researchers are using AI to uncover a record number of security vulnerabilities. Bug bounty programs that used to receive a few dozen reports a month are now seeing hundreds or more. That’s both a good and bad sign.

On the bright side, every patched security flaw is a positive thing. No one wants their app to be less secure, after all. More security means more peace of mind. Or does it?

The side effect is a deluge of security warnings. Companies and individuals are holding up every single issue they find, as if to say, “Look at this! We’re all doomed unless you buy x, y, and z!”

The reality is that no two vulnerabilities are the same. Some will be more severe and more likely to be exploited. Indeed, the random connections AI makes can mean an attacker needs to follow a very specific (and unlikely) set of steps to do real damage.

Regardless, all bets are off when an issue becomes public. Hackers will know (or can easily find out) how to exploit the vulnerability. From there, product makers rush to develop and deploy a patch.

This leaves the rest of us to wonder what’s an emergency and what can wait. It also makes freelancers and agencies afraid to ignore their email. What if our security plugin finds a critical issue?

The number of security flaws discovered by AI is on the rise.

We Need Smarter Ways To Manage Web Security

Even the most attentive web developers will struggle to keep up with the pace of security disclosures. Rarely does a day go by without another big doomsday flaw dropping.

The traditional workflows for everyday agencies and freelancers aren’t enough. Automated updates offer speed, but don’t guarantee safety or stability. Besides, how do we protect our sites from the inevitable undiscovered AI-built threats?

Here’s hoping we find smarter ways to manage security threats. We need help to make sense of all the information out there. A mechanism to quickly apply patches and minimize exposure would also be welcome. Some of these things already exist – but they must be applied at scale.

These issues could be resolved at the hosting level. After all, hosts are the closest point of contact for a website. Content delivery networks (CDNs) like Cloudflare could also help with a seamless mitigation strategy.

The bottom line is that AI has fueled an explosion of security discoveries and potential attacks. Freelancers and agencies can’t handle them alone. Help!

The post How AI Fuels the Web Security Goldrush appeared first on Speckyboy Design Magazine.

Are Browser-Based Apps Enough for Web Designers?

13 September 2026 at 19:09

Setting up a new computer is something I look forward to (make fun of me if you want). There’s something about reading the specs and knowing you have a more capable tool at your disposal. It feels like I’m improving myself as much as my business.

Historically, part of this ritual includes installing a ton of apps. I add the requisite Adobe design tools, the Microsoft Office suite for productivity, and a host of other software. Apps for email, FTP, media conversion, and a local web server environment remain staples.

My current system is now a few years old, and I have dozens (hundreds?) of these apps. They still serve their purpose. But it recently dawned on me that most of what I use could be replaced by a web browser. That will likely mean fewer apps to install on my next computer.

These are words I never thought I’d utter. My web design career began before the first release of Netscape. As such, I’ve had a love/hate relationship with browsers. For every benefit, there have been limitations and quirks to deal with.

These days, you can do pretty much anything within your chosen browser. That got me thinking: are traditional design apps still relevant? Should we abandon them for browser-based tools? I’m not so sure, but let’s figure this out together.

Modern Web Apps Break Boundaries

It used to be that most browser-based apps were inferior to their desktop counterparts. Common workflows like text and media editing felt clunky and minimally useful. I used them in a pinch and usually came away frustrated.

Meanwhile, desktop powerhouses like Excel, Photoshop, and Dreamweaver were infinitely more flexible. They were built for those who care about quality and require high-level functionality. Such professional-grade tools have always been worth the cost.

That narrative has been turned on its head by a combination of more powerful web standards and server technologies. There are now online video editing platforms that can produce top-notch results. Design tools like Figma make it easy to create and share interactive mockups. Google’s suite of productivity tools offers all the bells and whistles without compromise. Even Photoshop has an online version these days.

Collaboration might be the biggest selling point of all. You can keep clients and colleagues in the loop with minimal effort. This improves efficiency and saves us from the never-ending email chains of yesteryear.

And the appeal of these apps goes beyond functionality and convenience. They’re also cross-platform and device-agnostic. It used to be that you’d need a desktop app built specifically for your operating system. Using a browser means it works on Windows, Linux, macOS, Android, iOS, and more.

Then there are the hardware requirements. Granted, you should still have a system with plenty of memory and a modern graphics processor. However, having a massive hard drive isn’t necessary when storing files in the cloud.

The old boundaries of software have vanished. Doing all the things within a browser isn’t a chore like it used to be. And these apps may be enough for most web designers.

Browser-Based Apps are now powerful enough for professional use

Trust and Content Ownership Are Concerns

Software is always an investment, regardless of how you access it. There are also privacy and security risks to consider. Browser-based tools often amplify those concerns.

Companies like Adobe and Microsoft have some level of tracking within their desktop apps. And they do connect to the internet. So, this is nothing new. But working in a browser opens up a different (or, at least, a bigger) can of worms.

For instance, cloud storage is quite convenient. But what happens if the provider gets sold or goes out of business? Will you lose access to your data? Are policies in place to maintain account security in the event of a breach or server crash? The answers aren’t always clear, and you may not find out until something bad happens.

Then there is the matter of artificial intelligence (AI). It seems like every tool on the planet has an AI integration of sorts. How are these features used on your content? Does the provider train their models with your work? Could your sensitive information become exposed online?

Working online also opens you up to third-party tracking. It may be something relatively innocent, like an analytics suite. But ad networks and similar companies could be watching you – and there is no guarantee they’ll abide by the rules.

These are important questions to answer when thinking about your (and your client’s) data. Again, desktop apps aren’t immune to these issues. But an online app that shows up overnight deserves an honest assessment. The risks could far outweigh the benefits.

Privacy and security can be tradeoffs when using online tools

Desktop Apps Are Still Relevant When Control Matters

It’s truly amazing to see how far web technologies have come in the past decade. You can see it in both commercial and open-source software. Functionality once reserved for powerful desktop devices can now exist in the palm of your hand (and with responsive design, for that matter).

I still believe there’s a tradeoff, however. The work-from-anywhere tools we use have plenty of benefits (provided you really do want to work from your lawn chair). But you lose a measure of control along the way.

There’s something to be said for storing files locally (with routine backups, of course). Not to mention the ability to customize an app’s layout or tool set to match your workflow. There’s a level of personalization you don’t seem to get in a browser.

The reality is that you don’t need desktop software for every purpose. There are plenty of online tools that will do the job. But there are scenarios where these old-school beasts make sense.

For example, I can’t imagine Disney making their next hit movie solely within a browser. And web designers who want full control of their workflow might want to keep a few items installed on their hard drives. I know I will.

The post Are Browser-Based Apps Enough for Web Designers? appeared first on Speckyboy Design Magazine.

How to Work With Your Client’s Next (Or Previous) Developer

25 August 2026 at 11:20

Building and managing websites for clients is challenging. Sure, there are technical and financial obstacles to work around. You’ll also find that you’re managing client personalities. And, despite our best efforts, some clients will leave for greener pastures. But it works both ways. Sometimes, you’ll be on the other end of the spectrum, with a client leaving their previous developer for you.

I’ve experienced both scenarios. Sometimes, there’s no rhyme or reason why clients come and go. You can do everything right, and still a client looks elsewhere when it’s time for a redesign or new project. Perhaps they were swayed by a sales pitch. Or, a new person comes in and wants to shake things up. It’s an unfortunate part of this business.

Regardless, there’s still work to be done. Their website may need to be migrated to a different host. Credentials need to be created for the new freelancer. There are project assets and notes to share.

It’s an awkward situation at best. But never fear, I have some tips for making the transition as smooth as possible. Keep reading to learn the do’s and don’ts of working with that new (or old) developer!

Keep It Professional

Maybe it sounds obvious. However, it’s easy to become emotional when letting go of a project (and its revenue). The same thing applies when you’re the new developer. Some clients will paint an unfortunate picture of their previous agency. Don’t get caught up in it.

Odds are, neither you nor the other party is evil or inept. There are always two sides to a story, and you’ll probably only hear one of them.

As such, there’s no reason to be rude or unhelpful. Answer questions, document processes, and respond within a reasonable period of time. These are common courtesies that will speed up the transition. After all, no one wants this thing to drag on for too long.

The funny part is that you may encounter the same developer again. For example, I’ve gained and lost clients to the same local agency. It’s a reminder to keep it professional and avoid burning bridges.

We may be competitors, but we’re all in the same boat.

Put aside your feelings and be professional.

Get Paid Before Doing the Work

These transitions can be especially frustrating if a client owes you money. They may expect you to work with their new developer with a promise to pay later. Avoid this scenario at all costs!

A client who is always late with payment is unlikely to make good on their debt after you’re gone. As such, getting paid should be a condition for transferring the site to someone else.

Create an agreement (in writing) that outlines what you need from them before you can do the work. Don’t provide a single file or login until that condition has been met. This places the ball firmly in their court. If they want to move on, they’ll need to settle their outstanding debt. It’s a perfectly reasonable request.

If the client balks at the idea, you may need to bring a lawyer into the fold. It’s not ideal, but it may be the only way you’ll get your money.

Ensure that your client has paid their outstanding invoices before providing assets to another developer.

Think Before You Share Sensitive Information

Sharing credentials is part of any website transition. There are logins for hosting, content management systems (CMS) like WordPress, and third-party SaaS applications. Not to mention API keys and software licensing details.

You may be tempted to send a laundry list of logins to the new developer. However, it’s worth taking a step back and ensuring you aren’t exposing yourself to risk.

If you manage a client’s hosting or domain name, for example, be sure that anything you share is specific to their website. You wouldn’t want someone to have access to other client data. If possible, create delegate accounts that provide only the necessary permissions.

Also, create a new administrator account for their CMS, rather than sharing your login. This takes you off the hook for any user activity or, worse yet, a hacked password. And make sure your account is deleted when you’re out of the picture.

Software licensing can be tricky, especially if they aren’t under your client’s name. If you have a developer license for a WordPress plugin, consider your comfort level with allowing a client to continue using it. It might be worth recommending they purchase a separate license.

If you’re inheriting the site from another developer, think about what you’ll need. Ask about all of the above and find out as much as you can. The goal is to avoid any surprises once you take over.

Don't share your credentials with anyone - even new developers! Create a separate account instead.

Transitions Are a Part of the Job

It’s safe to say that no one enjoys transitioning a website from one developer to another. It’s often a messy process and can raise your anxiety levels, regardless of which side you’re on. But there’s an opportunity to make the best of a difficult situation.

Maintaining a professional attitude is a must. Treat it as just another business transaction and do your best to leave personal feelings out of it. Work with integrity and aim to produce the best possible outcome.

It’s also important to protect your interests. A client who’s leaving must live up to their end of the bargain. Don’t allow them to walk away without paying their outstanding balance. Also, be careful about the information you share with a new developer.

The most positive aspect is the experience you’ll gain. Learning to manage clients coming and going will serve you well. Doing so will allow you to focus on the task at hand while avoiding all the negatives. That’s great, because you’re likely to need those skills again and again.

The post How to Work With Your Client’s Next (Or Previous) Developer appeared first on Speckyboy Design Magazine.

How Low Will You Go for a WordPress Project?

7 August 2026 at 09:50

Booking projects is a challenge for every new WordPress agency. So, you often take what you can get. That includes low-revenue and otherwise unappealing gigs. Everyone has to start somewhere, right?

That tendency fades as you build your business. You move on to the bigger fish in the pond in an effort to make more money and expand your reach. Any small fish left in your portfolio could potentially hold you back from leveling up.

Even so, you’ll still hear from potential clients who want you to take on their small project. Or you might be asked to undercut a competitor’s price on a large WordPress site. Either way, it may lead to mixed feelings. How should you respond?

Established agencies don’t need to take every project. It’s worth considering where you draw the line, however. How small is too small? Does a lower upfront cost mean there’s no potential for future profit? And, is it ever worth taking on a large project for a bargain price?

These are important questions to ask as your business evolves. Let’s explore the pros and cons of “going low”. We’ll also share some tips for determining the minimum requirements for accepting a project.

Does the Project Offer Any Additional Benefits?

Money is an important part of any project (we all need to keep the lights on and the AI tokens flowing). However, there are other potential benefits. That may be enough to make a small or heavily-discounted project worthwhile.

For example, consider working with a charity or other non-profit organization. These clients are often bootstrapped and have a limited budget. As such, the project is more about doing good than making a big profit. This is both a source of pride and something you can use in your marketing efforts.

Likewise, some projects can open the door to a specific industry or clientele level. If you don’t have experience in the enterprise WordPress space, offering a discount could increase your chances of booking the gig. You exchange a bit of money for prestige in your portfolio. Proving your worth to one such client could make others take notice.

This won’t be the case for every project. There will always be clients looking to cut costs however they can. Others won’t have the resources to work with your agency. Still, some opportunities are beneficial beyond money.

Some lower cost projects are opportunities to break into a new market.

Consider the Potential for Future Profit

Just because a project starts with a smaller profit doesn’t mean it has to stay that way. There is usually a path to increasing your revenue in the long term.

Maintenance packages are a great vehicle for keeping clients in the loop while creating dependable income. WordPress requires routine software updates, security monitoring, and hosting. Clients may also want to add new features as their website evolves. These are all things you can and should charge for.

Such recurring revenue is important for every agency and freelancer. New projects are harder to come by, and budget-conscious clients may be wary of spending big on redesigns. Maintenance and related subscription services improve your business’s sustainability.

This strategy also mirrors what we see in other industries. Clients are acquired with a lower starting cost, while the “real” money comes in the form of future services.

Book enough of these arrangements and you won’t be as susceptible to the boom/bust cycle of new design and development projects. Note that this is part of a bigger plan, rather than something to do on a one-off basis. So, think about how it fits into your business before making a decision.

Future maintenance needs can increase project revenue.

Find the Price Point of Diminishing Returns

Every agency should have a minimum project price. This helps you avoid losing money and gives you more room to focus on your goals. But how do you determine that number?

You could come up with an arbitrary amount. Some agencies won’t touch a project for under $5,000, for example. It sounds reasonable. However, you still risk losing money on the proposition. It’s better to study your workflow and resources before setting a minimum.

The first consideration is the cost of taking a project from start to finish. Time spent on design and development is a part of the equation. But don’t forget about client communication, the revision process, and testing. Commercial theme and plugin licenses can also be a factor.

If your agency has employees, think about who will do the work. Their salary counts toward the ultimate cost. You might also consider where else they could be spending their time. For instance, will a small project take them away from a bigger one?

The same thing applies to solo freelancers. Lesser projects don’t always mean less work. They can overwhelm your calendar and take time away from your top clients.

Don’t leave it to guesswork! Set a minimum price based on facts. The result should be a profit margin you’re comfortable with.

You'll have to do some math to determine a minimum price for your projects.

Accept WordPress Projects That Are Worth Your While

Experience will help you determine which projects to accept and which ones to turn down. Yet, there’s value in digging deeper before deciding. There could be more to the story than you think.

Some projects offer long-term benefits that are easy to miss. You may find opportunities to stabilize your agency via recurring revenue. They might also be a gateway to establishing a new niche. In some cases, it’s worth taking a leap of faith.

Understanding the time and resources involved is key to the decision-making process. This will put you in a position to say “yes” or “no” with confidence. You’re also less likely to experience regret after the decision!

Take time to figure out what makes the most sense for your business. That will free you to move onward and upward.

The post How Low Will You Go for a WordPress Project? appeared first on Speckyboy Design Magazine.

Cherish Your Tokens, Grumpy Designer

26 July 2026 at 09:24

In case you didn’t notice, it’s getting more expensive to ride the AI bandwagon. Web professionals are using the technology to do more than write code. We’re also employing it for just about every other task you can think of – even the most mundane ones. Tools like OpenClaw are taking our usage to new heights, literally. I mean, did you look at your latest bill?

Seriously, some of us are spending something close to a BMW’s (or perhaps a Ferrari’s) monthly payment on AI. What started as a small monthly fee to use ChatGPT, Claude, or Copilot has turned into something completely different. We have become the proverbial kids in the candy store.

It’s a bad case of consumerism fueled by our desire to experiment with new toys. It doesn’t help that AI companies are making it easy to spend significant money without a second thought. Integrating with your favorite SaaS or even WordPress is easy. Yet, the virtual cash register silently rings with each prompt and automation we create.

Perhaps all of this is happening too fast (maybe that’s the intention). We may be falling into an AI-powered trap that will be difficult to escape.

The Grumpy Designer likes to keep things rational. So, let’s hit the brakes, take a step back, and analyze what we’re doing. We’re the only ones who can stop the insanity, after all.

Your Monthly AI Plan Isn’t All-Encompassing

The early days of AI (a whole 2-3 years ago) were exciting. I had fun playing around with ChatGPT and seeing what silly or productive things I could accomplish.

Its coding abilities may pale compared to what we have today. But it was still incredibly handy for troubleshooting and building basic WordPress plugins. I decided that their $20-per-month Plus plan was a relative bargain. It offered access to the latest models and improved performance.

And it’s still a good deal, if you use it in your browser or their app. An individual performing occasional coding, image generation, or file analysis will get a lot for their money. It’s once you step outside of those boundaries that things become costly and confusing.

Such monthly plans typically don’t provide you with API access. For that, you’ll need to purchase tokens. It’s a common practice across the big AI companies.

I won’t argue with the premise of token-based usage. AI requires a lot of computing power to do its job. It must provide quick and accurate answers to user queries. Then there is the cost associated with training and improving each model.

The real problem lies in educating consumers on the differences. It’s not until you need an API key that you realize your monthly plan won’t cover you.

Monthly AI subscriptions typically don't include API access.

How Much Will That Task Cost?

Generating an API key and connecting your favorite AI model to a third-party service is simple. Figuring out how many tokens you’ll need isn’t so clear. That’s the downside of not having a good/better/best pricing model.

Reputable AI companies let you set spending caps and disable auto-purchasing once you hit your limit. This will save you from a massive bill. It’s also a good security measure, should your API key fall into the wrong hands.

However, experimentation is the only way to understand the costs of using AI tokens. Figure out what you want to do, ask AI to do it, and check your account dashboard to see how much you spent. The trick is to extrapolate that cost based on how many times you’ll perform a given task.

The other challenge is that some tasks will use more tokens than others. For example, generating a headline for your blog post will likely cost less than generating a featured image. Thus, you’ll want to watch your token usage carefully.

Setting a small spending limit may be fine for light-duty tasks. That strategy won’t work for organizations with multiple users who are highly dependent on AI, though. You’ll quickly run out of tokens and will have to go without the service or set a higher limit.

It appears that companies are beginning to realize that willy-nilly usage of AI is costly. Some will narrow the scope of what these tools do for them. It’s also an argument for developing local AI models. Maybe we still need humans after all?

You'll need to experiment with tasks to see how many AI tokens they use.

Put AI in Its Place

Sure, AI can do just about everything. But the decision on when and how to use it is ours to make. The increasing and uncertain token costs are reason enough to scrutinize every task. Some of what we’re doing may not be worth the price.

There are other benefits to being less reliant on AI. Fewer tokens spent means less electricity (and less pollution). The environmental impact is real and only getting worse as more of us employ these models.

It’s also an opportunity to stay connected to our humanity. Imagine all the knowledge we might lose if we cede every task to machines. There is also the potential to lose personal and professional relationships. Do you want to trade that for efficiency?

All of this makes me want to treat tokens as something to spend wisely. From now on, I’ll ask myself: Is this task tokenworthy?

The post Cherish Your Tokens, Grumpy Designer appeared first on Speckyboy Design Magazine.

How Consistency Benefits Your WordPress Agency

6 July 2026 at 12:30

Starting an agency is like a grand experiment. You book a few projects and feel the rush of building something from nothing. You also learn some lessons about working with clients and managing money.

Then, just as you think you’ve figured it out, things become hectic. Your to-do list grows faster than you can complete tasks. Unexpected events, such as a broken site, force you into a panic. How will you ever keep up with the demand?

Hiring another developer or project manager can help. However, that’s not always feasible. Budgets only stretch so far.

This is where consistency swoops in to make life easier. By creating processes for getting things done, you’ll have proven steps to take. Better still, you can improve them as you go. The result is better efficiency and less chaos in your day.

The great thing is that you can make a process for just about anything. Tasks like design, troubleshooting, and even client communications are on the table. You can even personalize them to match your needs.

So, how does it work? We’ll show you a few examples of processes that will bring consistency to various parts of your business. Let’s get started!

Start With a Theme and Plugins You Trust

The design-and-build process starts with your chosen theme. Many themes tend to cater to a niche or try to be everything to everyone. The first option isn’t ideal for working with clients in different industries, while the latter may be too bloated and complex. Neither is right for scaling at an agency level.

Look for a theme you can use as the foundation of every new project. For example, starter themes offer handy features without an opinionated design. This flexibility lets you take the design and functionality anywhere you want to go. And there are options for both classic and block themes.

It’s also worth sticking with the same page builder plugin across the board. There are several on the market, and it’s tempting to try them all. But every tool has a learning curve. As such, you’ll spend too much time figuring out how things work instead of getting things done. Using multiple page builders also complicates future maintenance. Not to mention juggling several commercial licenses.

This approach extends to plugins that handle forms, SEO, e-commerce, and other common functionality. Using a set of preferred tools on your projects can lead to more predictable outcomes. Efficiency and expertise come from repeated use.

You’ll reduce friction throughout the project’s lifecycle and always have a solid starting point.

Using a trusted theme means you have one less thing to worry about.

Create Processes To Organize Your Business Tasks

The more clients you have, the more you’ll benefit from organization. Using different billing policies, contract formats, or communication methods becomes messy. The right tools and processes can help you clean things up.

It’s time to simplify. Examples include limiting your maintenance fees to tiered packages, using a single app for billing and invoicing, and storing client information in a customer relationship management (CRM) app. The more you can consolidate these tasks, the better.

Client communication is another area where simple is better. Using email is fine if you have a small client roster. However, a ticketing system can make it easier to keep track of messaging. You could use an outside service or install one on your WordPress website. Take things a step further by designating times of the day for replying.

We can’t forget about your to-do list itself. Project management can be a nightmare without organization. Plenty of apps exist for staying on task, or you could vibe code your own. The point is to know where you stand with each project and have an archive of notes to reference as needed.

Since WordPress is our specialty, you might consider using it to build an admin portal. The free and low-cost options are budget-friendly, and you can tie everything into a single package. Imagine not having to visit multiple sites or download a bunch of apps to run your business!

A project management app will help you keep track of deadlines.

Trust the Process

Creating consistent processes will turn your agency into a well-oiled machine. Doing things the same way and using the same tools allows you to focus on your clients. That’s a growth path you can’t build if you’re bogged down with menial tasks.

You can also pass this knowledge to new employees and contractors. It keeps everyone on the same page and avoids confusion. Onboarding becomes easier, and work happens faster.

Get started by examining how you work. Look for pain points and complicated tasks that you dread. Think about where you spend the bulk of your time.

The post How Consistency Benefits Your WordPress Agency appeared first on Speckyboy Design Magazine.

❌
❌