patrick.net

Anyone want to try to embed a Tweet?

https://www.wikihow.com/Embed-a-Tweet

1. Go to X. Find a Tweet to embed on your site.
2. Click on the down arrow icon (v). Select Embed Tweet from the drop-down list.
3. Remove the media From the Tweet (optional), if desired. Uncheck the Include media checkbox to hide media (photos, GIFs, videos) which displayed alongside the Tweet.
4. Hide the original Tweet from a reply (optional). If the selected Tweet is a reply to another Tweet, you can hide the original Tweet by unchecking the "Include parent Tweet" checkbox.
5. Copy the HTML code from the pop-up screen. Paste into your blog or website.
6. Done. Now you can see the Tweet on your website!

If it doesn't work, please email me the HTML you pasted and I'll figure it out.

Testing. 1, 2, 3..

You don’t hate journalists enough. pic.twitter.com/qQKW5ycqvf— Rothmus 🏴 (@Rothmus) August 13, 2024

Shouldn't it look like this?

I even got this while trying to post this comment:

Thanks for letting me know. I guess I'm being too aggressive against the robots.

OK, now I allow 30 requests per minute instead of only 15.

I think There should be atleast two tabs.
USA
WORLD

@patrick
People with international topic don't want to bore USA centric readers.

FarmersWon says

People with international topic don't want to bore USA centric readers.

That's just your posts, for the most part.

Patrick says

Thanks for letting me know. I guess I'm being too aggressive against the robots.

OK, now I allow 30 requests per minute instead of only 15.

Well, I am a 'power poster'. I can post per minute really fast. Probably faster than the bots.

I'm actually a bit confused as to how nginx rate limiting works. Here are the relevant lines:

limit_req_zone $binary_remote_addr zone=ratelimit:10m rate=30r/m; # 30 requests per minute, to match robots.txt "Crawl-Delay: 2"
limit_req_status 429;
...
limit_req zone=ratelimit burst=10 nodelay; # commented out in dev, uncomment in prod!

I think I'm saying create a 10 mb memory area called "ratelimit" and limit each ip address to 30 requests per minute, but allowing up to 10 requests at once and not just delaying requests that exceed that 10 to match the rate limit.

"When the 'nodelay' parameter is set, requests that exceed the burst limit will be rejected immediately with a 503 Service Unavailable error, instead of being delayed."

@Patrick

For the link to the latest images, can you add the #footer param to it?

Because it is at the bottom of the last page of them where the actual latest image is.

@DemocratsAreTotallyFucked

Sure thing, done. Though I used #last because that's more consistent with how that image thread works. Oversight on my part not to have it there to begin with.

Patrick says

DemocratsAreTotallyFucked

Sure thing, done. Though I used #last because that's more consistent with how that image thread works. Oversight on my part not to have it there to begin with.

Cool! Just tested it. Works great.

@Patrick

Tried using the font size attribute here:

https://patrick.net/comment?comment_id=2118924

But it just gets stripped out.

@DOGEWontAmountToShit

True, font size is not one of the allowed attributes:



The reason is that people could then make a post unreadable by making the font in a comment ultra-huge.

But with a bit of work, I could allow the size attribute and put a cap on it.

Patrick says

But with a bit of work, I could allow the size and put a cap on it.

Ok.

Do you have what is allowed or not in any master list? If so, can you post that here?

It would be good to know before I try to use any of them.

On the other hand, could be a waste of time as I am one of few PatNetters who actually embeds HTML in his posts/comments.

That is the master list. You can see which tags and which attributes are allowed.