Help

It’s a bit of a stretch calling it a plastic, as it’s not petroleum based from what I’ve read.

You cannot meaningfully delete your posts or comments. That’s not because of any issue with lemmy, but because you posted them publicly. They will be archived and indexed in other services.It is always best to remember that all your activity here is public, and will be linked to your username. Given that, you may wish to minimise any personally identifying information you post, and use several accounts to split up your activities by topic.

I don’t believe other instances will receive any sort of deletion request from lemm.ee, it’ll just go away. Any instances that have a copy of your posts or comments will keep them for as long as they wish. Even if you manually delete the comments and lemm.ee federates that action out, there is no guarantee that any other server will actually act on it, and you can be certain that archiving services will not.

Ultimately it comes down to the fact that you posted, commented or voted in public, and that will remain public indefinitely. That’s as much down to howpublic data is captured by other entities as it is to the concept of federation.

Put it in a pair of jeans and you have captured the very essence of Lemmy in a single image.

It might, possibly, be a viable use case if the LLM produced the summary for an editor, who then confirmed it’s veracity and appropriateness to the article and posted it themselves.

The thing is, in X11 that clipboard behaviour was written once, and that made it work everywhere. Obviously there’ll have been work done on it over time, and non-native frameworks (java UIs and such) would have had to do it themselves, but for the vast majority of programs the author, and indeed the author of the toolkit probably didn’t have to think about it at all. It’s one of the nice things about the X11 architecture that I think we lose with the wayland approach, everything that should work the same everywhere is written once. I suspect that over time we’ll see only a few wayland compositors really lasting and being maintained, and we’ll start to get back to that common architecture.

I can definitely understand your frustration with the clipboard situation, but it’s a decades old paradigm, and I’m used to it, so it seems reasonable to me. That said, I do use clipman to automatically store the text I’ve copied to the clipboard, and let me switch to previous values, so maybe that sort of thing would at least help you a bit?

if you’re going to teach all your tools how to use multiple shortcuts and interact with a complex clipboard situation

The people writing the tools don’t have to do this, it ‘just works’ as it’s functionality the UI framework provides. It used to be that whether you used Tk, GTK, Qt or any of the others, you still ended up with X11 components on screen, and those components handled the UI interactions like middle click paste from selection or ‘ctrl-v’ paste form clipboard, but then we got a few UIs that tried to draw themselves (Java apps were terrible for this). I don’t know what it’s like on wayland, I suppose it could be different per compositor. I’ll get around to testing it at some point, but I’m in no hurry to leave X11 behind.

just having them able to look back an arbitrary distance in the history of a single clipboard, like M-y in emacs.

You’ll get no argument fro me, that would be a more intuitive approach, although rather than just a stack like that, I’d probably prefer to have a set of registers to yank to and paste from too like vi. That way I can put the information I want to keep using at a specific location, and just use the rolling stack for the more ephemeral stuff.

I’m still using X11, so this might be different in wayland, but in just about everything shift-insert pastes the selection and ctrl-v pastes the clipboard. In terminals paste from clipboard is ctrl-shift-v as ctrl-v already had a purpose.

Copying to selection just involves highlighting the text, copying to clipboard is ctrl-c or ctrl-shift-c in a terminal.

I had to actually think about those as they’re basically just muscle memory now! I might use the clipboard to store a path I need to use in multiple places, maybe in multiple tools, and the selection for ephemeral data like a snippet of output from the last command, or an ID value from a web page, something like that. It’s a bit tricky to explain, it’s just the way it’s always worked on unix and linux UIs, and it just becomes second nature to think with those tools.

Do not respond by playing loud noises back, no matter how tempting, that’ll just give him the chance to say “see, they’re the ones doing it”. Going away for a break might be a great idea though, just to get some rest and relax a bit. I’d suggest putting up external cameras covering the whole property, and internals covering doirs and windows first though, just in case he does anything harmful. I know you said he was frail, but you don’t want to take chances.

This from 2 years ago, and it aparently took the Ukrainian forces 18 months and a few days to plan and execute. Conclusion: the Ukrainian armed forces are monitoring NCD for cunning ideas, but it takes a few months for them to get authorized.

I’m very happy having the selection and primary clipboards be separate (I’ll admit I don’t use the secondary clipboard). Being able to copy one block, then select a second block, paste that in from selection and then paste from clipboard makes a lot of CLI tasks quicker.

There probably should be a setting that says ‘K.I.S.S just one clipboard please’ though, for those that prefer that way of working.

Not at all, but I’d say we don’t really remember ancient kings either. We might remember the effect they had on the world, or some particularly unusual characteristic that was recorded for posterity, but I’d say that once the last person who knew them dies, we can no longer remember ‘them’, so much as witness a sort of ‘shell’ of ideas about them.

We don’t remember what they sounded like, or smelt like, how they smiled or what they said to their nearest and dearest. We don’t really know much about them as people compared to the king that became their shell. The things that made them unique people are gone when the last person who experienced them dies, so I’d say we really don’t remember them as people, even if we do remember the ‘king’ or ‘copper merchant’.

If the details aren’t specific to your server, could you post the body of the message? They might not stop there, and I’d like to know what’s going on before they hit my server.

Do we actuall remember Ea-Nasir, or do we just recall a modern meme about one aspect of his life?

Right, that’s it, we’re removing the network and power connections too.

To be fair, I’ve had my share of foul ups on remote servers too, but I have noone to complain to but myself about that.

I’d be interested to see if this upside down printing technique would work with other filaments as it sounds like it could be the answer for printing overhangs on smaller models at least. I can see bigger models coming unstuck from the bed being a major downside though.

He’d obviously read up on 17th century witchcraft. It is well known that you may fascinate a woman by giving her a piece of cheese.

01000001 00100000 01110011 01110100 01100101 01100001 01100100 01111001 00100000 01101000 01100001 01101110 01100100 00100000 01100001 01101110 01100100 00100000 01100001 00100000 01101101 01100001 01100111 01101110 01100101 01110100 01101001 01110011 01100101 01100100 00100000 01101110 01100101 01100101 01100100 01101100 01100101 00101110

I mean, if you’re not using LFS, are you really using linux at all?

Walked across a room and pulled a muscle in my shoulder. It was painful enough that I could barely lift it for a week or so.