There was a post relating to this the other day: Some explicitly single-user ActivityPub software to check out

Last time that happened to me, it was because the ‘name’ I was using was too long (I removed some characters and it worked). There isn’t the same limitation for the ‘display name’ field though.

Well, there’s the The 90-9-1 Rule for Participation Inequality in Social Media and Online Communities, which suggests:

Summary: In most online communities, 90% of users are lurkers who never contribute, 9% of users contribute a little, and 1% of users account for almost all the action.

So whatever number you’re looking for, it’s 1% of that. Not that subscriber count means much, especially for older communities that have 10’s of thousands of subscribers who aren’t even using the platform any more.

I think it’s how they do it in America (I was watching a video of James May reviewing a cybertruck, and he commented on markings that say things like “Xing Pedestrian”). It makes a certain kind of sense, I suppose.

There are instances like https://soccer.forum
https://nba.space
https://nfl.community

The communities aren’t super-active because the idea is that they’re remote-only, but that means they don’t get the benefit that comes from local users browsing their local feed.

Here’s a community node for mastodon

Should this be a link to something?

We appear to be at an impasse.

I’ve recently been adding an API to PieFed and forked the Lemmy Thunder app as way to test things. My position on this comes from tinkering with Thunder - I can’t claim to understand it all, but it seems to me that the API and the app are fundamentally interlinked in ways that make being too adventurous with it difficult. For that app, it would break the existing paradigm to do the kinds of things you’re talking about. Thunder uses its own version of an API client (written in Dart), but I’ve assumed that other apps are written in a similar way, and are essentially wrappers around Lemmy’s JavaScript client.

Hopefully, someone else with more app development experience will contribute to this discussion, and set one of us right (I don’t mind if it’s me that’s wrong).

Most frontends already display available crossposts so you’re not wasting anything more than grabbing all the comment sections as well.

We’re talking about different things. I’m talking about the view you get when you first open an app - the ‘home’ screen that lists the posts. The API response for api/v3/post/list doesn’t indicate whether something has been crossposted. You can see for yourself by getting a list of the 2 oldest posts on lemmy.ml:

curl --request GET --url 'https://lemmy.ml/api/v3/post/list?type_=Local&sort=Old&page=1&limit=2' --header 'accept: application/json' | jq .

For those 2 posts, you can only find out if they have crossposts by individually querying each post using the api/v3/post endpoint - the first one in that list would be:

curl --request GET --url 'https://lemmy.ml/api/v3/post?id=2' --header 'accept: application/json' | jq .

where crossposts would be in the ‘cross_posts’ array.

So for an app to display whether a posts listed on the main feed have crossposts, they’d have to query post/list, and then for each entry, query /post as well. This isn’t the way these things typically work - there’s normally a 1-to-1 relationship between an API query, and displaying the results of that query on the page. Looping through the list you’ve been given, and making extra queries adds complexity and delay, when the expectation from the user is that this list should appear pretty quickly.

What you’re talking about, is the view once a user has clicked on a post, not the post list. This provides the crossposts info. It’s important to realise though, that the cross_posts array provides everything an app could want to display info about the other posts. It’s not like they are pulling the data for one post, and then pulling data for each listed crosspost, so if they were to start getting the comments for each crosspost, that would be an extra effort (and a potential waste).

I don’t agree at all. There’s space for complex frontends which attempt to adjust the feed according to their own logic, as well as minimalistic frontends which follow the backend’s design explicitly.

My counter to that, would be that if you aren’t using the API in the way the developers expected, your app has ceased to be frontend, and is instead its own program that’s scraping data from it. There are already some heavy desktop-orientated frontends, and none of them do what you’re proposing. I think that the reason why, is because the proper way to do it is for the Lemmy’s backend to be changed to provide the information they need in one go. That’s unlikely to happen, but that doesn’t mean that hacking away at an improper solution is necessarily the right answer (you just end up supporting a project that isn’t supporting you in return).

No reason that I can see. Your instance is sending stuff out, LW is getting stuff in, you’re not banned on LW (as far as I can see), LW and feddit.org are likely in the same part of the world (so no fed delays). There’s been times when LW has received a post and federated it out, but not shown it itself, but that’s not the case either.

I don’t know. It might be worth asking on LW’s matrix channel, to see if an admin will look into it.

