I have "always trust domains" off, but I don't get any pop-up like that.
Edit: it's because I also had "use external browser" on. Feel like I should still get the popup though.
I have "always trust domains" off, but I don't get any pop-up like that.
Edit: it's because I also had "use external browser" on. Feel like I should still get the popup though.
Part of the issue is that three dot option is pushed off screen for me in very nested comments (like yours). I can only see it comments closer to the root.
It is also nicer to be able to select which text you want to copy.
Speed of development. It could take months for a PR to get into Lemmy core and then a new release.
Things that get into Lemmy core have to be well thought out and the core Devs have to want them in there.
Running custom code is a way to make changes without having to get their approval, and if it proves popular enough, then maybe they'll implement it upstream.
It could be a long tap on the space to the right of the comment timestamp.
There should definitely be a way to select the text of a comment.
Your advice is applicable to your own original comment, so it seems you do agree with what I said, at least to some degree.
Anyway, in the interests of constructive discussion, let me ask you specifically. Do you think this WEI proposal is good for and why? Does the proposal mention at all what the downsides of this feature might be, or how it could be abused? Is it proposed in such a way that the dominant implementors can't deviate later from the terms suggested in the proposal?
Is there a planned feature list somewhere public?
Two things I'd like from RiF are :
markdown links opening in a little popup that shows you where they really go.
Draft comments, so if you're writing a message to someone, you can go off in the middle and check something else on Lemmy using Connect without losing what you've already written.
And one other thing is an option to customise how code blocks look, though maybe I'm just missing that in the options.
The user experience is nicer as a native app, if done right. With a PWA, you have to deal with anything crappy that the browser inflicts on you, and the developer largely can't do anything about it. For example, Chrome sometimes just crashes or freezes entirely on me, which means Voyager can too.
See elsewhere in this thread for examples of little things that stem solely from being a PWA .
Don't get me wrong, I think Voyager is great for a PWA and it probably gets a lot of value out of being a PWA making it easier for people to contribute. But it's just not as good as native for me.
I think this is not really inline with the philosophy of the main Lemmy devs. For this to happen, I think someone else would have to do the work of creating the random selection service. If it was popular enough, maybe they'd put a link on join-lemmy.org
I've been oscillating back and forth between wefwef and Connect and think I'm likely to stick with Connect.
I love all the customization options, they really let me change the UI to the way I was used to with RiF.
One thing I'd ask for is an option for text posts to have a dummy thumbnail so that all submission entries have the title, submitter, community, comment/vote counts in the same place. At the moment posts in the list without a thumbnail look a bit disjointed.
Can your instance not do that as is? Just spin up a bunch of fake users and make them all vote on something?
So if you're the only user (let's assume for ease) then, that represents all the updates (posts, comments, votes) from each community that you are subscribed to?
It's way faster for one. It actively scrapes articles from behind paywalls, using a bank of credentials it has. Archive.org respects robots.txt and will take down copyrighted material on request. Archive.is doesn't do any of that.
I would view it as complementary to archive.org. it's more like sci-hub to me. A useful tool, run by one person who likes the idea of providing such a service.
What exactly do you think is being tracked by your ECS being sent along with DNS requests? All it means is that archive.is can't load balance properly because they don't know what their nearest server to your location is. If you're so privacy conscious that leaking a portion of your IP to a DNS provider, then hardcode archive.is IPs into your hosts file or use a VPN. Not that your problem can really be with archive.is, because you're visiting the site anyway, giving them your full IP.
It just seems like such a non issue to me.