As long as they have a version that supports it, you can flip over to the Web UI to set it, then go back to a native client, if need be.
Kbin/Mbin have supported instance blocking since forever. Dunno about piefed and sublinks.
As long as they have a version that supports it, you can flip over to the Web UI to set it, then go back to a native client, if need be.
Kbin/Mbin have supported instance blocking since forever. Dunno about piefed and sublinks.
Yeah, user migration would be nice.
If it were a shift to simply using a keypair as the basis for identity, which would be a big change, then one could potentially transparently use any instance. That'd be neat from an instance reliability standpoint.
Keypair-based identity would also permit migrating an account from a permanently failed instance. Right now, the home instance is the authoritative source for the account. The problem with that is that if the instance goes away forever, then there's no authoritative source left to determine who controls a user account. One of the use cases that I'm worried about is a big instance going down because the admins get in a car crash or something, and it killing all the user reputation that's been built up, because nothing can be done after the permanent failure.
IIRC feddit.uk had a close call like this a while back.
What would that involve? I mean, you can already have spoiler sections in post body text.
Lemmy.today is in Oregon.
Honestly, though, as long as your home instance is in the same half of the US, or for Europe, anywhere in Europe, I doubt that latency is gonna be very noticable.
That helps, but honestly, it shouldn't be a client workaround.
Detect AI prompts attached to images and not strip them from images on upload the way other EXIF data is.
Stripping EXIF location data to help keep people from being doxxed is one thing, but AI image generators try to make images with metadata to indicate that the images are AI generated, which helps avoid using them for training and lets people inspect how images are created. As of now, that gets stripped on upload. It's particularly obnoxious over in !imageai@sh.itjust.works.
EDIT: Even nicer would be the option to leave EXIF location data attached, and merely warn a user at upload time about location data and provide the option to strip it, as I can certainly imagine communities where people would really like to be able to include precise location data with their images.
I haven't looked into any actual decision process, and personally, I'd like to be able to post vector files myself, but there are some real concerns that I suspect apply (and are probably also why other sites, like Reddit, don't provide SVG support).
SVG can contain Javascript, which can introduce security concerns
My guess is that there are resource-exhaustion issues. With a raster format, like, say, PNG, you're probably only going to create issues with very large images, which are easy to filter out -- and the existing system does place limits on that. With a typical, unconstrained vector format like Postscript or SVG, you can probably require an arbitrarily long amount of rendering time from the renderer (and maybe memory usage, dunno, don't know how current renderers work).
At least some SVG renderers support reference of external files. That could permit, to some degree, deanonymizing people who view them -- like, a commenter could see which IP addresses are viewing a comment. That's actually probably a more general privacy issue with Lemmy today, but it can at least theoretically be addressed by modifying Threadiverse server software to rewrite comments and by propagating and caching images, whereas SVG support would bake external reference support in.
I think that an environment that permits arbitrary vector files to be posted would probably require some kind of more-constrained format, or at minimum, some kind of hardened filter on the instance side to block or process images to convert them into a form acceptable for mass distribution by anonymous users.
Note that Lemmy does have support for other format than SVG, including video files -- just not anything vector ATM.
If the art you want to post is flat-color, my guess is that your closest bet is probably posting a raster version of it as PNG or maybe lossless webp.
Can also store an SVG somewhere else that permits hosting SVG and provide an external link to that SVG file.
There has to be soy milk or almond milk or something else that could be used.
If you have a gun, never get within knife range.
I mean, it's doable now, but I think that the limiting factor is just the userbase. More developers using the platform, more people interested in writing code for browser extensions.
There is a lemmy/kbin assistant extension for Firefox, which is far, far more basic than RES, but provides one critical feature that I regularly use -- being able to view a post on one's home instance. So people have done work on these.
Also, if by "Old Lemmy", you mean mlmym, that's not merely the website. It's an alternate Web UI that instances can run alongside the regular one. My home instance does so at https://old.lemmy.today/
EDIT: Your home instance does as well, at https://old.lemmy.world/