I'll be posting a series of posts showing the lifecycle of different berries.
Today, I'm starting with the blackberry. I hope you enjoy it!
#nature #life #photography #amazing #blackberry #fruits #berries #photo #photos #beautiful
| pronouns | she/her |
| avatar source (ty) | https://www.treasure-prizes.com |
| header image | https://www.discogs.com/artist/2437594-Lets-Pretend |
I'll be posting a series of posts showing the lifecycle of different berries.
Today, I'm starting with the blackberry. I hope you enjoy it!
#nature #life #photography #amazing #blackberry #fruits #berries #photo #photos #beautiful
6) The security model is two-fold
* At the instance level, 2 instances being "federated" means for every user on instance A, if any user on instance B is following them, that instance A user will be included in the public timeline on instance B (the "fire hose"). The same is true vice versa.
If A has "silenced" B, users on A can still follow, read, interact with users on B, but the B users will not be included in the public timeline on instance A automatically.
If B has defederated from A, no user on B can use that instance to follow, read, interact with any user on instance A in any way. You can think of this as blacklisting an email domain.
** At the toot level, you can mark a toot's privacy as being
public (fair game for the fire hose),
Unlisted (not advertised in the fire hose, but non followers can view them from boosts, direct links, or from your profile),
Followers only (non followers will not see them), and
Direct (basically DMs, but with an arbitrary number of users, as few as 1!)
4) Try to find a Mastodon instance that fits your vibe and whose code of conduct you agree with. Your home instance is kind of the people you would be interested to read even if you aren't following them. But there's nothing saying you can't switch or have alternate accounts.
5) screencap quoting and copy/paste quoting is generally considered passive aggressive or malicious. Use the boost (to get through^W^W^W) feature. If you don't want the original author to know what you have to say in response... Maybe don't say it? Use the reporting system to highlight abuse and bad actors.
Want to start a thread aimed at #newbies coming to the Fediverse during the #twittermigration
This will just be some protips to aid your integration.
1) understand that a lot of people already here left the "bird site" with some trauma or baggage. Try not to bring Twitter drama here, or at least tag it with a content warning
Remember also that there is already a culture on the fediverse that differs from Twitter's.
2) Use content warnings gratuitously! There's lots of things that trigger people, and it's a kindness to give them the option to engage or not. Common CWs might include politics, religion, mental or physical health. Check your instance's code or rules for other specific topics
3) along with that, you can mark images as sensitive, which displays them blurred until clicked on. Generally it's polite to do this for pics that represent the same kind of topics that tend to get CWs, but also try to do this for pics that feature direct eye contact
Welcome, birdsite refugees!
I'd like to link the guide made by @[email protected] and particularly highlight the section on choosing an instance: http://guidetomastodon.com/
I'm happy to provide more context as necessary, but as a new parent, I have a limited timer/attention for any given train of thought, so have to explain in chunks lol
@upthorn I think so, but not trivially (for me). The main thrust is that the archive only stores the IDs of your followers in ./data/following.js and ./data/follower.js . You would need to load the contents of those files and use that as the basis for something like fedifinder to iterate over. And you'd still need to get a twitter api key.
It's a really good question/point, and if no one has already started working on it, I might give it a crack, but obviously can't promise any results, lol. At the very least, it would be fairly simple to generate a list of usernames and parse out the fields that fedifinder searches for instance info, then scan over those manually