patrick.net

Please everyone do use the flag link to mark comments that are obviously personal.

Patrick,

Could you add, below the comment box, a quick summary of the html tags and other formatting tags that you accept?

Could you use a more subtle watermark on memes? The big white banner on the bottom is a bit much.

Thanks, I agree it's jarring if the meme background is dark.

I'm not great with graphics, but would like to make the banner the same general color as the meme to not stand out as much. I don't know how to do this yet.

yawaraf says

Patrick,

Could you add, below the comment box, a quick summary of the html tags and other formatting tags that you accept?

@yawaraf

OK, did that. How can I make it prettier or more useful?

Thanks. I like it.

For visuals I might surround each tag with the angle brackets or separate the with commas.

Allowed html tags: <a> <b>
Allowed html tags: a, b, blockquote

Also add them to the edit comment page.

Use the title tag to show the user a short explanation when holding the mouse over it.

<span title="bold">b</span>

Clicking on the tag inserts it together with the closing tag, if necessary. If text is selected, then the tags are put around the text.

Bonus if you can somehow, for each tag, link a page that give a full description of the element. I wouldn't know how to do that without cluttering the page.

Stout says

Could you use a more subtle watermark on memes? The big white banner on the bottom is a bit much.

@Stout

OK, now I'll just print the "selected by patrick.net/memes" on the bottom of the image itself instead of adding a white banner. This text will sometimes get blurred by the image itself, but sometimes will work fine, eg:

You might want to make preparations to move PatNet to the dark web.

I'll keep this site going one way or another.

Do we have a Completely Retarded Thread?

Not sure where to post this one:

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.