Change to the link format from now on, to also support mbin and other fediverse apps that may come along.
I didn't do it like this before, because earlier versions of Jerboa didn't understand this link type, and I don't like that it repeats information - the name and the description are often the same, but not always, and the name can be hard to read, so the description needs to be there, but it's often redundant. I can't combine the description and link like [Hello Internet](!hellointernet@@feddit.uk) because lemmy will interpret that as link to a post for some reason.
I tested in the front-ends and mobile apps I have available, and they all work.
I've been resistant to changing it to this, and when mobile app users have said that they're app didn't support '/c/' links, I've been "well, fix your app then", but it turns out that all you have to do is say the magic words 'Fediverse Interoperability!' to me and you can win the argument.
Are you testing from there? I'm surprised any link works, local subscriber or not. I went to Moist, and could see that 'The Onion' community had been resolved, but when I tried the link from a 'trendingcommunities' list on Moist, it didn't work, because mbin puts everything at '/m/' rather than '/c/'.
If you're testing from lemmy, I made a video the other day of what happens when you click on a link that doesn't already have a subscriber. It errors at first, but if you wait for the backend to complete everything required, a refresh will bring it through.
I can't test what happens with mbin, because instances don't typically resolve remote objects if you're not logged in, and I don't have a mbin account. It's possible that a 'wait-and-refresh' brings it through, but - like I say - I'm surprised any link works on there.
things may have changed recently, but the /c /m thing is kinda of irrelevant if the links are crafted the right way
communities dont 'just exist' in every instance they are created as they are 'seen'. if a user clicks on a link with the expectation it exists (direct to /c/%com, /m/%com) it will fail with 404 if it has never been seen
if the link is crafted to push through the search of the instance, the user can get to the community regardless if the instance has ever 'seen' the community.
if the link is crafted to push the the search function, it works no matter what:
For lemmy, the links are already crafted the 'right way'. It's what I was testing for when I made the video I linked to (the instance I was on was brand new, so it had never heard of the community link I clicked on, but it still worked).
I don't think crafting all links to point to a search endpoint is the correct solution. It'll do what's required for mbin, but I suspect the vast majority of users are on lemmy. For them, it's an extra step to get where they want, from a page that's either filled with extraneous info (every time TIL has been mentioned for your link) or will say 'no results' until the backend has completed its tasks.
Oh, well, I don't know when lemmy changed then (and presumably diverged from mbin) - this community's been running and using the same link format for about 7 months.
Fediverse communities don't really exist - lemmy has communities, and other apps have things that are similar in some ways but not in others (e.g. mastodon groups, peertube channels, and mbin magazines). There's lots of little differences that limit full interoperability, meaning that lemmy doesn't have as much connection with the wider Fediverse as perhaps it should. This is more a subject best addressed by app developers than me. I can't solve problems like that with a list of links.
In other areas, I've done what I can - I made a virtual lemmy community that natively features posts from mastodon accounts that haven't even heard of lemmy. Pretty cool, I thought, but no-one gives a fuck. So I resent the idea that lemmy being closed-off in any way is something I'm indifferent to.
I just clicked the 'search' link I just made from lemmy.world, btw. The link to the actual community is 4th from the top, buried between cross-posts and mentions. Moreover, the likelihood that 'search' post work on every lemmy app is pretty low. Right now, these list work on any of the multitude of front-ends or mobile apps you can get for lemmy, which is a minor triumph in and of itself. Changing them to work for mbin would just break something else. Even if it didn't, they'd work on lemmy and mbin, and then they'd be some new app (who haven't hard-coded search in the same place) that they wouldn't work for, and we'd be back at square one.
I suspect that ActivityPub is too broad and too permissive for that. For every post on lemmy, it already sends out two different activities - one for lemmy, one intended for mastodon. On lemmy, a new post is a 'Page', on mastodon it's a 'Note', on PeerTube it's a 'Video'. Lemmy understands all 3 (more or less), but my feeling is that if Fediverse apps are inter-acting well together, it's largely because someone hacked it.
The thing the Fediverse most reminds me of is DLNA (aka uPnP Video) - it's supposed to be universal, but if you ever saw the config for a DLNA server, you'd see it had to do different things for every different brand of client.
communities dont ‘just exist’ in every instance they are created as they are ‘seen’. if a user clicks on a link with the expectation it exists (direct to /c/%com, /m/%com) it will fail with 404 if it has never been seen
On Lemmy, it will just exist when you reload that 404 page.
I happened to see on another post that mbin will resolve links beginning with a '!' - I signed up to moist to check, and they go to the '/search?q=' link. This is an mbin specific thing, so maybe I misunderstood when you mentioned crafting links to go there.
I changed all the links today to use these ! links. This is how the very first post was on this community incidentally, and the very first comment was someone saying they don't work on Jerboa. This is the official lemmy app, so I changed to the /c/ version. Since then, Jerboa has changed to support them, and I tried the links on other apps, and other front-ends, and they all work.
Future posts in this community will use this link format, so they'll be compatible with lemmy, mbin, and whatever other fediverse apps support it (I tried with Mastodon, but I don't think they like relative links of any kind).
(shit, sorry, replied from the bot account - freamon)
i love these posts, and using them to find new communities to subscribe to.
im really just rooting for the most universal access method, which this seems to be. i specifically requested mbin be modified for this reason as it used to utilize the @comm instead of !comm, eliminating a differentiating pathway.
again, thank you for helping us all link together!
!florida, 中国的最新发展, A place to learn about China, Chinese and China's latest developments, (Reddit's Sino), up 16.3% to 39, (651 posts) !allthingsfoodandcooking, 中国的最新发展, A place to learn about China, Chinese and China's latest developments, (Reddit's Sino), up 16.3% to 39, (651 posts) !yurop, Europe, up 16.3% to 39, (651 posts) !minipcs, Mini PCs, up 16.3% to 39, (651 posts) !letstalkaboutgames,, Let's talk about games, up 16.3% to 39, (651 posts) !palworld|中国的最新发展, A place to learn about China, Chinese and China's latest developments, (Reddit's Sino), up 16.3% to 39, (651 posts) !trams_trolleys_streetcars, 中国的最新发展, A place to learn about China, Chinese and China's latest developments, (Reddit's Sino), up 16.3% to 39, (651 posts) !science|中国的最新发展, A place to learn about China, Chinese and China's latest developments, (Reddit's Sino), up 16.3% to 39, (651 posts)
MBIN (moist): Table looks like garbage, but a ! link will resolve to a '/search?q=', so it can find something it hasn't heard about before (florida@lemmy.ml)
Lemmy (Jerboa): Can resolve known, and unknown on refresh (florida@lemmy.ml).
Lemmy (Boost): Can resolve known, and unknown on refresh (allthingsfoodandcooking@sh.itjust.works).
Lemmy (Connect): Can resolve known, and unknown - no posts until refresh (yurop@lemm.ee).
Lemmy (Eternity): Can resolve known, and unknown - no posts until refresh (yurop@lemm.ee).
Lemmy (Sync): Has a separate pop-up for 'Show Table', but handles unknown stuff really well with no refresh required (minipcs)
Lemmy (Thunder): Handles unknown stuff really well with no refresh required (let's talk about games)
Lemmy (Voyager): Table is rubbish. Unknown worked on refresh though (palworld)
I love this stuff, what about making a community about the innards of lemmy (and the fediverse)?
I'd love to know how the pictrs service works (and why I have lots of doubles for example) and also compile lemmy from scratch instead of depending on a docker image.
I didn't bother with picts-rs, but I found compiling lemmy to be fairly straight-forward (following the instructions on join-lemmy. Rust is difficult for me though, and lemmy's code seems like a labyrinth. So I've no idea what lemmy's up to most of the time (spinning its wheels randomizing the Hot sort, would be my guess).
I was about to say that communities for the innards of lemmy maybe already exist on programming.dev or at !lemmy, and then I looked at that community, and the first post I saw was promoting !learningrustandlemmy, spookily enough.
The bot at lemmyverse.net has been failing, so these results are over 2.5 days.
The 'Native Mastodon Posts' community won't feature on lemmyverse.net, unless I can be bothered to write a proper API server, so I popped it on the end of the list 'cos it's the new thing I've been working on, but it won't always be there.
This is helpful to see. I've gotten to that screen many times before and I often give up because I can't be bothered to find a community the only other way I know how -- through search with the "!" and everything.
Glad to see I can wait and refresh. I can handle that workload.
Bonus video illustrating the 15 second gap between a lemmy instance sending out a Follow (to subscribe to something) and receiving the Accept back that'll move the status from 'Pending' to 'Joined'
Lots of non-real-world factors here: the lemmy instance is running on an VM, it's connecting via a tunnel to a home DSL connection, and lemmon.website isn't running lemmy, but it hopefully demonstrates how subscribing is 2 distinct actions, and how it can get stuck on 'Pending'
Trending Communities
Active