I have a question about #activitypub :
-
@DePemig The filtering could be done on the client side. But if I were to implement this in server-to-server context, I would probably add a new property to
Followactivity, e.g.filter.Another example from the sender side: I am a music group and I would like to invite people to: "Follow #concert_announcement for @mycrazycoolband"
If filters are static, they could be implemented as groups / circles.
-
Another example from the sender side: I am a music group and I would like to invite people to: "Follow #concert_announcement for @mycrazycoolband"
If filters are static, they could be implemented as groups / circles.
This is one of the features, I want to implement with fedi-herds.
The main current obstacle for me is: How would you want to specify the filter rules? One would need to develop a way to describe filters on Objects / Activities. Solutions like Pleroma's MRF are just "let's write code".
If you want to allow users to write filters, you want a more limited DSL...
-
This is one of the features, I want to implement with fedi-herds.
The main current obstacle for me is: How would you want to specify the filter rules? One would need to develop a way to describe filters on Objects / Activities. Solutions like Pleroma's MRF are just "let's write code".
If you want to allow users to write filters, you want a more limited DSL...
@helge @DePemig For hashtags we need a way to say "give me all
Notes wheretagcontains an object withtypeequal toHashtagandnameequal totagname"There is a FEP by @mariusor that describes collection filters: https://codeberg.org/fediverse/fep/src/branch/main/fep/6606/fep-6606.md. I guess we can re-use those conventions for lists
Another FEP is https://codeberg.org/fediverse/fep/src/branch/main/fep/5bf0/fep-5bf0.md, but I think it doesn't have implementations
-
@benpate Now I think about this 10 minutes longer, this seems like something that one can be done on the client side, right?
Hey Gilles! It looks like several other *far more knowledgeable* people have already chimed in, but yeah.. this would probably be best as a filter on your client or your own home server.
I *think* Mastodon already does something kinda like this.. allowing you to filter out boosts from accounts you follow. It's a nice add that we could probably expand on.
-
@helge @DePemig For hashtags we need a way to say "give me all
Notes wheretagcontains an object withtypeequal toHashtagandnameequal totagname"There is a FEP by @mariusor that describes collection filters: https://codeberg.org/fediverse/fep/src/branch/main/fep/6606/fep-6606.md. I guess we can re-use those conventions for lists
Another FEP is https://codeberg.org/fediverse/fep/src/branch/main/fep/5bf0/fep-5bf0.md, but I think it doesn't have implementations
Oops, I was celebrating my birthday yesterday and see your replies only now. I'm a bit humbled since I have close to zero technical knowledge about the protocol. However, great to read that my question is interesting for you!
-
Oops, I was celebrating my birthday yesterday and see your replies only now. I'm a bit humbled since I have close to zero technical knowledge about the protocol. However, great to read that my question is interesting for you!
As @benpate also noted in his answer, an implementation on the client side, be it mastodon on another software seems possible (as indeed, mastodon and other softwares already allow you to follow someone's posts excluding boosts). If I may ask, @silverpill, what information or functionality could be gained by defining this on a "server-to-server" level? You could not create an hashtag that someone "owns", could you?
-
As @benpate also noted in his answer, an implementation on the client side, be it mastodon on another software seems possible (as indeed, mastodon and other softwares already allow you to follow someone's posts excluding boosts). If I may ask, @silverpill, what information or functionality could be gained by defining this on a "server-to-server" level? You could not create an hashtag that someone "owns", could you?
-
@silverpill HTTP-Signatures work for GET requests too.
From them you can extract the actor that accesses a C2S resource and determine based on the resource's recipients (to a reasonable degree) if it's allowed. No S2S required.
-
I have a question about #activitypub :
Is there a method for: Following from account xyz only post of a certain type (e.g., images) or a certain hashtag (#abcd).As an example: I would like to be able only to see the comics that a comic artist posts, but not their further opinion. (type is only image)
Another example from the sender side: I am a music group and I would like to invite people to: "Follow #concert_announcement for @mycrazycoolband"
Maybe @benpate knows about this?
on the publisher side: create an actor representing the topic you think your audience wants to follow. when the actor is a Person (the most common case), the topic is "everything this person does". probably not what you want in all cases!
on the receiving side: you can store everything you receive in some storage backend and query it. this is what fedi does. "give me all posts by x with tag y" is a query on the entire local database of syndicated posts.
-
on the publisher side: create an actor representing the topic you think your audience wants to follow. when the actor is a Person (the most common case), the topic is "everything this person does". probably not what you want in all cases!
on the receiving side: you can store everything you receive in some storage backend and query it. this is what fedi does. "give me all posts by x with tag y" is a query on the entire local database of syndicated posts.
@DePemig for publishers you can think of a blog category as having its own atom feed or activitypub outbox. in my website's static site generator (hugo) i configure a taxonomy called "streams" which output to multiple formats
each rss channel item / atom feed entry / activitypub outbox activity / etc can be attributed to some author that doesn't have to be the actor you followed. this might cause some weirdness in tracking your "following", since you never followed the author themselves.
