Yes, thank you, mr parrot.
Yes, thank you, mr parrot.
You’ve only made the case to implement authorized fetch on lemmy. Mastodon did it, Pixelfed did it. No reason why lemmy cannot do it.
edit:
To be clear, I don’t give a rat’s ass what lemmy instance admins do in this matter. Threads interaction is more compatible with mastodon and pixelfed anyway. I just think the chicken little act is ridiculous when bad actors of concern are definitely already here. You’re not stopping anything from coming in. This place isn’t untainted like freshly fallen snow. It’s a pool that gets peed in on a regular basis.
And that’s why you can personally block it like any other instance in your settings. It’s no different than blocking a lemmy instance that also harbors those exact same kind of people.
Good to see more reasonable people in all of this.
Threads is also overrun by a lot of algorithm induced hate speech and far-right extremism
Pretty sure you’re confusing Threads for Twitter. Threads doesn’t contain any more of that than lemmy or mastodon already does, and it’s probably less, so such handwringing is overstated. They’ve already implemented a “Restrict” setting in addition to blocks and mutes, and frankly their handling of blocking and how people can interact with your account after being restricted or blocked is already more effective than what’s here or on mastodon.
I think you only made a case for having two or more levels of instance block, that already exist. One due to objectionable/illegal material that cannot be overridden, and another for something like threads where a significant number of users may not want to be opted in automatically, or want to block it due to purely ideological, non-illegal reasons, which would effectively be put in place by automatically adding the instance block to user accounts that can be removed at any time, which arguably can already be done with minor changes. That’s essentially what dansup is doing, complete with including a command for Pixelfed instance admins to apply the optional block to all user accounts.
All true, and making this a feature would simply be implementing the inverse of the new capability… overriding an instance level block instead of imposing one not already at the server level.
FOSS ingenuity at work. All it needs is adaptation and adoption.
The most reasonable solution I’ve seen so far, from the pixelfed and pixelfed.social creator
Try using actual sentences to express yourself, it’s more effective.
Except I have no idea WTF that reply means so good luck getting threads users to understand it.
Most people on Threads aren’t pro-corporate, they don’t actually give a shit about that. They’re just too confused by the decentralized model to be on Mastodon, couldn’t get an invite to Bluesky, and wanted somewhere to be other than Twitter.
Being connected to it all via Threads could eventually help them get enough understanding to migrate to a different instance.
well said 👏
Well now I have a new “app” to test. I could login with my reddthat account just fine, and it acts like a native app on iphone if I first open it in safari and then add it to the home screen. I can “close” it and it remembers my account just fine on reopen. TIL more things about lemmy.
Just want to add to my comment that the #1 reason I sometimes prefer the browser over an app is that you can open content in multiple tabs, just like on desktop. I can have several tabs open, each dedicated to viewing one community. Easier to cut and paste urls and other content into other apps. I don’t like being confined to one viewport for everything. It’s nice being able to interrupt reading a discussion to go down a rabbit hole in another tab, then close it and pick up where I left off. Navigation in the apps can be generally unpredictable right now. Or you completely lose your place and have to go find it again. Lots of pros to using a browser for it.
Interesting, I have a lemmy.world account but I don’t think I’ve seen the mobile view in my browser. At least, the url stays the same for me, it’s one of the reasons I didn’t consider that possibility. I’m used to seeing a m.domain variant on other sites. I’ll have to experiment and see if going to that specific url changes something.
edit: I’ll be damned, it does give me a whole different interface I never knew about.
beat me to it, but it’s apropo this is coming from a shitjustworks account
I also backed up and now see what you meant about being able to have multiple front ends for an instance. I read that as being able to select a frontend, not as having an “instance.com” and a “m.instance.com” at the same time, but that would solve the concern I raised. Yeah, we’re good.
What do you mean “about to” and “again”?
Also
What accounts do I need to follow for this experience?