• 12 Posts
  • 62 Comments
Joined 2 months ago
cake
Cake day: July 18th, 2024

help-circle




  • Due to his advanced age, Jonathan spends his days doing almost everything with his mate, including eating, sleeping and mating.[13] The sex of Frederica, one of two of his favourite tortoises thought to be female (the other being Emily), as well as his companion since 1991, was cast into doubt in 2017 when island veterinarian Catherine Man indicated that due to a deformity of its plastron its sex could not be verified,[4] and is now known to be male, being renamed Frederik.[1] While Frederik was undergoing the examination, Jonathan came over and did not leave the side of Frederik and the veterinarian during the entire process.







  • It is and I could. I’d be fine doing it, but why not just read them when they come up in !fediverse@lemmy.world? I’ve been trying not to create communities that are going to be duplicates or spam, or split the user base between one way of reading articles and another way of reading articles. Do you want it as a DM, maybe?

    I think an even better way would be software that can follow the original Wordpress feed, if they have one, but Lemmy can’t do that right now.


  • PhilipTheBucket@ponder.catOPtoFediverse@lemmy.worldFollow RSS feeds from Lemmy
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    Not a problem at all. I think a better way to do that will be to let moderators of existing communities add the bot to their existing communities. Someone asked about doing that, and it’s easy to set up the bot to make it possible, so I think I’ll just do that instead. I don’t need to create a duplicate community for anything that’s already got one.

    I’m fine with the existing structure, with one community per periodical. I tried !coding_blogs@rss.ponder.cat and !science_streams@rss.ponder.cat and it looks like some people are into that type of structure, but I’m thinking mostly in terms of one-periodical communities or moderators from off-instance communities being able to add things.

    Are there any that you would cherry-pick that you think you would personally use? I’d be perfectly willing to add them, if so.



  • PhilipTheBucket@ponder.catOPtoFediverse@lemmy.worldPaywall content for rss.ponder.cat
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Than there is problem with I don’t trust media will write the truth anyway, so giving them few bucks will probably not change that. But it is important for us to know what other people know.

    Are there any media sources that I’m hosting feeds for which you feel that way about? I think the problem is much worse in a lot of free content, and I’ve been trying to bring in honest and high-quality sources when I’m adding news sources.

    While this is outside of our current discussion, they need to find better model.

    If it is a daily newspaper, maybe paywal new articles and release after sone reasonable time (like a week, or month… or a year).

    I don’t understand, can you explain more?

    Edit: I understand now. That’s outside the scope of my abilities… I would like to be able to offer a paid subscription with a deal that provides access to a wide variety of paywalled content, like a site license at a university, but I think that’s also outside the scope of my abilities. You’re right that they need a better model.

    I like your idea of separating feeds, to keep paywalled content out of my feed.

    It seems like a good compromise. I certainly understand that if someone’s decided not to read paywalled content, putting a lot of it into their Lemmy feed in a way that’s difficult to disable isn’t a good thing to do. I think separating the paywalled content into a separate user so it’s easy to block is probably a good pragmatic solution.







  • I completely agree. Maybe my phrasing was careless. I wasn’t trying to be critical of the pace of accepting PRs or anything. I only meant that I think more flexibility in the frontend would help, instead of needing any minor UI change to go all the way through a cycle all the way up to you, incorporating it into the core codebase, and then filtering back down to an upgrade by the instance admin. But please don’t take it as blaming you for any of that situation. I was raising it in the effort to propose a solution and also to advocate against people just complaining about the moderation tools and then moving on, and waiting for you to make them happy.

    I did look at the backend plugin system PR, although sadly not enough yet to have any opinion or feedback on it. I do think a frontend plugin system, of sorts, could help a lot. I’m not sure when I will have time but I will try to put together something on this instance to show what I’m talking about, and if I do wind up doing it and it’s well received, I am completely open to putting it together as a fixed-up and official PR for the main codebase.




  • This is a very good idea. Slashdot hit on something very good with their scoring and moderation system, and then the lessons were forgotten in the systems that came after Slashdot.

    There are so many small tweaks like this tagging idea that would improve things, that I think the way to do it is a frontend “plugin” system that can accommodate them without it being a big fandango of tweaking the core to include fifty of these little nubbins all over the codebase.

    Nothing that’s ordained from on high will ever be completely perfect. If you can have a little text box on your custom frontend, where you can tweak your own UI features, and then talk with the instance admin about importing one of those little tweak plugins for the whole site, or for your own community only, that sounds like a huge step forward to me. If you’ve ever added little tweaks to Wordpress, with the custom CSS boxes or by adding a few lines to functions.php, I envision this being similar.

    This is all much more ambitious than I was thinking of when I asked this original question, but it would be a lot of fun to work on. If the result was it going back up into Lemmy, and each instance having its own collection of tweaks and a thriving community of people working on them without needing to disrupt the pace of development on the core, that would be a pretty excellent outcome.



  • It’s not absolutely safe against bots and sockpuppets, but it surely makes it more expensive than even a $10/account membership.

    I think, sadly, that either sending in your national ID or paying $10 would be unacceptable to so many people that it would make it a lonesome failure of an experiment. I’m on your side about the idea, but I think people would just take the path of least resistance and create their sockpuppets on some other instance, and your main accomplishment would be driving away legitimate users.

    PIxelfed is still just supporting ActivityPub. I’m talking about multi-protocol communication. A smart client should be able to let you communicate with Lemmy communities, subreddits, Facebook groups and all types of different platforms from a single unified interface. There are plenty of people that think this is something undesirable (like everyone that wants instances to block Threads), but I’d argue that building these integrations with closed platforms would eventually destroy them because they would lose the monopoly on network effects.

    I get it. Aren’t there projects that are working on that? Friendica and Emissary? Adding integrations with closed-source networks to those isn’t too hard. At that point, it’s not its own web app anymore, though, more akin to an email program. It’s a good idea but it’s different than what I had in mind. You will also have to deal with API limits or terms of service and legal issues, once you start looping in the closed-source networks.

    No, but you could have a web server that responds to multiple domains. Ideally, the server listening and responding to the AP requests should be able to work with multiple “virtual servers”, instead of having to have only one instance == one domain that we today. AFAIK, only Takahe does this for microblogging.

    Yes, that part’s not overly hard. I’m already doing virtual servers for ponder.cat and rss.ponder.cat, to run them both on the same VPS, and I’ll probably add more virtual servers for development of frontend tweaks if I keep going with Lemmy. Some of the ideas I had in mind for hackable frontends involved wildcard virtual servers to serve people custom “instance” sites off a subdomain that’s different from the actual actor ID instance name.

    What I’m saying is that if someone’s actor ID from the POV of the rest of the Fediverse is still https://ponder.cat/u/rglullis, and ponder.cat goes down, nothing that either ponder.cat or any new instance can do, can “catch” requests that are being directed to that actor ID. You have to make the actor ID either https://rglullis.com/u/rglullis or https://rglullis.sometrustedthirdparty.com/u/rglullis from the beginning, and arrange for ponder.cat to be handling any traffic for those domains, so that you can switch away from the ponder.cat instance later on if you want to.

    Of course, you can tell people that they can either have a ponder.cat user, or a rglullis.com user if they want to buy their own domain for their user, and they can have an actor that will be transferrable from ponder.cat to any other Lemmy server that supports the feature. It wouldn’t work with current Lemmy, but in theory it could be made to work, if someone were willing to make the right Lemmy changes. It would be tough but it might be worth it.

    Overall I think it might be better to address the same issue at the protocol level as some other federated social media networks do, so you’re not introducing crazy new requirements on both the server and user experience side in order for people to be able to transfer their users later.