𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 

Ceterum Lemmi necessitates reactiones

  • 2 Posts
  • 35 Comments
Joined 3 years ago
cake
Cake day: August 26th, 2022

help-circle










  • Yeah, I am only peripherally curious about them, so I haven’t yet done any legwork to see who’s behind it and what the values are.

    I’m quite pragmatic about politics: I’d work with just about anyone to bring income disparity down, to fix problems with our version of capitalism, to address the Police Problem. Anyone who agrees we need to overhaul the election system in the US, and bring in proportional representation, RCV, eliminate the electoral college? I’d share a table with them on those efforts.

    However, I feel as if joining a movement requires a bit of a deeper dive, as sympathetic issues can mask undesirable long term objectives. I don’t trust my gut instinct on these things.




  • They’re out there. The Venn diagram of people still choosing IRC (as opposed to being forced to use it b/c that’s where the community is) is probably just a circle.

    I was a big XMPP user back in the day, but because of the lack of multi-device message syncing and the really shoddy state of encryption, I wandered away. Plus, using XML for the protocol really geeked me out. XML is a document format, and per the spec, to be well-formed it needs to have an open and matching close tag. Jabber hacked around this by making a sort of infinite document - you get the open tag, but never the close tag - and it just felt really icky.

    I understand a lot of these things have since been addressed. I don’t know if XMPP still uses that bastardized version of quasi-XML without a close tag. But other things have come along that I like more. About 6 months ago I started running a client on my desktop again, but like you, nobody I knew was still using it, and nobody new was advertising it as their connection info, so… yeah. After a few months, I stopped running the client.


  • @Nikelui is 100% right: a chat room may be private, but it’s not secure. Even in an encrypted room, every additional person you add reduces your security. I’m sure there’s some paper out there that studies this, and that the graph of # of members vs security is an inverse power ratio.

    If it’s a public chat, there is no security.

    However, with Matrix, if you run your own server and restrict access to your friends, at least you can be fairly certain your chat room isn’t being used to train an LLM, or to harvest information about you for advertising.



  • I only wish I’d evolved it much earlier.

    For most of my career, I haven’t really needed it. I was a computer programmer for ages, and there were no to-do lists, aside from natural ones that fall out from trying to get from here to there. It was moving to management that really exposed my need for a process.

    todo.txt isn’t so much of a process as a data format, but it worked. The big evolution came with executive lists, which I read about on Lemmy of all places. I believe EL doesn’t really cover more than the EL itself; combining them was my innovation, although I’m certain I’m not the first to come up with it. I can’t imagine effectively doing it on paper.




  • That sounds like Carlin, but Carlin dispensed much wisdom in his time.

    My favorite story from Jack Marigold’s A Child’s Garden of Grass goes something like:

    A drunk, an acidhead, and a pothead are walking through the woods. As it becomes evening, they come to a city surrounded by a wall, and in the wall is a closed door with a sign that reads: “This door is only open 9-5”. After knocking and getting no answer for a few minutes, the drunk shakes his fist and says, 'let’s smash the door down!" The acidhead peers at the doorknob for a few minutes and says, “let’s just float through the keyhole.” The pothead shakes his head and says, “naw, man; let’s just sit here and wait for it to open in the morning.”

    I can’t handle pot; makes me super nauseous for the entire time I’m high. Always has. But I love the people.


  • Personal to-do lists, a two-tier todo.txt process.

    I have One Big Todo list, into which everything goes, with (at the least) added date and priority. At any job, this list becomes unmanageable and overwhelming within a couple of months, so I use the Executive List process a the second tier. It’s the critical part that makes the rest work.

    I create a new executive list every morning; it’s a list of things from my main list that I think I could accomplish that day. It is always larger than I have time for: the important thing about “could do today” is that it’s things that I’m able to complete - I have everything I need to do - not whether I necessarily have time. But the list is reasonable; it’s not hugely more stuff than I can accomplish, it’s just that I know I won’t complete everything. As I check things off, they’re also checked off the big list. New things only go in the big list first, although they might also get added to the executive list.

    The EL is psychological:

    • It’s manageable. It’s not a overwhelming, like the Big List of Everything I Need to Do is. It’s easier to face.
    • I know I won’t complete everything, because I’ve intentionally overloaded it so that I can’t. This removes the stress to “do everything” on the list.
    • It is trashed at the end of the day, and the first thing I do the next day is create a new list from scratch. This further removes stress about the importance of the list.

    The big list only ever gets bigger. Once a month, quarter, or year I go through the big list and delete (well, archive) everything that’s OBE. But the nature of management is that there’s always more than you can do, and much of it isn’t really important, but you can’t determine this in the moment. This is like going into Jira and deleting tickets over two years old, or whatever similar progress your team uses.

    The EL lets you prioritize accomplishable tasks for the day; it’s ephemeral, and surmountable. It’s also a way to break down bigger tasks from the Big List into bite-size chunks; the BL may have “resolve issue requiring scheduled server reboots”, and you might put “talk to OPs about sending nightly logs to dev team” on the EL.

    I used to just fill journals with pages and pages of to-do lists. It was worse than useless. Even moving it to todo.txt was a partial solution, because while it was easier to query, the list still became overwhelming. I dreaded looking all that list. The EL changed all that. I start the day looking at the BL, poking at it, pulling some things out into the EL for the day, maybe deleting some OBE items, but it’s low key. Once I get a half dozen or dozen things in the EL, I stop, and start working on those items.

    Throw it away at the end of the day, though - completed or not. If you’re completing everything, add more stuff tomorrow; you should always have something to throw away, to reinforce that you’re not trying to do everything. Don’t carry the EL forward, or it just becomes another BL.

    Some scripts really help, here. Copying things from BL to EL; completing things in the BL that were completed in the EL. It’s not necessary, but it makes things easier. This is why I use todo.txt - it’s plain text, and easily manipulatable with standard Unix text processing tools, and so easy to script.