that’s literally the whole point of this?
the point of this is a new youtube is unlikely to take off because people can’t start using it without missing all their regular content.
this means you can keep all your regular content and add new sources, with the same creators, which means they can start to move to new platforms and take their followers. that’s how we’ll replace youtube.
not sure if you’re joking but I can see the url is wrong… .ee on the end, not .me
there you go! thanks for updating, good to know
yeah, our unit tests def won’t pass if we have a dependency loop so it’s a waste of time checking every build.
it was crazy how difficult it was to find info on the setting and the right place to set it, considering the impact it was having.
i’m pretty sure it’ll be a long? - did you try it?
I saw an issue that would allow admins to just point a sub to another server, if that community grows more. seems like a reasonable idea.
lol it’s all good 😁 I don’t mind the posts at all
right? “sync users never shut up”
meanwhile my feed:
edit: and three posts down:
we get it you don’t like sync, I’m just trying to find content in an app i enjoy 🤷♂️
yeah I think I’ll go to the ad removal fee. it’s expensive but I use it a lot 🤷♂️
I originally did the monthly sub because I didn’t have an option and that was the cheapest, it is kinda pricey but it’s light years ahead of what I was using
also I’m a developer and I think the guy who made it has probably working like mad to make this, and if it’s his sole income and it got pulled out from under him… idk. it’s a gamble to not just go get a 9-5 and work on this instead
bro has to eat and I already donate to my local instance.
I think full federated auth across servers is a much more difficult problem - it’d be nice but outside the scope of this request!
Ya if it’s not federated already, I’m thinking the link will just remain as-is?
yeah that seems entirely reasonable. it’ll still be a big improvement in most cases. also even if it only happens as it federates initially it’ll probably still catch many cases. is it possible to do a follow-up check only for links that weren’t updated the first time? if you could store a cool-off and maximum number of tries that would probably keep it light and as functional as possible.
when serving posts with un-processed links that haven’t been updated, and it hasn’t been checked in the last 3 hours, re-check for a federated article and update. do this for up to 24 hours after the comment is posted, after that just give up? that gives it a few opportunities but doesn’t continue to waste resources if it’s unlikely the link will be resolved.
I’m not sure if it’s easy to add columns to track those attempts though.
oh that’s awesome! yeah i can see it being an issue especially if that post isn’t already federated. would be a great quality of life improvement though.
Found the feature request issue, it’s at https://github.com/LemmyNet/lemmy/issues/2987
ok sounds like it’s not a feature - the link format i suggested includes both the instance ID and the instance url, so it would be possible for your home server to use that to preprocess to a useable link. I wonder if there’s a suggestions box 🙂
I think my home instance blocks porn-only instances, which is fine with me. I can open an account on the porn instance if I want, it’s not the same kind of browsing.
i’m sadly finding communities with only one or two posts mostly, but i’m staying the course and i’m hopeful!
no and i’d struggle to recommend it. it seems to be mostly talking about being on the fediverse and hating other social media… hopefully we’ll get to a point where there’s more discussion outside of just being here and why.
what features do you miss?