Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DA
Posts
17
Comments
1,578
Joined
2 yr. ago

  • I watched a coworker run rm -rf * from / as root the other day. He started wondering why things weren't working. I told him what he just did, but he didn't get it at all. Luckily it was a VM that could be recreated from a template. He probably lost 30 minutes of time. But it could have been waaaay worse if it wasn't a disposable VM.

  • I agree, but I really don't see any other possible way to do this other than either having one entity in charge of voting information (all this power in one place leads to just having reddit again) or to just not store it (would make it trivial to manipulate votes). I think this is unfortunate just a limitation of federated software. All the information must be public. Even the contents of direct messages are visible in the database. I think can see every direct message between everyone on any instance federated with mine, though I haven't actually checked.

  • I think you can see it from any instance that's federated with you. I am an instance admin for an instance where I am the only user, and I can see who is upvoting and downvoting you, who has a different home instance and is posting on a third instance.

    Theoretically, you could create your own instance just to view this information.

    Though, I am not a huge fan of making this information publicly visible because I think it will discourage people from voting if they know everyone can see how they voted. If you wanted to just check it for yourself, I don't think there's anything wrong with that.

  • It is stored. I can see everyone that upvoted and downvoted your comment by looking into my database right now.

    It has to be, actually. Otherwise you could easily use the API to keep upvoting the same post or comment over and over.

  • This is absolutely not true. I just verified in my database that I can see how everyone voted on your comment. I can see that @Bishma@discuss.tchncs.de and @snowe@programming.dev (you) upvoted this comment, and that @dandroid@dandroid.app (me) downvoted this comment.

    Edit: more people voted since my comment, and I can see all them, but I don't want to put those people on blast. I wrote a very short SQL query to get me this information for any comment id. It took about 3 minutes with zero previous knowledge of the lemmy database.

  • I wasn't working under a contract, but I worked for a company that got bought out by another. On my resume, I didn't want it to look like I changed jobs, so I put them as one job, with the name of the company being, "Company A (merged from Company B)"

    Maybe you could do something like that.

  • I mean, they look nice, but I don't dislike whatever the default font that I use is, and I'm definitely not going to go out of my way to change a font. As long as it's legible, I don't really give two shits what the font is.

  • You can have bots in Teams although I haven’t found any particularly useful ones yet.

    I meant more of writing them yourself. My old company used Mattermost, and we wrote a bot to choose where to eat for lunch each day. It would pick 3 choices from a list that anyone could add to, and we would vote on those three options or veto.

    I like having the option to make my own bots.

  • The only time I have had it not be able to use my mic was when I had some issue with my whole computer and no app could use my mic. It could have been a driver crash or something. But other than that, I haven't had that issue. Slack ALWAYS has that issue for me, though.

    For missing features, you can't add custom emojis, you can't have bots, searching chat history is horrible (almost to the point where it's not usable), there's no markdown for spoilers, code blocks, italics, etc. so you have to click the buttons for it (not sure if spoilers even exist in Teams), code blocks are really clunky, you can't link other conversations.

    When my work briefly used Slack, it was really nice for text chat. But some teams just didn't switch, and there's just so much value having everyone on one platform. Fragmenting users was very counterproductive, so we went back to Teams.