Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. General Discussion
  4. New Fediverse features that actually aren't new

New Fediverse features that actually aren't new

General Discussion
3 2 6
Log in to reply

Feed RSS
New Fediverse features that actually aren't new

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • julian@activitypub.spaceundefined

    Cursed hack to fix Mastodon-Threadiverse communication

    Technical Discussion threadiverse mastodon hack
    5
    2 Votes
    5 Posts
    20 Views
    julian@activitypub.spaceundefined
    @trwnh@mastodon.social oooh that's interesting. I actually commented on the former. But I am realizing now that NodeBB actually explicitly addresses quite a few people because we try to keep everybody in the loop. Responding to a topic with hundreds of posts could mean a Note object with hundreds of individual users addressed in cc. Perhaps it's wiser to not assume "addressed? generate notification.", and instead have configurable notifications based on thread/context participation.
  • julian@activitypub.spaceundefined

    FEP-f15d: Context Relocation and Removal

    Technical Discussion activitypub fep threadiverse
    6
    2 Votes
    6 Posts
    36 Views
    julian@activitypub.spaceundefined
    Hi @silverpill@mitra.social right; Move and Remove are explicit actions concerning membership of a context in an audience. Update is overly broad and receivers would have to infer audience change based on what the updated object contains (e.g. Audience Y is suddenly missing, and Z is new, was this always the case?) It is likely that sending audience as an array will not be correctly interpreted by existing software, so this property is an unreliable indicator of context audience membership at best Existing threadiverse apps check addresses, and audience may not be used at all in some. There is no conflict with Move(Person), and I have not heard a convincing reason to adopt a new activity type when these two AS activities work quite well to describe what we want to accomplish.
  • jupiter_rowland@hub.netzgemeinde.euundefined

    @Jasper Burns

    General Discussion cwfediversemeta quotepostdebate quotetootdebate fediversegroups fediversemeta quotedshares quotetweets quoteboosts
    6
    0 Votes
    6 Posts
    10 Views
    jupiter_rowland@hub.netzgemeinde.euundefined
    @Jasper BurnsPermissions, part 3: At contact levelLet's go one level further down. The second level of Hubzilla's permission system is per contact. On Mastodon, that'd be those whom you follow.If Mastodon was like Hubzilla, you'd have the possibility to create permission templates which you can then assign to those whom you follow. (Hubzilla calls them "contact roles", by the way.)Like, you could make one template for those whom you really trust. You grant all permissions in that template.Then you could make one that's more privacy-oriented. You only grant permission to send you toots, fave and reply to your toots and send you DMs.In theory, you could also make one for those whom you absolutely must follow, but whose toots you don't want. In this one, you only grant permission to fave and reply to your toots and send you DMs. This, however, only makes sense on something that works like Facebook, something like Hubzilla, where you can only confirm follow requests by also following back because connections are always mutual by default.Then you could go to your list of followed accounts. And you could edit and configure them, one by one. You could choose which of these permission templates is assigned to them and thereby what you allow them to do. While you're already there, you could also, for example, add them to lists or remove them from lists.There's one catch, though: If you grant a permission for your whole account, you automatically grant it to everyone whom you follow. You cannot forbid one of your followed something your account generally allows. So if you want to be able to choose whether someone is allowed to do something or not, you must not allow it for your whole account, and instead, you must allow it followed by followed.(streams) and Forte make things a great deal easier than Hubzilla, by the way: They don't require such templates anymore. Instead, when you go edit a contact, you'll see one on-off switch for each permission, and you can turn each permission on or off right there, right then (provided it isn't inherited from the channel). You still have such templates, but they only serve to grant the same set of permissions to a whole lot of contacts without having to click single permissions on or off for all of them.(7/9)#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions
  • fediforum.org@bsky.brid.gyundefined

    Have you heard of the #Threadiverse, and important part of the #Fediverse?

    Uncategorized threadiverse fediverse
    1
    0 Votes
    1 Posts
    14 Views
    fediforum.org@bsky.brid.gyundefined
    Have you heard of the #Threadiverse, and important part of the #Fediverse? If not: Julian Lam (@julian@activitypub.space) is coming to FediForum next week and will talk about: Threadiverse improvements. Join us!FediForum