• 3 Posts
  • 386 Comments
Joined 6 年前
cake
Cake day: 2021年1月21日

help-circle


  • Honestly AI has been used for moderation for decades. The newer models will be quite effective. It could be very useful for limiting lower effort spam. Sure dedicated spammers will figure it out and get by it but as the models get better that will get harder.

    Of course like every use of probabilistic technology like AI it should still go to human review. We shouldn’t be shadowbanning people because computer said no. But holding suspicious posts in a review queue for the moderators seems quite reasonable (much like they already do with their current systems).

    Honestly this sounds more like an investor update showing how innovative we are using modern technology and how it is going to really improve the platform and stonks will go up up up than any meaningful change to their current moderation systems.


  • I also used to read a lot as a kid then stopped for a long while. I have gotten back into it by reading before bed. I try to get to bed at least 30min early on most days—sometimes much earlier if I am having a lazy day or otherwise feeling like I don’t want to stay up—then I get a bunch of reading before bed. As a bonus reading makes me sleepy so I always nod right off when I put the book down (or sometimes have to put the book down because I am falling asleep and can’t keep my eyes open) I’ve managed to finish a good number of books already this year.

    But I think the moral of the story is just find some time that works for you, reserve a bit of time in your day and try to make a bit of a habit out of it.






  • declaring multiple variables is less error-prone than in C. In C, the following declares x to be a pointer, but (surprisingly at first!) y to be a normal integer:

    int* x, y;
    

    Whereas the equivalent in Go does what you’d expect, declaring both to be pointers:

    var x, y *int
    

    I don’t think this is a related at all. C could have easily decided that the definition makes both x and y pointers. They just decided not to so that you can declare more variables on one line by being able to do int x, *y, **z, .... It is more flexible.

    Similarly that Go line could have been parsed like var x, (y*) int if they wanted to. They just made a different choice.






  • The fact is that it depends and it is a bit confusing for people not familiar. But it isn’t hard to get used to.

    +8Q, Paris isn’t specific enough. There are multiple +8Q inside Paris. It can also be a bit risky to make short codes like this especially with larger cities as different maps may put the city in different spots.

    What does work is +8Q Eiffel Tower which is useful for something like “Meet me here by the Eiffel Tower” or “I’m right here” when you are texting someone you are meeting and you know you are close but can’t see each other.

    So you end up with a few common options:

    • +8Q Eiffel Tower We are pretty close together but need to get the exact spot.
    • V75V+8Q Paris, France For exact spots around a known area.
    • 8FW4V75V+8Q For fully qualified with no reference needed.

    And a few less useful options:

    • 8FW4V7+ This large part of a city.
    • 8FW4+ This part of the country.
    • 8F+ This area of the world.

    If I was designing the system I don’t think I would have done this “trailing zeros assumed” approach. Because IMHO for day-to-day use V75V+ Would be more useful as a shortcut for ????V75V+ rather than the actual V75V????+ showing a rough location on a human scale (in this case the Eiffel Tower park is pretty clearly targeted) rather than an area larger than a city. But that is really the only complaint I have.