this post was submitted on 27 Jul 2024
105 points (99.1% liked)

Fediverse

28380 readers
1909 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
ruud@lemmy.world
Xylinna@lemmy.world
MrCenny@lemmy.world
TragicNotCute@lemmy.world
automodbeta@lemmy.world
woelkchen@lemmy.world
105
What do you want to have in a Lemmy instance? (ponder.cat)
submitted 3 months ago by PhilipTheBucket@ponder.cat to c/fediverse@lemmy.world
94 comments fedilink hide all child comments
 

I started up my own instance and now I have realized that there's no reason anyone would join mine instead of any other instance.

That's no good. What neat stuff would the Fediverse like to see in a Lemmy instance?

  • Follow RSS feeds in your Lemmy feed? I have that already, in a way, but it would be nice to be able to do it for any feed automatically without it being clunky.
  • Follow Mastodon users? Or tags?
  • Embedded video? That seems costly.
  • Hackability? The ability to run your own customized front end? Or good scripting features in the browser console?
  • A better looking UI? This one is functional but it's not pretty.
  • Better moderation? I have heard the Lemmy tools aren't that good.
  • Something else?
you are viewing a single comment's thread
view the rest of the comments
[–] PhilipTheBucket@ponder.cat 2 points 3 months ago (1 children)

The pondercat rss bot can already do that. You can create a community that gets posts from any number of RSS feeds.

Well, you can't, but I can. I don't want to make it available for anyone to use yet, because I don't want an explosion of RSS spam, but if you want to connect some RSS feeds to a community and it's not going to become obnoxious, I can do that for you.

Hackable front ends, I think, could be a huge deal. I don't know how easy that is, but if it's possible for someone to run a modified version of the frontend just for them out of a subdomain, without it being a security nightmare, that would solve a lot of these issues of wanting an extra button on the report page, but having to have it go from you to the site admin to Nutomic back to a code update to a PR and back down the chain and so on, before it can get done.

With some web apps, that's easy, and Lemmy's frontend and backend are already nicely separated. I don't know if there have to be privileged things running in the frontend, though. I looked at it just now but I couldn't completely sort out how realistic it is. That might mean it's not very realistic.

[–] maegul@lemmy.ml 2 points 3 months ago (1 children)

The RSS not seems cool! Is that open source some where?

[–] PhilipTheBucket@ponder.cat 2 points 3 months ago (1 children)

It is not, partly because it is still rough and just written, and partly because I'm scared people will start blasting RSS spam everywhere and it will be my fault.

[–] maegul@lemmy.ml 1 points 3 months ago (1 children)

partly because I’m scared people will start blasting RSS spam everywhere and it will be my fault.

That is fair. Might be worthwhile talking to instance admins and core devs about how best to make use of it? Putting it behind some admin approval or administration might be the best way.

There was an instance a while back that was dedicated to something similar. Their system was to define the feeds themselves without any real user input, and it never really took off.

Maybe a dedicated instance that provides more user control but is also set up to control and limit things could go a long way? One basic control might be limiting usage to user accounts older than a certain threshold. lemm dot ee does this for image uploads (4 weeks minimum age).

[–] PhilipTheBucket@ponder.cat 2 points 3 months ago

That is fair. Might be worthwhile talking to instance admins and core devs about how best to make use of it? Putting it behind some admin approval or administration might be the best way.

That's a good idea. And then, if it turns into a mess of botspam, it's not my fault.