Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

I meant, post the image of your comment on Reddit so that the automod can't block the text.

Doesn't actually matter. You can have HTTP URLs that bounce to content on the lemmy.dbzer0.com instance through other Fediverse instances, including both kbin and lemmy instances. For kbin, it's an "/m/" prefix for "magazine", and for lemmy a "/c/" prefix for "community".

https://kbin.social/m/[email protected]

https://lemmy.ml/c/[email protected]

Every time someone adds a new Fediverse instance, it creates a new instance that can be bounced through.

Here's a list of lemmy instances:

https://lemmy.fediverse.observer/list

And kbin instances:

https://kbin.fediverse.observer/list

People have been adding them quite quickly over the past few days.

Also, there are URL shorteners and all that sort of thing that can make it harder to block content via doing redirects in case they start doing something like doing a substring search on URLs for anything containing lemmy.dbzer0.com. I imagine that you scurvy scalawags of /r/piracy are probably more-familiar with what Reddit blocks in that area than I am. Might be a good idea to mix that in, just to discourage them trying to block large chunks of all of kbin/lemmy with the rationale that they're trying to block you pirate folks from linking others to your pirate fortress.

EDIT: A bit more experimentation shows that whatever you guys have set up and however lemmy normally works, it apparently can be reached, albeit with a warning thrown up about a bad cert, via the IP address:

http://167.86.124.45/

This opens a number of interesting doors for linking to your outlaw port.

Unless the Reddit blocking code has fully-conformant-to-procotol parsing of IP addresses -- and very, very few software packages do -- it probably isn't capable of reducing IP addresses in URLs to a unified format. However, the web browsers that users use normally have a fairly-robust implementation and probably can understand such interesting formats. And IP supports representations in other numeric bases. Here's a handy base calculator:

https://www.rapidtables.com/convert/number/base-converter.html

So, for example, we could throw a little hex (base 16) in there with a leading "0x":

http://167.0x56.124.45/

Maybe make it interesting by doing a little octal (base 8) on top of that, with a leading "0":

http://0247.0x56.124.45/

Maybe merge the last two octets there...124*(2^8)+45=31789, so:

http://0247.0x56.31789/

A quick test also shows that aside from the cert warning in Firefox, it looks like your lemmy instance is fine with serving up your instance content to any browser that reached you having any hostname that maps to your IP. If any of you guys have any domains anywhere and can add an A record to it that points at 167.86.124.45, you can link to your lemmy instance via that hostname. If you get an actual cert for that hostname and throw it up on the server, and if whatever the server infrastructure for your lemmy instance is supports multiple certs -- I have no idea, haven't looked at it -- then you can probably even get rid of the cert warning.

I can probably throw you some other ideas if they start cracking down on those. Feel free to ping me.