I just started my bot @LesbianHexbearSupercharger@hexbear.net; and it’s begun subscribing to a ridiculous amount of communities. This is important because in order for a federated community to appear in the all page one member of the local instance must subscribe to that community. Some new communities I can already see are /c/UnixPorn and /c/SelfHost. Posts might take a while to populate, though, as these are new communities Hexbear hasn’t yet seen
Thanks to @Char@mander.xyz for the advice in this thread.
Please note, hornyposters, that I’ve disabled subscribing to NSFW communities.
Must be >:D
I miss when we had the git repo full of emojis though, it always was so up to date, now we have to do guesswork to find what the latest emojis are
Yeah I have a few emoji submissions that never got added because I submitted them while the site was in its Albanian bunker arc, called like :corbyn-gamer:, :smut-busters: and :bipartisanship: and a few others
Maybe I should resubmit them or something
Unleashing us on even more of lemmy
in order for a federated community to appear in the all page one member of the local instance must subscribe to that community
Holy shit this is an important caveat.
So… To maximise hexbear reach, it is beneficial for Hexbear to maintain an account on foreign instances which subscribes to all Hexbear comms, ensuring that the foreign instance receives all Hexbear content. Let’s call these accounts embassies. @CARCOSA@hexbear.net
Honestly this should be explained to all instance owners and maintenance of embassy accounts should be a common practice. This is one thing Hexbear should encourage instance owners to do, and doing so will earn some good will.
When we federated I did that on the largest instances on our allow-list, I thought smaller ones should have the choice to opt-in
Make an account there and search for it. Actually, you could just use their search bar without logging in.
