Just passing through.
I think in some ways Mastodon is better suited - if you use the list feature actively there, it gets quite powerful. And personally I quite like the way content gets community curated on Mastodon once you follow enough people.
I love Mbin, but scratches a very different itch. :)
I think support for boosts is a game changer for interoperability. As a Mastodon user I wouldn’t really want to follow a community even if it was well implemented, but I’m happy to follow users who boost content I’m interested in.
Boosting content is the way posts spread on Mastodon. If anyone follows me from Mastodon they will see all the content I boost; if they enjoy it, they might re-boost to their followers and the ball starts rolling. And that’s how you suddenly get comment sections where Mastodon users are actively participating.
Though luck, they are interpretations already and have been doing it since the beginning.
The first comment I ever made to a Lemmy community was via Mastodon - that’s how I found out about Lemmy in the first place.
Thanks! I haven’t seen that site before. Happy to see PieFed on the rise!
Yeah, it’s a site dedicated specifically to Lemmy. So Mbin and Piefed are not counted, neither is Mastodon or any other service. :)
I feel like dark theme is often tricky on different monitors - If the font is too heavy it’ll look awful, if it’s too light it might look bad on low resolution displays. Combined with different colour contrasts on different screens, and it gets really difficult to know what people will end up seeing.
The headline - “MBIN SERVERS” - looks great on my 4K monitor, but slightly less good on a worse one. The same goes for the text stating that “Also view servers on FediDB and Fediverse Observer”, but it’s not so bad for the white text. The hyperlinks, however, might suffer from a lack of contrast with the background (a slightly too dark blue) combined with very thin text on low resolution monitors.
I guess brighter hyperlinks could also benefit the names of instances.
It’s not something I ever noticed myself when using the site, but keeping it in the back of my head while looking at it I can see why some might have some problems with it. :)
!dadvice@lemmy.world is there right next to !bellyexpansion@lemmynsfw.com at [9.6, 38.3]. I guess someone is excited about their wives being pregnant. :)
As other people say, it’s easier to let the plants do the job for us.
That said, check out vertical farming if you’re not familiar with it. It’s a modern approach to farming that very much relies on plants, but dramatically reduces problems such as excessive land use and dependence on pesticides.
Going to mastodon.social and searching for 5teverin0@pxlmo.com in the search field, I see posts going back to August 21 just fine from there. So it’s not clear to me what is not working?
Federation of post is not retroactive - if you search up yourself from another instance you should find your profile, but you might not see your old posts. If you follow yourself, all future posts will be federated.
Thanks for the response! I’m sorry to hear that a core contributor vanished like that. Hopefully (s)he’s allright and just needed to delegate time differently. And as long as there’s at least two of you who feel somewhat dedicated to the project, even if you cannot always be active, that’s great. :)
It reminds me of the old proverb that if you want to go fast, walk alone, if you want to go far, walk together. If Mbin can continue at a sustainable pace, where you’re not afraid to take time off when you need it, I have no doubt it can go far. :)
How do you feel about Mbin in that regard? Do you feel like development is in a healthy place, with not too much of a burden on any one person?
I guess similar situations as the one described here could occur, with an inherited code base and all it entails.
Yeah, very fair. I’m lucky enough that the things I use Mastodon for has more or less established communities there.
The federation of comments is a huge headache. Intuitively it makes no sense the way it’s solved - if I go to the comment section, I don’t want a bunch of it to be randomly hidden from me. It’s something that just needs to be solved better, even though we’ll always see slightly different things as not all content is equally welcome everywhere.
I’m happy Lemmy works better for you though! I think it might just be a better format for nerd stuff. I like Mastodon for many things, but this is where I go to embrace nerd stuff. Politics here are more insufferable than at the Mastodon instance I’m on though. ;)
Sad, but mostly awful that the project has gone down in such a messy way. That sounds like a tremendous personal load that was completely uncalled for.
Sounds like… uncomfortable business? :)
More seriously though, couldn’t a.gup.pe help with discoverability? Tag a larger group, and the post is automatically forwarded to a lot of servers and shown to a fair share of users.
But yeah, bring on a smaller fedi server for microblogging has obvious drawbacks that people tend to brush over. It does require more effort to become discovered.
It’s a poster design, not a logo. It doesn’t need to be as instantly recognizable. Putting one or three other in the background would make it a lot less visually interesting.
Amazing!
The pace and responsiveness of development in PieFed is unlike anything I’ve seen before. It’s a brilliant platform, thank you so much for developing it!
Thanks! Just checking it out quickly made me discover !films@fedi.video, which seems to be a great repository of public domain feature length movies from the old days. Wonderful! 🍿
I don’t mind proprietary software - it seems it’s what a lot of people want, and I simply won’t use it.
Promoting proprietary software named “OpenSomething” should, however, be banned as false marketing.
If I understand correctly, there’s a central pump running behind the scenes in any AT implementation. You feed content into the central hub, and it pumps it out to everyone connected to it. Bluesky itself provides the one major pump that feeds its network right now.
So in that sense, Bluesky is a centralised network with decentralized users.
Frontpage is building a different pump, spreading different kind of content to a different type of platform. So there’s no obvious connection between the Bluesky pump and the Frontpage pump - that’s why they’re talking about bridging in the post.
It almost seems a bit silly - in order for two AT hubs to talk, you need to build a bridge for them. At that point, you could might as well have built an AP protocol and made it work with Bridgy.fed.
Furthermore, all “instances” running Frontpage would process data through the same central hub. If that goes down or they run out of funding, it’s all over.
I’m applauding the Frontpage crowd for trying something new. But I’m not entirely convinced I see the benefit compared to what we’re doing over here.