TenForward: Where Every Vulcan Knows Your Name
/c/TenFoward: Your home-away-from-home for all things Star Trek!
Re-route power to the shields, emit a tachyon pulse through the deflector, and post all the nonsense you want. Within reason of course.
~ 1. No bigotry. This is a Star Trek community. Remember that diversity and coexistence are Star Trek values. Any post/comments that are racist, anti-LGBT, or generally "othering" of a group will result in removal/ban.
~ 2. Keep it civil. Disagreements will happen both on lore and preferences. That's okay! Just don't let it make you forget that the person you are talking to is also a person.
~ 3. Use spoiler tags. This applies to any episodes that have dropped within 3 months prior of your posting. After that it's free game.
~ 4. Keep it Trek related. This one is kind of a gimme but keep as on topic as possible.
~ 5. Keep posts to a limit. We all love Star Trek stuff but 3-4 posts in an hour is plenty enough.
~ 6. Try to not repost. Mistakes happen, we get it! But try to not repost anything from within the past 1-2 months.
~ 7. No General AI Art. Posts of simple AI art do not 'inspire jamaharon'
~ 8. No Political Upheaval. Political commentary is allowed, but please keep discussions civil. Read here for our community's expectations.
Fun will now commence.
Sister Communities:
Want your community to be added to the sidebar? Just ask one of our mods!
Honorary Badbitch:
@jawa21@startrek.website for realizing that the line used to be "want to be added to the sidebar?" and capitalized on it. Congratulations and welcome to the sidebar. Stamets is both ashamed and proud.
Creator Resources:
Looking for a Star Trek screencap? (TrekCore)
Looking for the right Star Trek typeface/font for your meme? (Thank you @kellyaster for putting this together!)
view the rest of the comments
I have zero blocked communities, 11 blocked users, and... the entire lemmy.ml instance. :-)
I don't feel like I'm missing anything at all important.
To be fair, having an instance blocked means you have a lot of communities blocked as well.
Strangely enough, the way that PieFed implements that, in the manner opposite of Lemmy, I see no content from Lemmy.ml users anywhere across all of Lemmy, yet I do oddly have access to those communities still:-). They are not entirely empty, but definitely far more so than the original, having only posts and comments from people on other instances contributing to them:-).
I like this approach much better actually.:-)
Daym, I need to get some of that pie.
It's not fully ready yet, for someone who does not have an early adopter mindset, but it's coming, and I'm able to use it as my daily driver already (with frequent fall-backs to Lemmy when I need something that PieFed hasn't implemented yet).
I just heard that Andrew got a fork of Thunder working for PieFed. So... that will be helpful to see coming to the main branch at some point:-). ⚡
That's because you see the content posted there by people from instances you're federated with and that you haven't blocked. Perfectly normal behavior.
If their instance was to block yours then you would only see the content posted by people from your own instance on theirs (as far as I understand from my experience with what l can see on Beehaw).
For a function that says "Block everyone from <instancename>", PieFed's ability here does remarkably exactly and precisely what it says that it will.
In contrast, Lemmy's "block instance" does not block either the users or domains (the term that Mbin and PieFed use to refer to URLs originating from an instance), and instead might be better termed a community muting.
Though so few people use PieFed (it's not ready for mainstream yet) and so many here use Lemmy, that the "expectations" are stilted towards what Lemmy offers by default, even as misnamed as it is (although iirc the Sync and Connect apps for Lemmy can also do a true instance user block).