Egregoros

@p @j @Junes @SilverDeth @CrayonEater @ElDeadKennedy @ceo_of_monoeye_dating

That turns them into a reply, sure, but the problem is the same. Once there's a quote post with the same context, the thread usually goes two separate ways making it hard to read through, because there are now two diverging topics. The flatpak v2 systemd thread from a couple days ago is a good example of that I think. There's like three akkoma quote posts in the thread that all keep the same context, including a broken thread thanks to signed fetch.

https://hachyderm.io/users/jorge/statuses/116607961190448307 (https://fluffytail.org/notice/B6Z1k3LoKVhutjVdj6)

I hate Elixir so fucking much.

Yet you really like Ruby. The two aren't that dissimilar. Also there's a third Misskey representation :)

@phnt @CrayonEater @ElDeadKennedy @Junes @SilverDeth @ceo_of_monoeye_dating @j

> Once there's a quote post with the same context, the thread usually goes two separate ways

That happens with threads anyway. It's fine.

As things stand, this is, I believe, an exhaustive list of my options here:

1. Implement quote-posts and then kill myself.
2. Kill all quote-posts by rejecting them at the MRF level.
3. Turn quote-posts into replies.
4. Hack into all servers that implement quote-posting and remove the code that supports this terrible misfeature, thereby killing this problem at the source.

I chose option 3. I didn't like options 1 or 2.

> The flatpak v2 systemd thread from a couple days ago is a good example of that I think.

I haven't seen it.

> https://hachyderm.io/users/jorge/statuses/116607961190448307

hachi derm dot input/output (one of the Individual Eleven) refuses to allow FSE to fetch posts from them.

> There's like three akkoma quote posts in the thread that all keep the same context, including a broken thread thanks to signed fetch.

That's Akkoma's problem.

> Yet you really like Ruby. The two aren't that dissimilar.

Well, I haven't ever downloaded a release of Ruby and found a .DS_Store file in it. Programs I wrote for Ruby 1.6 still work. I have never had to update a separate VM in lockstep with updating Ruby.

"When you mix water and brandy, you ruin two good things." --a guy that thought brandy is good but in any case he is correct about the *principle*

Elixir is like if you took some of the parts of Ruby and shat them into Erlang and then in places where Ruby was nice, you decided to replace it with whatever Python does. As shitty as Elixir is, it's nowhere near as terrible as Phoenix, which attempts to replace sensible Erlang CSP style with shitty Rails shit that sucks and the unrepentant PHP dipshit DHH only made Rails because he couldn't figure out what to click on to see the Logo Turtle when he got a Macook ro. Every time I trace a bug to a five-clause `when` in the Pleroma source code, I get the urge to figure out who is in charge of Elixir and drive to his house.

@p @j @Junes @SilverDeth @CrayonEater @ElDeadKennedy @ceo_of_monoeye_dating

>I haven't seen it.

Nothing of value, like usual. Just a bunch of smug posts from corpo plants in the linux space.

>That's Akkoma's problem.

Including an FSE problem now. But no hard feeling of course, everybody has their own preferences. I'm not a fan of quote posts being used like on twitter either, the "lmao, look at this idiot" trope.

>five-clause `when` in the Pleroma source code, I get the urge to figure out who is in charge of Elixir and drive to his house.

That's one of the syntax features I quite like. It separates the success branch from the error handling below, so they don't mix. Apparently enough people like that feature that Erlang copied it: https://www.erlang.org/doc/system/expressions.html#maybe
fedi-p-old-man-yells-at-webdevs.png

@p @j @Junes @SilverDeth @CrayonEater @ElDeadKennedy @ceo_of_monoeye_dating
>Until you have to debug and it matters which of the clauses failed.

In reality you should wrap it all in a tuple for error handling which makes the issue clear, but it is true that it isn't the case in most code people write, including Pleroma

with {_, true} <- {:check_one, check(var)},
     {_, true} <- {:check_two, check2(var)} do
  process(var)
else
  {:check_one, e} -> {:error, :check_one, e}
  {:check_two, e} -> {:error, :check_two, e}
end

>rails

I think it is fair to say that Ruby is hot garbage. Especially if you need something that doesn't perform awful.

@phnt @CrayonEater @ElDeadKennedy @Junes @SilverDeth @ceo_of_monoeye_dating @j

> In reality you should

What people *should* do and what they did do are often different; what the language encourages, etc. But I didn't write this codebase. Here it is and I have to deal with it.

>> rails
> I think it is fair to say that Ruby

Ruby isn't Rails. Ruby is nice. Try using the language without touching Rails. It's enjoyable. You fire up irb, load up a JSON parser, walk down a data structure, toss a few transformations at it. It's nicer than ever touching jq.

> Especially if you need something that doesn't perform awful.

Player skill issue.