iso

joined 2 years ago
MODERATOR OF
[–] [email protected] 2 points 1 month ago (2 children)

@[email protected] I hope this works for you :)

[–] [email protected] 2 points 2 months ago

I reset statuses every few months for a re-check. Other than that, there’s no mechanism specifically for this case.

[–] [email protected] 2 points 2 months ago

Interesting but potentially useful feature. I'll have to think about where to squeeze it in :)

[–] [email protected] 2 points 2 months ago (3 children)
  1. In order for an instance to follow a community in another instance, both must be registered in lemmy-federate.

  2. If an instance has the "auto add" feature enabled, newly created communities will be added automatically within 1 to 5 minutes. This process is automatic. No action is required from an admin/moderator/user. You can see this from instances page.

  3. If "auto add" is not enabled, any user can add that community manually. If not added, lemmy-federate will not work for that community.

Off topic, no need to apologize this much :)

[–] [email protected] 2 points 2 months ago (2 children)

I tried it and it works as of now. But it could be timeout, rate limit or something else. I'm thinking of showing the errors on the management page (or with Grafana). I created a task for this. Then you can see what kind of problem you're having.

[–] [email protected] 5 points 2 months ago (5 children)

Lemmy Federate doesn't do anything special. It searches and follows communities just like normal users do. The only difference is that it does this from every (registered) instance, for almost every community. The reason I didn't explain it in more detail is that it has evolved into an admin tool rather than a user tool. Generally, admins know what this tool is for.

However, I can explain a few things that will be useful for you outside of the "All" tab:

Discoverability

Lemmy Federate enhances community discoverability by allowing users to search communities from their instance. Instead of relying on an external site, you can discover new communities while staying within the context of your own instance.

Crossposts

Let's say that [email protected] is federated in your instance, but [email protected] is not. In this case, you won't see crossposts from [email protected] sharing the same link as [email protected].

Initial post count

When a community is pulled for the first time, only a certain number of recent posts are pulled with it. If you are the first to follow a community you are interested in from your instance, you will not be able to see all posts from that community.

[–] [email protected] 7 points 2 months ago* (last edited 2 months ago) (8 children)

I created this tool and have been using it in my instance since the very beginning. My instance is almost 2 years old and it’s total database size is 60.2GB.

The thing is:

  • If a community is generating enough activity, it’s likely that someone from your instance is already following that community.
  • If a community isn’t generating enough activity, it won’t create much of a network/storage burden anyway.

Sure, it will make a small difference, but it’s nothing compared to the benefits it provides.

[–] [email protected] 8 points 3 months ago (2 children)

TBH Toastify is not that awesome.

[–] [email protected] 2 points 3 months ago (1 children)

Nope. lemy.lol. With only one l, peepo logo.

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago)

I'm glad you added lemmy.ml 🙏 Yes, you just need to create a bot account and add it. Communities are added/updated periodically.

[–] [email protected] 1 points 3 months ago

If you say so. I'm a big fan of Cosmic because I'm hoping it will fill the modern, beautiful and also fast DE gap in Linux world. That's why I may have sounded a little harsh (especially since it's not even beta).

[–] [email protected] 2 points 3 months ago (1 children)

Communities on Lemmy Federate are updated every 24-48 hours. You can re-add existing communities to force immediate update. So it's a valid action.

/cc @[email protected]

 

I apologise for being in beta for the last few weeks. I didn't think it would be such a painful process. I will remain in stable from now on unless something extreme happens.

 

I think the title says it all. Basically, when a new comment appears on your targeted post, it sends you a PM about it.

@[email protected]

Usage

  • Subscribe to a post: just mention the bot in the comments or send the link to the bot via PM.
  • Unsubscribe from a post: send PM to the bot with stop text and link of the post like stop https://lemmy.ml/post/1234
  • Unsubscribe completely: Send PM to the bot and add stop text to your message. It will unsubscribe you from all subscriptions.

Note: the bot sends only one notification per post. It waits for the previous notification to be marked as read for new comments.

Made with @[email protected]'s lemmy-bot project 🙏 Tomorrow I will publish the code publicly after adding README and self-hosting guide.

 

I think the title says it all. Basically, when a new comment appears on your targeted post, it sends you a PM about it.

@[email protected]

Usage

  • Subscribe to a post: just mention the bot in the comments or send the link to the bot via PM.
  • Unsubscribe from a post: send PM to the bot with stop text and link of the post like stop https://lemmy.ml/post/1234
  • Unsubscribe completely: Send PM to the bot and add stop text to your message. It will unsubscribe you from all subscriptions.

Note: the bot sends only one notification per post. It waits for the previous notification to be marked as read for new comments.

Made with @[email protected]'s lemmy-bot project 🙏 Tomorrow I will publish the code publicly after adding README and self-hosting guide.

 

I think the title says it all. Basically, when a new comment appears on your targeted post, it sends you a PM about it.

@[email protected]

Usage

  • Subscribe to a post: just mention the bot in the comments or send the link to the bot via PM.
  • Unsubscribe from a post: send PM to the bot with stop text and link of the post like stop https://lemmy.ml/post/1234
  • Unsubscribe completely: Send PM to the bot and add stop text to your message. It will unsubscribe you from all subscriptions.

Note: the bot sends only one notification per post. It waits for the previous notification to be marked as read for new comments.

