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/)TO
Posts
23
Comments
1,694
Joined
2 yr. ago

  • I never would have thought to print them at an angle like that, but thinking it through, I bet relative to other obvious-ish options, it a) improved part strength (particularly along the axes where you most need strength), b) saved a bit of material, c) improved bed adhesion. Smart move in general. I'll have to keep that approach in mind for my own prints.

  • Probably isn't going to be easy to track down. The only thing I've been able to find is this. The only things that match up are the last name and the timeframe (and even the timeframe isn't perfect. September 19, 2009.) No idea beyond that whether that's the "correct" Webber couple. (Also, the wedding registry page doesn't mention whether Megan took the Webber last name. If not, and if the t-shirt is related, I'd think the t-shirt would use the term "Webber/Lange Wedding" or some such rather than just "Webber Wedding". But who knows.)

    I checked the Wayback Machine hoping an older version of the same page a) might be available and b) might have more information than the basically no information that the current version of that page has, but unfortunately they don't appear to have any versions of that page saved.

    The source of the page doesn't have much information (aside from what's visible in the page, the URL, or the title of the page) except for a zip code: 90049. Probably where Megan and Thomas live.

    Again, no idea if that specific Megan and Thomas are related to the t-shirt. But I guess there's a small chance.

    Edit: I guess you could contact screen printing companies in LA near that 90049 zip code and see if you can find a screen printing company that will admit to having made that shirt. They might be able to tell you the story of it. If there's a tag in the shirt, it might even say the name of the screen printing company.

  • Short answer: yes.

    I was definitely looking to do a game that was basically as far from "railroad" as possible. And Dungeon World (the system in which we were playing) definitely encourages that sort of way of playing. (Though to be fair, we weren't doing Dungeon World quite how it was supposed to be played. There was player churn at the beginning of the campaign, so trying to ) It definitely ended up being more "comedy" than I anticipated, but the players loved it and I got some great stories out of that game. (Well, mostly the one story I just told, but yeah.)

  • I was GM'ing this game. The premise was that the goddesses created the world as this perfectly idyllic place -- an absolute utopia that I frequently compared to Mayberry RFD -- until the shit hit the fan. An ancient evil awakened and turned it into an absolute post-apocalyptic wasteland. Except for the single most populous city which the goddesses managed to shield from the corrupting influence of the ancient evil (before themselves succumbing to the corrupting influence). (A few fortunate pockets here and there also escaped the corruption.)

    The PCs were the most murder-hobo of murder hobos. There was a town of halflings who continued their happy lives from before the calamity by day but turned into demons by night, not remembering anything come morning. The party marched them all (children included) into the schoolhouse, barricaded them in, and set fire to it. When they ran across a few dwarves who had retained their sanity, they robbed them blind. In the one city which was fully shielded from the ancient evil, they fireballed a procession of a dozen or so devout monks to take out one cultist hiding among them. That all just to name a few of their heinous crimes.

    Of course, in response to all of this, the central city put out arrest warrants on the party. They were going to be dragged into court and hung out to dry whether they liked it or not. I had a whole court scene planned.

    But it never happened.

    They sneaked into town, publicly executed the mayor and the sheriff, and installed the local crime boss as the new mayor.

  • Elon's pet LLM chat bot. The one that he recently tweaked temporarily(?) to spread South African "white genocide" conspiracy theories on Twitter because... well because what else would you expect Elon to spend his time doing?

  • I want everything to be owned by myuser, group media

    Wait, "everything?" Yeah, that's probably contraindicated. You don't want to be changing ownership of stuff in, say, /etc or /bin or whatever to your user. For the most part, stuff in those locations should be owned by root:root. If there are exceptions (things that should be owned by root:

    <something else>

    ), the package manager will make sure they're set as they should be.

  • Yup. Entirely possible. Blocking third party cookies might somewhat reduce sites' ability to tell that you're the same you on the same browser between VPN and direct connection, but even that isn't any guarantee that Linkedin (and/or the ad providers Linkedin uses) and Spotify (and/or their ad providers) don't know you're the same user between VPN and direct. And if there's some amount of collusion and/or purchase of user tracking info going on between those entities, even only first-party cookies are sufficient for them to be able to prove the link between your direct and VPN IP addresses. Even without any cookies, though, there are still browser fingerprinting techniques that are worth looking into if you want to know more about defeating that sort of tracking.

  • The way I've embedded magnets in prints in the past was to:

    • Design a magnet-shaped (plus like 0.2mm of clearance) cavity into the print, but leave it completely "closed off" to where it's "inside" the print.
    • But only "closed off" by like 2 or 3 layers (I was printing at 0.2mm layer height for this particular print).
    • Use "pause at layer" functionality in my slicer (I used Cura at the time) to pause just before the first layer that would "close off" that cavity.
    • Start the print and when it pauses, drop the magnet into the cavity.

    Yes, I was a bit nervous about the magnet potentially jumping up and sticking to some ferromagnetic metal that's part of the print head, but that didn't happen in my case. YMMV, I guess.

    I guess theoretically it could also be the case that the heat from printing could weaken the magnet, but again, that wasn't an issue in my case.

    Just to elaborate on what my project was, I had a freely-spinning part that I wanted to be able to fix in place or unfix. I fashioned a "stop" that when engaged would fix the freely-spinning part in place. The way it works is that the stop can move freely up and down. Putting it in the "down" position fixes the freely-spinning part in place and gravity keeps it engaged. But to disengage it, you slide it straight up. At the top of the "track" in which it slides is where I put the magnet. I used the same technique as described above to embed a little stack of about four staples into the stop itself. So, by sliding the stop to the top of the track, the magnet attracts the staples, keeping the stop disengaged until you pull it back down again to where gravity will keep it engaged until you move it back up.

  • Also, I'd really like to know who made the art.

    I choose to believe the person on the other end of that text conversation fired up Gimp and made the image when they got the request for "funny shit".

  • Anyone want to place bets on how long it is before Elon uses this as an excuse to whisper in Trump's ear that he needs to classify the Fediverse as a terrorist organization? It'd conveniently shut down competition with Xitter (and other billionaire-owned social media sites) if Mastodon (and Lemmy and PeerTube and Diaspora etc) was shut down for "RaDiCaLiZiNg fErTiLiTy ClInIc BoMbErS" or whatever BS.

  • Then make the "one true frontpage" for Lemmy or whatever (implement ActivityPub, maybe borrowing some code from the Lemmy codebase itself, or kindof making a fork of Lemmy), and if it's good, it'll be used. If not, it won't.

    But then, it might well fall victim to this phenomenon:

    Lemmy has lots of competing "front pages." How will one more change anything? A more generic domain name or something?

  • Very probably if you can't think how it would be beneficial for your use case, it won't be beneficial to your use case.

    "Website" (as opposed to "web app") sounds like something static with no server-side logic (save serving up static content) which further makes Docker not seem very useful for your use case. In your shoes, if I haven't inferred too much, I'd probably first think of some CloudFront/S3-based solution.

    Typically, Docker is used in cloud infrastructure (AWS or the like) in situations where there's a lot of server-side resource usage and you want to be able to scale up on very short notice. It can also be useful for on-prem sort of situations, or for if you want to run server-side software in a "contained" sort of way where you don't have to install your software's dependencies on the host machine. (Running a Java app on an EC2 node without installing a JRE on the instance, for instance.) Docker is also good (particularly relative to PaaS options) for minimizing vendor lockin (though, again, only really if you have server-side logic to contend with, and if you're dealing with a static website, it's hard to imagine vendor lockin being an issue.)

    I suppose you could shoehorn it in. Stick your static website on an EC2 node with a Dockerized Nginx to serve it, or even bundle your static website into a Docker image, but I'd imagine you'd pay more for such a solution than just using CloudFront with S3 or whatever.

    (And yes, I keep mentioning AWS, but there are lots of hosts out there. For the more focused LAMP-stack-providers rather than IaaS options, Docker would be of even less use.)

    Now, even if you do intend to have server-side logic, I'm not sure Docker really adds much to the conversation unless your server side logic is expected to use a fair bit of CPU and/or RAM, you're expecting to get a good amount of request volume, and you want to be able to scale horizontally very quickly.