• 1 Post
  • 83 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle


  • So first of, the part of my comment that you quoted doesn’t make sense because what I’m saying is that bluesky theoretically allows for decentralized relays but it’s impractical in practice. Your analogy doesn’t really apply to that.

    I do think that it’s misleading to call bluesky decentralized today (at least without any caveats). The goal of the project however is to eventually create a more meaningfully decentralized social network and they have tangible plans for moving in that direction so I think it’s unfair to dismiss this aspect of bluesky completely.


  • I think that it’s fair to want the interviewer to ask more critical questions and in general be more precise with their phrasing but

    repeat that PR talking point

    is a very cynical and uncharitable take on bluesky and decentralization. Cynical takes aren’t necessarily wrong but they’re not necessarily correct either.

    The AT protocol is by its own account an ongoing project with problems that still need be solved before it is able to provide a social network with all the properties that they’re interested in.

    I don’t think that it’s accurate to say that bluesky is “completely” centralized (it is less centralized than most social media) as much as it’s de-facto centralized. One reason for this is that it’s prohibitively expensive to self-host relays. This is something that the AT protocol devs have plans for addressing, so it’s possible that this de-facto centralization is a temporary stage in the evolution of bluesky and AT proto.

    It is of course possible that they are lying or that they will be unsuccessful despite best intentions but taking for granted that it’s just a “PR talking point” is, once again, very cynical in a way that I don’t think is completely motivated.






  • I don’t know that it’s the “algorithms”: a lot of people just use their following feed on twitter and although it changed a while back that was the default feed on bluesky for a long time. I think that there is a fairly large portion of bluesky users who mostly just look at following and still don’t really like mastodon.

    Imo, a big reason why bluesky has been a more successful twitter competitor than mastodon is cultural: mastodon has been around for years before musk bought twitter, and a big selling point was that it wasn’t like twitter, for example that its “less toxic”. A large part of mastodons userbase never liked pre-musk twitter that much and will tell you of for acting like you would there. Bluesky on the other hand has a large portion of users who liked pre-musk twitter and are happy to follow pretty similar social norms as they did in pre-musk twitter.

    This is to some extent reflected in the functions of the different sites as well, for example you can’t quote retweet on mastodon which iirc is deliberate because qrt dunking is “toxic”. Bluesky has quote retweets (although they allow you to untag yourself from a qrt).











  • Helix has better defaults for sure and I get why people might prefer it but I have a very hard time imagining it being a better choice than vim in every situation even with a lot more development.

    Also, if you work with programming for example your editor is going to be one of your main tools and I think that “reading guides” is an acceptable amount of effort to put in to learning such a tool. Vim has a higher barrier of entry than it needs to (this can to some extent be explained with backwards compatability) but with Helix you still have to put some time in to understanding the editing model anyway.


  • The biggest thing missing from helix right now imo is plugin support, so a lot of plugins that I really like wouldn’t be available. I use fugitive a lot for working with git for example.

    Another one is the quickfix list in combination with ex commands. One thing you can do for example is setup :make to run your compiler and then when you get compilation errors they’ll show up in your quickfix list. You can then use :Cfilter to focus on one type of error and then :cdo to for example do a find and replace on the remaining lines.

    In general, if I don’t have an lsp available for whatever reason (I work in cmake a fair amount at my $DAYJOB for example) I would much rather use vim, in particular because of the stuff that you can do with ex commands that I mentioned above (also works great with grep) but also because of the ctags support.

    Helix can do a lot of nice things out of the box for a lot of cases of software editing, but it’s not nearly as broad or as customizable of a tool as vim