Frontends generate the main feed by querying api/v3/post/list. This doesn’t provide any crosspost info - for that you have to go into the post itself by querying api/v3/post. As such, frontends would have to do a fair bit of extra work to wrangle the required information for a main feed that combined crossposts. The only attempt I’ve seen at doing this was in a dev branch of Tesseract.

I’d argue that you have a problem as soon as you start saying ‘frontends need to do some extra work’ - it breaks the dynamic between backends and frontends. Backends should be big, complicated things, worked on by people familiar with the project, to provide all the logic, whereas frontends should be light, relatively easy to write, runnable on devices with limited resources, and mostly focused on how the information provided to them should be displayed. They should store the user’s preferences, and login details, and that’s it - everything else should come from the backend.

As for combining comments, this can lead to fraught situations. This link was posted to both ‘cars’ and ‘fuckcars’. This link was posted to both ‘taylorswift’ and whatever-the-fuck ‘barelower4thwomenmusic’ is: so the comments for a music video would be from Taylor Swift fans, as well as from people with a foot fetish. Moreover, if this is the expected behaviour, trolls can use it to get up to no good, and make a bunch of comments appear in a new crosspost to a community subscribed to by people guaranteed to disagree with them.

I think anyone trying to ‘fix’ this issue will run into the fact that certain assumptions have been made in a software’s design, and those assumptions determine how database relationships are formed. The real answer may lie in something like ‘ClubsAll’, rather than an attempt to fundamentally redesign existing platforms.

In the meantime, crossposting is being actively encouraged. Movie news is posted to 5 different communities, open-source news is posted to 8, Taylor Swift music videos are posted to 12. The useful crossposts (one that help you discover a new community) are in the minority - most of it just ends up being annoying. And it’s because there this idea, that some time in the future, there’ll be a tech solution to make it less annoying, and the suggestion that maybe you should just pick the community you like and post to that, is - to me - surprisingly unpopular. Not only might this solution never come, but anything URL-based can’t do anything about the same question being posed to ‘nostupidquestions’ and both ‘asklemmys’, or with an image being uploaded and posted to one community, and then re-uploaded to post to another.

This whole thing feels like trying to find a tech solution to what I see as a user problem of mindless posting to as many communities as you can find. To be honest, it’s a problem that makes me a bit disillusioned (I saw a post the other day that was posted to both ‘interestingasfuck’ and ‘mildlyinteresting’, and thought - if that’s the community names we’re going with, and this behaviour is apparently okay, then we may as well be on Reddit).

For ‘Action Horror’, I’ve liked The Hunt (2020), Ready or Not, Totally Killer and Strange Darling (technically not a horror, but it’s about a serial killer)

I watched Red Rooms recently, and that’s French (Canadian), so if anyone asks you what you watched recently, you can say ‘Les chambres rouges’ and sound all intelligent and stuff.

Good luck - I get the sense that ‘kurwa’ has lots of meanings, but what native speakers mostly use for is: ‘give me a minute, I need to figure out how to conjugate the rest of this sentence’.

Congrats.

There’s also a !lemmyapps@lemmy.world, btw.

It’s a useful metric. Maybe it’s the better one, but personally I’d like to see good data from both.

I had to look at All + New the other day because the Fediverse was being spammed by some twat, but otherwise it’s

90 / 0 / 10 (if I look at All, it’s All+Hot, not All+New, 'cos that’s for masochists)

It’s a trade-off, I guess. Admittedly, there’s not much benefit the user (though they could be warned via email if their account is going to be de-activated). There is however a benefit to the community, in that it can provide more reliable data to see if it’s trending in popularity (a 100 extra users isn’t significant if it thinks it has 30k users, but it moves the needle if that number is at a more realistic level).

I recognize most of the users there even in the big communities with over 30k members

Communities with 30k members could really do with pruning the completely inactive ones. It’s not like there’s any commercial reasons to pretend that places are busier than they actually are.

I know all the cool kids hate on AI, but as someone out of the loop, that ‘podcast’ is really impressive. I guess it speaks to how a influential certain style of podcasting is (from the likes of NPR) that a machine can copy it the same as other humans do.

As for the embedded link, this works for me (and others on the same site as me), but it might not for others:

Just curious: how would you classify Chrome OS? As Community/Linux or Community/Linux/Chrome (to recognise how much heavy lifting the browser is doing). And would you want to call Google’s additions ‘Community’ or something else?

Sorry - I meant that it’s literally the username they’ve used. They’ve used the word ‘911’, like you’ve used the word ‘windyrebel’.