• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle

  • Yeah, I think “forumverse” isn’t bad. Though I have always felt like a Reddit-like interface and a forum interface are fundamentally different, in some way I can’t really put my finger on. I’ve been involved in bulletin board forums (fora?) in one aspect or another since the late 90s, so maybe it’s just nostalgia vs. recency bias; though it could also be the feeling that a “forum” seems like it should be hyper-specific, with different subforums on an already-niche bulletin board scoping down to even more niche and specific areas.

    (Side note: Actually, now that I think about it, maybe the forum -> topic -> thread connection is why people like the name “threadiverse.” The word “thread” definitely seems like it arose from there.)

    Anyway, I am fully ready to admit that I’m yelling at clouds here. Get off my lawn, dang kids and all that.



  • I don’t think likes serve the same function as votes. The downvote, the ranking as a function of score and recency, and the surfacing and consensus-building that comes as a result are the main point of this sort of platform.

    By contrast, the microblog “like” (at least on a platform without an algorithm, like Mastodon) doesn’t do anything other than express appreciation.

    Threads are common in pretty much every form of social media now, from friend-aggregation sites like Facebook and Friendica to messaging services like Discord and Revolt. They’re hardly exclusive to a Reddit/Lemmy-type service. Mastodon even organizes posts into threads (though I think that it does so in a much more clumsy way).

    (Edit: by “don’t they have votes?” do you mean polls? Because that’s a completely different function altogether than the Lemmy/Reddit vote.)




  • Samsung actually added Knox to their Android implementation a few months before iOS added Secure Enclave. I think Qualcomm had some sort of trusted execution environment around that time, too, if I recall correctly. And Google added Trusty to the AOSP two years ago. So it’s already running on Android, and has been for ages.

    But I’m not convinced a TEE would be necessary for a device that doesn’t run any third-party native code. Browser tab sandboxing is already pretty robust; I haven’t heard of an escalation exploit being found in ages on any major JavaScript engine, meaning that the risk of data exfiltration or bootloader compromise are extremely remote, and would be much quicker (and less risky!) to patch via browser updates than firmware/OS updates.

    The only other reason I know of that you’d need a TEE is for DRM, and I’d be willing to wager most people who would want a FirefoxOS phone would actively prefer not to have that on their device.







  • It’s not thinking. It’s just spicy autocomplete; having ingested most of the web, it “knows” that what follows a question about the meaning of a phrase is usually the definition and etymology of that phrase; there aren’t many examples online of anyone asking for the definition of a phrase and being told “that doesn’t exist, it’s not a real thing.” So it does some frequency analysis (actually it’s probably more correct to say that it is frequency analysis) and decides what the most likely words to come after your question are, based on everything it’s been trained on.

    But it doesn’t actually know or think anything. It just keeps giving you the next expected word until it meets its parameters.