• 3 Posts
  • 28 Comments
Joined 10 months ago
cake
Cake day: December 1st, 2023

help-circle




  • Ok, so I heard a thing a long time ago about information density in languages, and that there’s a specific amount of information conveyed per second which is pretty consistent across languages, even when the number of sounds is higher or lower.

    This is true.

    Which means that a single word in English, for instance, would convey more information than a single word in Hindi.

    I don’t think that’s the right interpretation. There are words in English that would require sentences to be made for each if conveyed in a different language. But the same is true vice-versa.

    Have a look at subtitles for movies from one language to any other. Translators struggle conveying what should be paragraph long sentences of context behind a single word for one language. Do not get me started on double speak.






  • I don’t think Lemmy or Mastodon would be a good place to start necessarily. Don’t be discouraged, I just mean that I think this should be something separate, like a library,

    True. I meant suggesting this idea for generally any website that uses tagging. Will update post to show this better.

    As a code library it could be maintained elsewhere and let these folks keep working on their projects.

    We would need a group like the Wiki Foundation to set this up. Though I wouldn’t know how to pitch this.




  • That is more of an argument involving the implementation of tags in general within the federation. But to answer your question:

    Let’s say a group of people were to make a post on Mastodon with the tag #girls_night. How will all instances agree on the tag being correct?

    The simple answer is they won’t. If a tag is contentious, it will be like any other drama between instances.

    It’s the same for implementing tag hierarchy. Let’s say there is a default setup. Then if a tag or a tree of tags is contentious, each instance can include or exclude as they see fit.


  • Two new tables for “tags” would be required. One for instance wide tags and one for community tags.

    a curated list of tags users can attach to their posts. The list of tags can be maintained by both admins and moderators allowing for each community to tailor tags to their specific needs.

    It’s not what I was suggesting, but this should definitely be implemented for Lemmy.

    I’m talking about how some tags should directly relate to one another, and how this should not always be the case in vice-versa. The system I’m suggesting is less useful when you limit the scope of tags (as the RFC does), but you can’t really do that for user-centric websites like Mastodon.

    I think I’ll make an edit to clarify this in post.





  • I’m interested in a long time investment that will grow as I will

    As long as you pick up shortcuts from any editor you’re used to and can implement them or something similar in any hackable editor, you’re growing long term.

    Emacs and (Neo)Vim have passed the test of time and I honestly don’t think they’ll cease to exist in the upcoming decades

    Neovim will exist on account of being a lightweight refresh on Vim that, due to issues with the Vim owner, was able to gain enough momentum to take off.

    Emacs I’m not so sure. If you’ve checked the news anytime for Doom Emacs, you can see the maintainer mentioning how it’s become progressively difficult to maintain the project. I’d imagine it’s a similar story for plugins and other derivatives. People have attempted remaking Emacs from scratch, but there was not enough momentum for it, so that went under.

    There are a lot of beautiful plugins for both Emacs and Vim that personally, I wish could exist as programs separate from these editors. Have you had a look at the design philosophy behind Kakoune?

    “Kakoune is expected to run on a Unix-like system alongside a lot of text-based tools, and should make it easy to interact with these tools. For example, sorting lines should be done using the Unix sort command, not with an internal implementation.”

    This would stop so many tears being shed for deprecated plugins if they just focused on being a separate program that can interact with whatever code editor you want, be it VSCode, Vim, Emacs, etc.

    I also recommend reading this article here that goes more in-depth on this point and has a comparison of vim, helix and kakoune.