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. This is how the new Loops app Notifications screen looks like.

This is how the new Loops app Notifications screen looks like.

General Discussion
8 3 0
Log in to reply

Feed RSS
This is how the new Loops app Notifications screen looks like.

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

    Hello fediverse 🥳

    Uncategorized activitypub loops tiktok
    1
    1
    0 Votes
    1 Posts
    0 Views
    loopsundefined
    Hello fediverse 🥳 https://blog.joinloops.org/loops-joins-the-fediverse/ #loops #activityPub #tikTok
  • Matthias Pfefferleundefined

    where would you expect quotes to show up in #WordPress ?

    Fediverso wordpress fediverse activitypub
    16
    0 Votes
    16 Posts
    0 Views
    Pelle Wessmanundefined
    @pfefferle Something inbetween a classic pingback / traceback and the same presentation as a normal “retweet” / “retoot” / “share”I don’t think it should appear as a comment as it isn’t a directly reply to the post, it’s merely a mention / sharing of itIt could chronologically appear among the comments, but like pingback / traceback and such it should not appear as a style of a comment.And if one shows the number of shares a post have gotten, then a quote should for sure increase that one.
  • Box464undefined

    I thought Mastodon's quote post controls were extensive...these are "boundaries" that can be set in Bonfire for your posts.

    General Discussion bonfire activitypub
    2
    2
    0 Votes
    2 Posts
    4 Views
    Bonfireundefined
    @box464 we started drafting a section on "how do boundaries federate" in this document: https://docs.bonfirenetworks.org/boundaries.htmlThe short story is we interoperate with Mastodon's newly introduced canQuote and and GoToSocial's canReply/canLike/canAnnounce for general boundaries like only follows can reply or everyone can quote, and for everything else it's enforcement at the level of your instance (e.g. "basically just drop replies you don't want"). Feedback on that and on the docs as well is more than welcome!
  • julianundefined

    FEP 11dd: Context Ownership and Inheritance

    Moved Fediverso fep activitypub
    9
    0 Votes
    9 Posts
    47 Views
    julianundefined
    trwnh@mastodon.social Yes you're right, some messiness is bound to happen. I'm not trying to force all implementations into a specific inheritance pattern, that's why it's a "should", not a "must". Even then one of my concerns is that while in an ideal scenario, everybody inheriting their parent context leads to an entire collection all referencing the same context... in reality a lot of messiness will occur, objects will reference other contexts all over the place, etc. At the end of the day it's best effort, and if we are able to handle all that and still get to a point where backfill is achievable, then that's a win in my books. > it depends on how much you embrace the idea of each publisher being allowed to make their own claims (and how much you allow "clean up" after the fact) Part of me would like this to not happen, but it is unavoidable.