Made with @[email protected]'s lemmy-bot project 🙏 Tomorrow I will publish the code publicly after adding README and self-hosting guide.

 

I think the title says it all. Basically, when a new comment appears on your targeted post, it sends you a PM about it.

@[email protected]

Usage

  • Subscribe to a post/comment: just reply the post or comment and mention the bot. Or send the link to the bot via PM.
  • Unsubscribe from a post: send PM to the bot with stop text and link of the post like stop https://lemmy.ml/post/1234
  • Unsubscribe completely: Send PM to the bot and add stop text to your message. It will unsubscribe you from all subscriptions.

Note: the bot sends only one notification per post. It waits for the previous notification to be marked as read for new comments.

Made with @[email protected]'s lemmy-bot project 🙏 Tomorrow I will publish the code publicly after adding README and self-hosting guide.

 

Especially the errors related to traits are very difficult to me. Is there a trick? Will I get used to it? Or am I just a failure? :D

Like WTH is this?

the trait bound '(diesel::sql_types::Uuid, diesel::sql_types::Text, diesel::sql_types::Nullable, diesel::sql_types::Timestamp, diesel::sql_types::Timestamp): diesel::query_dsl::CompatibleType' is not satisfied the following other types implement trait 'diesel::query_dsl::CompatibleType': (ST0,) (ST0, ST1) (ST0, ST1, ST2) (ST0, ST1, ST2, ST3) (ST0, ST1, ST2, ST3, ST4) (ST0, ST1, ST2, ST3, ST4, ST5) (ST0, ST1, ST2, ST3, ST4, ST5, ST6) (ST0, ST1, ST2, ST3, ST4, ST5, ST6, ST7) and 24 others required for 'SelectStatement, DefaultSelectClause>, NoDistinctClause, ..., ..., ...>' to implement 'diesel_async::methods::LoadQuery<'_, _, models::Artist>

Or this:

the variant or associated item 'as_select' exists for enum 'Option<Image>', but its trait bounds were not satisfied the following trait bounds were not satisfied: 'std::option::Option<models::Image>: diesel::Selectable<_>' which is required by 'std::option::Option<models::Image>: diesel::SelectableHelper<_>' '&std::option::Option<models::Image>: diesel::Selectable<_>' which is required by '&std::option::Option<models::Image>: diesel::SelectableHelper<_>' '&mut std::option::Option<models::Image>: diesel::Selectable<_>' which is required by '&mut std::option::Option<models::Image>: diesel::SelectableHelper<_>'

or this:

the trait bound 'schema::image::columns::id: diesel::SelectableExpression<schema::artist::table>' is not satisfied the following other types implement trait 'diesel::SelectableExpression<QS>': <schema::image::columns::id as diesel::SelectableExpression<diesel::query_source::joins::Join<Left, Right, diesel::query_source::joins::Inner>>> <schema::image::columns::id as diesel::SelectableExpression<diesel::query_source::joins::Join<Left, Right, diesel::query_source::joins::LeftOuter>>> <schema::image::columns::id as diesel::SelectableExpression<schema::image::table>> <schema::image::columns::id as diesel::SelectableExpression<diesel::query_builder::SelectStatement<diesel::query_builder::FromClause<From>>>> <schema::image::columns::id as diesel::SelectableExpression<diesel::query_source::joins::JoinOn<Join, On>>> <schema::image::columns::id as diesel::SelectableExpression<diesel::query_builder::Only<schema::image::table>>> required for '(id, url, width, height, color, updated_at, created_at)' to implement 'diesel::SelectableExpression<schema::artist::table>' the full type name has been written to './target/debug/deps/server-25bcf4cf7c62d3bf.long-type-2030200755981097212.txt' 3 redundant requirements hidden required for '(diesel::expression::select_by::SelectBy<models::Artist, _>, diesel::expression::select_by::SelectBy<std::option::Option<models::Image>, _>)' to implement 'diesel::SelectableExpression<schema::artist::table>' required for 'SelectStatement<FromClause<table>, DefaultSelectClause<FromClause<table>>, NoDistinctClause, WhereClause<...>>' to implement 'diesel::query_dsl::methods::SelectDsl<(diesel::expression::select_by::SelectBy<models::Artist, _>, diesel::expression::select_by::SelectBy<std::option::Option<models::Image>, _>)>' the full type name has been written to './target/debug/deps/server-25bcf4cf7c62d3bf.long-type-3023492822805157679.txt'

 

After a few configuration tweaks and lemmy builds, I was able to increase the upload limit to 100MB and the timeout to 600 seconds without any problems. I kindly ask you to use this limit only when necessary 😅

Also after the Lemmy 0.19 RC update, resource usage increased. So I upgraded the server specs to 16CPU, 32RAM and the thing has improved a bit. I hope these problems will be fixed soon.

 

First of all, I apologize for the approximately 20 minutes of downtime. I didn't expect the migration to take this long :)

The reason I upgraded to a beta version because I was curious about the "scaled" post order and also saw some instances running it seamlessly.

Since it is a beta version, you may encounter interesting bugs, please let me know if this happens.

Some changes that caught my eye:

  • Scaled sorting
  • "moderator view" to manage moderated communities
  • Instance blocking
  • "Auto expand media" option
  • Fixed 2FA installation

Clients that not working right now:

  • Mlem
  • Alexandrite
  • Eternity

Thanks to everyone who making Lemmy better 🙏

view more: ‹ prev next ›