• 0 Posts
  • 64 Comments
Joined 2 months ago
cake
Cake day: January 24th, 2025

help-circle


  • RE: The biggest problem about this is the API definition. Libraries have APIs. But in a completely different way, webservers have APIs. If I say “we are going to a conference on API’s” what do you hear? That we are going to talk about REST, GraphQL, or gRPC, or web server APIs of some type. This is common phraseology. However, one time I was invited to such a conference, and it ended up being about C# design philosophy.

    In that way API is an adjective (REST API, C# API, …) AND a noun (webserver API). That’s a problem.

    And as an adverb, there is some justification to replace it with Library and others (REST Endpoint, C# Library)

    Because otherwise all public functions are API’s, which doesn’t seem necessary to me. Saying a Library has an API is somewhat redundant. Saying a server hosts an API is not, many servers run jobs or databases. Many websites don’t host APIs. Etc.











  • artificialfish@programming.devtoFediverse@lemmy.mlHow to get people to use Mastodon?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    16 days ago

    That’s merely an anchoring effect. Mastadon was the first of those technologies, and activitypub itself was heavily inspired by replicating Twitter so it was also the most straightforward implementation. Lastly, a lot of the far more favorited social media platforms rely on either strong content creators or social network effects to succeed, whereas Twitter creates enough bubbles and is less focused on people you actually know IRL that it doesn’t suffer as much from this problem.

    You don’t understand correlation and causation apparently, just pointing at stats and grunting without reasoning about them. The effective number of people using fediverse platforms being almost inverse of the number of people using non fediverse platform corollaries shows if anything that fediverse itself is facing an adoption problem, not that Twitter is the best platform for it to emulate.








  • Well I think the first thing is just simply that documents aren’t notes, so you wouldn’t write those things in Logseq.

    What you are writing in Logseq is a zettlekasten, which is just a personal knowledge graph. And in a knowledge graph, everything needs to relate somehow to everything else, that’s why it has to be an outline.

    So things can relate to the journal date they were written on, to their parent and children concepts, and to the links that they contain. Every idea has at least a relationship to the date you wrote it, but hopefully you can link that idea to more than just that relationship. You want to organically rediscover that next time you make a cake, that eggs are bad for your allergies, and be able to trace that you discovered that at this doctors appointment on this date.

    Otherwise, how would you ever find anything? And more importantly, how would you rediscover it organically when researching other concepts in your graph?

    Obsidian purports to help you create organized knowledge graphs, but it makes you plan your organization up front. Logseq lets it evolve naturally and organically, by giving you the necessary tools and constraints.