Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MA
Posts
59
Comments
679
Joined
2 yr. ago

  • Unfortunately it is still not enough. There have been many instances of people using these licenses and still corporations using their software without giving back, and developers being upset about it.

    And unfortunately there are no popular licenses that limit that. I've seen a few here and there, but doesn't seem to be a standard.

  • It is a matter of responsibility. If you can log into any lemmy instance or mastodon server with the same account, then which server takes responsibility for your actions in the fediverse?

    This is a good point and I should clarify: in this model, you wouldn't get open access to any instance. The instance has to explicitly trust (white list) instances from which it will accept log ins. It would be like federation is done today, but the lists would be separate ideally.

    Another model is it could do it on a case-by-case basis on the user level instead of instance level. But it would still enable the user to keep their dame ID and original domain.

  • This is a very valid concern and I should clarify a bit about the mechanism I have in mind.

    An instance admin can decide which instances it federates identities with, similar to how regular federation is done (but maybe these would have separate lists)

    So, in your case, you would only federate identity with instances you trust to have done proper vetting. It wouldn't be by default that having a federated instance means you have access to login the entire fediverse.

  • It will be yes! Right now I only have it locally and its messy, but the idea is like this:

    • Your home feed allows customizing the sorting algorithm. There's a sensible chronological-based algorithm, but you can customize it more.
    • Content is organized into feeds.
    • By default, you have your own personal feed similar to a micro blogging platform.
    • but you have the ability to have multiple feeds. For example, maybe you're into both technology and wood working, but not all followers are interested in both. So you have separate feeds, and users can follow one or the other.
    • A feed isn't only for one person's posts. For example, I might maintain a woodworking feed, but I'd "share" posts from other wood workers. In essence, I am a sort of "content curator". I pick out the good woodworking content and put it in a single feed for you to follow!
    • A feed can be like a Lemmy community or a Facebook Group. So it can allow multiple posters, it can be open to anyone to post, or it can be approval-only (but submitted from anyone). It can also be private or public (though that's a low priority feature)
    • A feed can use another feed as a source / baseline. This might mean that you get all the other feed's posts, but maybe you as the maintainer filter it further, or add some of your own. Or you can use multiple feeds as the source, so maybe there are multiple good wood working feeds and I like them all, so I combine them

    In my opinion, this replaces automated algorithms with manual curation. It also replaces moderation, as you might like a community but wish it was differently moderated, there might be another feed that sources the first feed but with extra moderation!

    The project is still in its infancy and I don't get too much time to work on it. But since you're interested, I'll try to get it into an open source-able state (albeit far from workable) and let you know when I do!