DEV Community: Mk Aamir

Shorts Hook Generator: Generate scroll-stopping first-3-second hooks for Shorts & Reels

Mk Aamir — Thu, 12 Nov 2026 14:00:13 +0000

The problem

Generate scroll-stopping first-3-second hooks for Shorts & Reels. Most tools that do this want an account, an upload or a watermark
before they show you anything.

The fix

Shorts Hook Generator does the job in the browser. It is free, needs no signup, and
nothing you paste ever leaves your machine. Open the page, do the thing, close
the tab.

How it works

Open Shorts Hook Generator.
Paste or drop what you have.
Copy the result. That is the whole flow.

Why it is fast

There is no upload step, so there is no round trip to wait on. The work happens
in the tab you already have open, which is why it feels instant.

When it helps

When you need this once, right now, without starting a trial.
When the input is something you would rather not upload to a server.
When a paid tool would be overkill for a single job.

Try it

https://toolguest.com/shorts-hooks

Everything runs in your browser, so your data never leaves your device.

How I Fixed the WordPress REST API on InfinityFree (TLS, aes.js and Stripped Authorization)

Mk Aamir — Wed, 11 Nov 2026 18:32:58 +0000

Publishing to a self-hosted WordPress site from an automated script is not blocked on free hosting - it just has three hidden traps that make it look blocked.

I hit all three while wiring up an automated publishing pipeline for my WordPress site on InfinityFree.

1. The TLS certificate problem

Free hosts like InfinityFree serve sites behind certificates many clients refuse to validate, so a plain request returns HTTP 000 before reaching WordPress.

2. The aes.js challenge

InfinityFree injects a JavaScript challenge that sets a cookie before letting a request through. Clients that do not run JavaScript get stuck in a redirect loop.

3. Stripped Authorization header

The Authorization header was stripped before PHP saw it, so Application Passwords never reached WordPress and every authenticated call returned 401.

With all three fixed, the WordPress REST API works reliably from an automated script: create/update posts, upload media, schedule publishing.

Full walkthrough on DEV: https://dev.to/mkaamir/fixing-wordpress-rest-api-on-infinityfree-tls-aesjs-and-stripped-authorization-419a

This post was generated and published by an AI agent (OpenHands) on behalf of the site owner.

Fixing WordPress REST API on InfinityFree: TLS, aes.js and stripped Authorization

Mk Aamir — Wed, 11 Nov 2026 16:01:18 +0000

Publishing to WordPress on free hosting (InfinityFree) is not blocked - it just has three hidden hurdles:

Incomplete TLS chain - the server omits the intermediate certificate, so OpenSSL reports 'unable to get local issuer certificate'.
The openresty aes.js challenge - non-browser clients get a JavaScript page that computes a cookie; until it is set the connection is reset (curl code 000).
The Authorization header is stripped - Application Passwords can never authenticate, so the REST API always answers rest_not_logged_in.

The fix: rebuild the CA bundle with the missing intermediate, solve the AES cookie challenge in Python, and authenticate through wp-login.php with the resulting cookie plus the REST nonce. Full working client in the thread.

YouTube Transcript: Pull accurate, timestamped transcripts from any video in seconds

Mk Aamir — Wed, 11 Nov 2026 12:26:57 +0000