Lemmy is very “open” right now; some might say by design, other might say flawed. OP is maybe coming from a good place and actually wants to help, but instead of doing it tactfully, OP is becoming the exact thing they’re advocating against — a spammer posting garbage.
This right here.
Op, if you’re not ready to moderate, don’t spin up your own server or do your own private instance. If you’re going to moderate, do it properly and don’t spew bad ideas while hiding behind a dumb “alert” throwaway.
I have shared them in a separate post; though, it would appear that there are still some federation issues as the post appears to be some what de-sync on my own instance and lemmy.world. I'm also for some strange reason unable to see your reply on my own instance, hence why I'm replying with my lemmy world account instead... If you do make some more progress, please do share it with the community at large so more of us can have the setup we'd like!
Yeah, the entire setup is quite finicky still. Part of me thinks Fediverse is forced into the spotlight by Twitter (Mastadon) and Reddit (Lemmy), and the whole thing is not quite baked yet. Don't get me wrong, having a more open space is great, but there are so many things that's not quite ready for prime time. I hope the dev team behind the platform (not the self hosted instance admins) will be more open to ideas and rapidly improve the platform.
I am new to the fediverse, and I don't use Friendica, so I could be entirely wrong about this. However, from what is described, perhaps Friendica has some sort of feature in which would trigger your instance to go out to fetch some data from another instance. Someone exploited this feature, spammed your instance with content from assortment of subdomains on the *.activitypub-troll.cf domain, and most if not all of them are probably non-existent. As result of that, your server is re-checking every 10 minutes to see if they've came back online. This would also explain why shutting down the Friendica service resolved the problem for you.
Yeah, I really do think we need both:
!gaming@... or !gaming@ which aggregates [!gaming@instance.a](/c/gaming@instance.a), [!gaming@instance.b](/c/gaming@instance.b), ... etc. that I've subscribed to into a single feed; and
#gaming which I can put !gaming@..., !pcgaming@..., and !consolegaming@... into a single collection.
This way we'd get the flexibility to pick and choose what we'd want to see more easily.
Love that there’s an app to get up and running so quickly. Thank you. A couple questions/feedbacks if I may:
I’m noticing some janky/sticky/bouncy behaviour. I tend to observe this in longer posts with more comments in the thread coming in via incremental loading. Some messages tends to stick and pop back after I scroll some distance. Is this artifact of Lemmy server rather than mLem client?
I mentioned else where that aggregation of communities would be very useful. Where us refugees came from had the concept of “multi” and one could custom tailor community_A+community_B+community_C to group similar concepts together. With the decentralized nature, would it be possible to add similar setup, as well as a generic “!community@“ feed that pulls and aggregates the feed from all of my subscribed instances if “!community”? A slick UI to manage this in mLem will make it a killer feature that other apps doesn’t have, thus drive adoption :)
Some people get really excited and write huge walls of text, which results in a lot of scrolling in feeds. It would be nice to have a compact view on the feed where it just shows the title and first few lines of text, and the tapping into the thread to see the full message thread. This would make scrolling through larger quantities of posts in feed faster and easier.
Is it possible to detect if the destination of a link is a Lemmy instance/post/comment, and render that in the app instead of bouncing the user to an in app safari view? Kind of defeats the purpose of using an app if we end up just seeing the instance’s web view anyway.
Thanks again for getting an app up and running for everyone!
Are there ways to manage lists of such? For example, on the former platform that doesn't deserve a call out, you can do "me_irl+meirl" and aggregate both into one feed. This makes reading the (albeit potentially cross posted) content in a unified feed much easier.
Another similar point I'm having a hard time getting over is that with a centralized platform, it is easy to go to "Subject A", and see everything on that subject. However, now I need to see "Subject A@lemmy.world", "Subject A@lemmy.ml", "Subject A@someother.instance"... Yes, I could subscribe to them all, but this ultimately end up creating a noisy home feed with also "Subject B@lemmy.world", "Subject B@lemmy.ml", "Subject C@lemmy.world", "Subject D@lemmy.ca", ... etc. all baked into one feed, as opposed to just something focused on "Subject A".
Lastly, discoverability leaves a lot of room for desire. Today, I'm fairly new to Lemmy, I am actively seeking out communities that I might be interested in, across multiple popular instances, and hoping that federation is enabled between the two instances. Tomorrow, I'd find that I'm subscribed to too many (see the noisy main feed issue above), and I'd remove a bunch. Next week, am I likely to go to the Join Lemmy directory to find new instances, and add "duplicate" communities from newly popular instances? I think not.
I think the long term survival of the platform (to expand beyond just us tech nerds that hate the former platform) will depend a lot on streamlining this workflow to make content discovery much more consistent. Even a simple option where a pseudo "!Community@" (with no instance) feed that aggregates all the "!Community" regardless of instance that you've subscribed to, might go a long way.
Everyone has an opinion, and at the end of the day, whatever works best for you is what you should stick with.
I like Traefik because you can mount
/var/run/docker.sock:/var/run/docker.sock:roto Traefik, then it can read labels from containers, and automatically wire up new instances based on labels on them. I'm sure there's equivalent in other reverse proxy solutions, but as I said, it works for me and I like it.I give that container my Cloudflare origin certificate, everything gets encrypted in transit to Cloudflare, and then Cloudflare handles all the SSL management for me, as well as provide extra layer of DDOS protection.