i think any features that flesh out the 'other half' of the fediverse implementation will be a benefit. if this is a popular feature on mastadon, it sounds like a great way to add value to mbin for that audience.
Ok, cool. I was torn whether a new page would be better or to improve the existing microblog page. In any sort that is not "newest" it would not make sense to include boosts, likes, comments, etc. within that page.
When creating a new page I can also try to save the position one was in so it does not reset on a reload
I think a combined view is what people have been asking for, this sounds like a filter on the combined view of sub to me.
I guess it's a bit different if you're wanting to show comments as well. That sounds difficult to do in UX to make the context of a reply make sense, not sure how Mastodon does it, I guess there aren't super complex tree structures? Because the comment they could be replying to could have nothing to do with the original post, you have to show the entire tree some times
I meant everything together, yes. The big thing I mean is that it is a timeline, so strictly chronological and there are events like "someone you follow liked x" or "someone you follow boosted y". And that comments from people you follow appear there as well, like they do on mastodon
I'm still interested personally in fixing the search. Eg. I try to copy and past your mbin url from this thread, into my instance. It I won't give any result. Unless I remove the last 'Mastodon-like-timeline' section from the URI. And try to search again.
I'm still interested personally in fixing the search. Eg. I try to copy and past your mbin url from this thread, into my instance. It I won't give any result. Unless I remove the last 'Mastodon-like-timeline' section from the URI. And try to search again.
I think you only have to add the optional slug parameter to the ap route 🤔
generally when a magazine does not exist on a server you search for @ magazinename @ instance.tld without the spaces. There is a good chance that the server requires you to be logged in when pulling in a new magazine. If the magazine already exists you should go to the "Magazines" tab and search for the magazine there
I know that there are tools to export/import the community and magazine subscriptions.
I believe that's only between lemmy <-> lemmy as there is no import implemented in Mbin currently
I haven't heard of anyone migrating successfully between the two. Usually the most important thing is the instance private/public keys remaining the same. It was possible for /kbin instances to migrate to Mbin as the keys were kept the same so all other instances considered it the "same" instance according to activity pub. I'm not sure if that would be possible lemmy -> something else, but encryption is outside my knowledge (whether all AP instances use the same type of keys or it differs between software).
There is also the planned software Sublinks which says it will be a drop-in replacement for lemmy. I tried searching their github / old posts and couldn't find whether they would support mastodon, just what they have on their site: "Embracing the fediverse, it supports the ActivityPub protocol, enabling interoperability with a wide range of social platforms." But if they do plan on it, it might be easier to hop to that when it's available as it's specifically being made as a drop-in replacement so I imagine there will be migration docs available, but like I said, no idea of the timeline of that.
@mozz Hey mozz, hope you're doing well! I just wanted to try to get in contact about PR453. I had mentioned that we think we're good with it and just hoping to get your OK to merge
This is something that is on the "roadmap" (meaning I have it on my mind). There is a github issue here for it. I have not been working at it for some time, because other more pressing matters came up, but we know about the issue
this is it exactly. the software should implement all the protocl pieces, and allow local admins to decide not only what is shown, but what is federated.
devs shouldnt be making that call.
i think up/down counts will start to make sense when people further understand the nature of the systems they are logging into. i would prefer not to create a technological solution to that ignorance.
and although its extremely unpopular, if we want reddit-like volumes of users were going to have to think about reputation points/karma. i think i just felt lemmy.world shudder
In principle each instance could keep a running total to be added to the global total.
Consider the purpose of the votes: it’s a popularity contest for ranking within a timeline. Does the community on instance X want their timeine rankings to be influenced by votes by instance Y (which could even be prone to shenanigans)? A tiny instance might want external votes, in which case it should ask other instances what their totals are. But if an instance reaches a certain amount of activity, then external votes are actually pollution that makes scores less accurate/relevant with respect to the views of that particular community. E.g. the solar punk instance does not benefit from votes of those on a right-wing instance like hexbear.
@BentiGorlich I personally want upvotes and downvotes of threads posts to be public to everyone on every instance, and count of favourites of microblog posts to be public only to followers.
Mbin Dev
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.