• 4 Posts
  • 545 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2023

help-circle


  • Yeah, I’m pretty sure my family was only the second owners of my house as well. All I know about the builder of my house is:

    • The same guy was responsible for building basically all the houses on my street.
    • He didn’t survey very carefully. All the property lines are off by like two feet. Lol. It’s caused me some heartache with the neighbors to my south with property disputes. (Well, to be fair, the neighbors to my south would have caused the property dispute had the property lines not been off.)

  • TootSweet@lemmy.worldtoAsklemmy@lemmy.mlWhen was your house built?
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 days ago

    Oh, I think I know what’s going on. It’s interpreting the number with a period on the end as a numbered/ordered list. Putting a space before the dot should fix it.

    1. This is an ordered list.

    And fixed:

    321 . And this is not.

    Still weird that the number’s sticking off to the side and getting cut off. Probably depends what client you’re using. In Lemmy-UI, it’s not cut off, but the number is further left than it would otherwise be. Jerboa looks fine, but it’s clearer on Jerboa that it’s interpreting it as an ordered list.



  • One could make a community named “Anon Posting” or something, lock it so only a mod can post, and then make the sole mod a bot that would post anything it got via DM (probably after automoding, rate limiting, etc) to said community.

    I do think it’s a good idea for the bot to keep a log in case it gets abused for sufficiently evil purposes. One could add some extra functionality to the bot that would give identifying information about the poster to instance admins on demand (via DM), but I think instance admins would have pretty easy access to all DMs made to the bot, along with identifying information anyway. (Feel free to correct me if I’m wrong on that.)

    Also, the bot could totally delete its logs and with them the identities of all posters after a while. Maybe a month?

    And, of course, this wouldn’t be ironclad anonymity. But it would keep identities secret from anyone but the bot maintainer and instance admins.

    Yeah, sounds like a pretty cool concept. Not volunteering to write such a bot (at least any time soon) or anything, but I support it.








  • Yeah, I think “a slice of bread” is a lot more common than “a bread slice”. Not to say I haven’t ever heard “a bread slice” used. I’m sure I have at least a few times. It would be pretty rare, however.

    Though, I’m not sure “a pizza slice” is all that much more common. Maybe there are regions where it’s very common? Or maybe it’s more common in certain contexts? Like maybe sell-by-the-slice pizza places might tend to refer to “a pizza slice” rather than “a slice of pizza” when talking with coworkers? (That said, I’d imagine they’d just shorten it further to “a slice” since the “pizza” part would tend to be obvious in that case.)

    Also, @eager_eagle@lemmy.world mentioned “water bottle”. I think if I hear “a water bottle” rather than “a bottle of water”, I’m probably going to assume it may or may not be an empty bottle intended for water rather than a bottle filled with water as “a bottle of water” would imply.

    Way off the topic of programming, but linguistics is fascinating too!


  • The Go programming language documentation makes a big deal about how it “reads from left to right.” Like, if you were describing the program in English, the elements of the Go program go in the same order as they would in English.

    I say this as someone who likes Go as a language and writes more of it than any other language: I honestly don’t entirely follow. One example they give is how you specify a type that’s a “slice” (think “list” or “array” or whatever from other languages) of some other type. For instance a “slice of strings” would be written []string. The [] on the left means it’s a slice type. And string on the right specifies what it’s a slice of.

    But does it really make less sense to say “a string slice”?

    In Go, the type always comes after the variable name. A declaration might look like:

    var a string
    

    Similarly in function declarations:

    func bob(a string, b int, c float64) []string { ... }
    

    Anyway, I guess all that to say I don’t mind the Go style, but I don’t fully understand the point of it being the way it is, and wouldn’t mind if it was the other way around either.

    Edit: Oh, I might add that my brain will never use the term “a slice of bytes” for []byte. That will forever be “a byte slice” to me. I simply have no choice in the matter. Somehow my brain is much more ok with “a slice of strings”, though.




  • I gave you an upvote.

    I could see a case for using “working person” instead of “worker.” It’s definitely not the sort of thing that’s agreed to be exploitative language (yet?) though.

    What I do for sure bristle at a lot more is referring to people as “resources.” Like, when planning a project, discussing how many “resources” can be “put on the project”. Definitely feels dehumanizing.


  • 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.