• 73 Posts
  • 159 Comments
Joined 2 years ago
cake
Cake day: August 24th, 2023

help-circle




  • i’m no longer sure if you’re envisioning a web browser or a website builder. your terminology is all over the place.

    I’s blurring the line in-between. It’s trying to set the interaction with the web on a lower level that is closer to the data. It’s like you are live-coding the website you want to use for a specific use-case. But then just call the high-level API-endpoints right away. Basically making the dev-tools and the dev-console of browsers the main way to interact with the web (which assumes a web that is build in a similar fashion).

    and no, the semantic web is in no way an an open, global codebase. it’s just a way of structuring html. i know berners-lee wanted the web to be more like what you are describing but the web we have today is not that. you’d need a new protocol.

    Yeah, that’s true :(


  • I don’t know. Basically, if you already know what you want, maybe you only want to type down a couple of statements (maybe even from a template or a tutorial that you found online), modify some stuff and then hit enter. And maybe this modifying of language could be the “browsing” part of the browser.

    If you look at it like this it would also be immediate and precise. You would only need to add very good code completion tools, e.g. when you click on a noun, you see all the attributes it has in your ontology. Much like in a IDE. There you also “browse” the space of all potential programs with the interface of language with code completion for keywords and defined concepts, which act like links in traditional browsers.

    In contrast, the semantic web is like a open, global code base, where everybody can contribute to. And traditional browser could not successfully implement a language interface because the code base had no defined semantic, this would be possible for the semantic web. And using LLMs, it could be propagated into other web paradigms.







  • I think it can very well be applied to the Threadiverse.

    • Sin #1: The First-Move Problem - Doesn’t really applies for the Threadiverse, because the instances (at least for me) do feel genuinely different, with a different culture, etc., which is one of the most exciting things for me here
    • Sin #2: Navigation Inconsistency - Basically the same here.
    • Sin #3: Remote Interaction Hell - Also the same here, right?
    • Sin #4: Private Mentions Aren’t Really DM’s - Same here, right?
    • Sin #5: The Phantom Social Graph - There definitely are synchronization issues on Lemmy, too (see the australian instance, which, I think has a latency of a week of so per post :D). Otherwise because the Threadiverse is still rather small, it seems to work mostly fine.
    • Sin #6: The Discovery Problem - Much better on Lemmy. The algorithms are both transparent and make the threadiverse feel alive even though it has much less user.
    • Sin #7: Basically doesn’t apply here, because you don’t follow users, but can be applied for communities. And multiple of the same communities on different instances are a big problem of the Threadiverse. Also abandoned communities. PyFed solves this with topics and Lemmy also has an upcoming feature for this in v1.0 I think.

    I think the most pressing issue is sin#7 if applied to communities.

    In an abstract sense, I see the Threadiverse as inversion of Mastodon: instead of posting messages to a personal account, which tags may be interesting to you to discover other similar content, in the Threadiverse, users post to hashtags and who posted them is only secondary important to you, but may be used to discover more content by the same account.