It's a different type of vehicle. I don't really know why, but the EUC style of wheels lets you go basically as fast as safety concerns will allow. The good ones can go up to 40-50 mph mechanically. You're never going to do that unless you have a death wish, but the point is that if you don't need to get on the interstate or carry large things with you, it's a good distance to being a full replacement for a car, with a lot of advantages over a car.

It's not just one company that makes them. The Veteran models are supposed to be good. I know there are some providers that make ones that are awful and unsafe. It's a little bit of a wild west, but there's also a whole community of people who 3d print parts for them, make modifications, that kind of thing. It's a very dweeby community in general, so maybe that is a deal-breaker. But the reason I say they are the future is that they are fast enough to be largely a replacement for a car, and smaller and handier than a bike or scooter.

How about tlnet? I just made !tlnet@rss.ponder.cat.

I completely agree. Maybe my phrasing was careless. I wasn't trying to be critical of the pace of accepting PRs or anything. I only meant that I think more flexibility in the frontend would help, instead of needing any minor UI change to go all the way through a cycle all the way up to you, incorporating it into the core codebase, and then filtering back down to an upgrade by the instance admin. But please don't take it as blaming you for any of that situation. I was raising it in the effort to propose a solution and also to advocate against people just complaining about the moderation tools and then moving on, and waiting for you to make them happy.

I did look at the backend plugin system PR, although sadly not enough yet to have any opinion or feedback on it. I do think a frontend plugin system, of sorts, could help a lot. I'm not sure when I will have time but I will try to put together something on this instance to show what I'm talking about, and if I do wind up doing it and it's well received, I am completely open to putting it together as a fixed-up and official PR for the main codebase.

It’s not absolutely safe against bots and sockpuppets, but it surely makes it more expensive than even a $10/account membership.

I think, sadly, that either sending in your national ID or paying $10 would be unacceptable to so many people that it would make it a lonesome failure of an experiment. I'm on your side about the idea, but I think people would just take the path of least resistance and create their sockpuppets on some other instance, and your main accomplishment would be driving away legitimate users.

PIxelfed is still just supporting ActivityPub. I’m talking about multi-protocol communication. A smart client should be able to let you communicate with Lemmy communities, subreddits, Facebook groups and all types of different platforms from a single unified interface. There are plenty of people that think this is something undesirable (like everyone that wants instances to block Threads), but I’d argue that building these integrations with closed platforms would eventually destroy them because they would lose the monopoly on network effects.

I get it. Aren't there projects that are working on that? Friendica and Emissary? Adding integrations with closed-source networks to those isn't too hard. At that point, it's not its own web app anymore, though, more akin to an email program. It's a good idea but it's different than what I had in mind. You will also have to deal with API limits or terms of service and legal issues, once you start looping in the closed-source networks.

No, but you could have a web server that responds to multiple domains. Ideally, the server listening and responding to the AP requests should be able to work with multiple “virtual servers”, instead of having to have only one instance == one domain that we today. AFAIK, only Takahe does this for microblogging.

Yes, that part's not overly hard. I'm already doing virtual servers for ponder.cat and rss.ponder.cat, to run them both on the same VPS, and I'll probably add more virtual servers for development of frontend tweaks if I keep going with Lemmy. Some of the ideas I had in mind for hackable frontends involved wildcard virtual servers to serve people custom "instance" sites off a subdomain that's different from the actual actor ID instance name.

What I'm saying is that if someone's actor ID from the POV of the rest of the Fediverse is still https://ponder.cat/u/rglullis, and ponder.cat goes down, nothing that either ponder.cat or any new instance can do, can "catch" requests that are being directed to that actor ID. You have to make the actor ID either https://rglullis.com/u/rglullis or https://rglullis.sometrustedthirdparty.com/u/rglullis from the beginning, and arrange for ponder.cat to be handling any traffic for those domains, so that you can switch away from the ponder.cat instance later on if you want to.

Of course, you can tell people that they can either have a ponder.cat user, or a rglullis.com user if they want to buy their own domain for their user, and they can have an actor that will be transferrable from ponder.cat to any other Lemmy server that supports the feature. It wouldn't work with current Lemmy, but in theory it could be made to work, if someone were willing to make the right Lemmy changes. It would be tough but it might be worth it.

Overall I think it might be better to address the same issue at the protocol level as some other federated social media networks do, so you're not introducing crazy new requirements on both the server and user experience side in order for people to be able to transfer their users later.

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.

Worked on, it sounds like.

This is outstanding. What I was thinking was UI plugins or custom frontends per-user, effectively, so it would fill in a needed niche on top of the backend plugins. Maybe they've done something in the UI area already.

This is really good to know.

I think hackability can go a long way towards this.

Especially on the frontend, there's no reason Lemmy shouldn't have custom "plugins" to change its behavior in certain ways. I think the issue isn't that the Lemmy developers don't want these things to exist that you're talking about, so much as them being the only ones in a position to make the changes or accept the PRs to make them happen. Of course in that situation, change will be slow and progress limited.

Me making changes to the frontend that intensive, or anything like it, was a bigger scope of change than I was expecting. I just wanted to make some tinkering things for my instance. But it wouldn't be impossible. And you could have your charts. Even little blinking lights and things.

Let me mull it over for a while.

Yep. I'm happy it's working.

Comic strips seem like they have their own communities which I don't want to collide with, and it's logical, since the frequency of posting is so much smaller that a human can do the postings no problem.

I understand now. I thought you meant something different by crowdsourcing. No worries.

Yes. I want to avoid having it become spam, so I decided to be careful which RSS feeds I add to keep the human-to-bot ratio up.

I think they can both be useful. Some people will prefer to have an RSS reader pulling the feeds from Lemmy communities, and some people will prefer to have Lemmy as their home base, so to speak, and like to be able to add updates from some RSS feeds to that.