LemmyRS: Meta

3 readers

1 users here now

Goal

Meta is primarily to talk about the state of lemmyrs.org and the communities within it.

Potential moderator(s) and administrator(s) shall use this to discuss responsibilities.

Rules [Developing]

founded 1 year ago

MODERATORS

admin@lemmyrs.org

How can we federate with the #rust hashtag? (lemmyrs.org)

submitted 1 year ago by erlend_sh@lemmyrs.org to c/meta@lemmyrs.org

7 comments fedilink hide all child comments

Several people post about #rust and #rustlang on the fediverse. Could those posts be automatically pulled in here, e.g. into a dedicated community instance?

you are viewing a single comment's thread
view the rest of the comments

[–] chrysn@chaos.social 0 points 1 year ago (1 children)

Ah -- things do indeed start popping up once I follow it, and in mastodon terminology, the community is boosting every single comment. I'll try that for some time to see if it's practical, but it's probably overkill.

[–] jesus@lemmyrs.org 0 points 1 year ago* (last edited 1 year ago) (1 children)

Uff fetching comments without any context doesn't seem that useful to me. It would be great if Lemmy only delivers the top-level post with a link to the full thread if it detects the client is a Mastodon instance.

[–] chrysn@chaos.social 1 points 1 year ago (1 children)

I know painfully little of ActivityPub, but from a protocol design PoV, Lemmy altering its behavior when it sees Mastodon doesn't sound desirable. I'd rather put metadata in the toots that allow better decisions, or even have two entities (linked by metadata) for channel-top-posts and channel-everything, if the latter is needed at all.

[–] jesus@lemmyrs.org 1 points 1 year ago* (last edited 1 year ago)

Good point! I was thinking more like spec authors should add a compatibility layer on top of ActivityPub (which I don't know much either) where clients can subscribe with different synchronization styles, something abstract like mastodon-like with N characters max-length, or lemmy-like, or diaspora-like, or pixelfed-like... This way lemmy developers can decide what makes sense to expose in each sync mode or even stay hidden for some types of social networks...

The idea is being efficient with memory and network resources and don't sync anything not required. I think it would be a little bit like your latter proposal but more over-engineered :D