@JakoJakoJako13@calckey.world @JakoJakoJako13 @nfl@lemmy.world I believe the reason Mastodon is showing “16 posts that don't populate" is because your mastodon instance isn't downloading the content for you. Did you follow @nfl? My understanding is that your instance won't fetch those posts until someone on your server is following the account, and even then it will only fetch new posts after someone follows the account, not the old back catalog. That's why you get the link to "browse more on the original profile."
awilbert
joined 7 years ago
@JakoJakoJako13@calckey.world @name@server @JakoJakoJako13 @nfl I find it easier to think of @ names as "feeds" instead of "users". This way, there's no distinction that needs to be made between "user feeds" and “place feeds” as you've described them. My mastodon account is my personal feed of content that I write. The @nfl feed is an aggregator feed that boosts out posts from the lemmy instance
@heatrunner @jpm @programming Not that I know of, but i'm sure there is somewhere. I think most of us are in the "poke it with a stick and see what happens" phase.
@jpm @programming You literally just did it! By tagging @progamming@beehaw.org, you created a new post. The replies you're getting on Mastodon are showing up as threaded replies on beehaw.
@JakoJakoJako13 @nfl@lemmy.world I agree that there are a lot of rough edges, especially when you start crossing boundaries between Activity Pub implementations. It may simply be the case that the @nfl moderators can't see your request to follow because they're not paying attention to the way the content is presented on mastodon. It's very early days in all of this, these hurdles will work their way out over time.