@jae@dcc@hj@sun >recommend some sort of ide with linter elixir-lsp is very meh and is one of those LSP servers that compiles everything on the fly with the actual compiler, meaning that your laptop will lift-off after daring to open a single file, or changing some module with a hot code path.
At least the diagnostics the compiler gives you are usually good and the new compile-time type checking is mostly smart-enough. Although it triggered a false-positive up once with Pleroma's object validator. https://fluffytail.org/notice/Au1Mbn33jOmDEgzPtI
@sun@dcc@hj Yeah, it's not trivial to work with and in certain areas very error-prone. Like when the Activity type handling got changed and Block Activities weren't added into some hard-coded list of accepted values which made blocks non-functional on remote instances while the local one though that everything was alright. It's very easy to make a mistake with weird consequences.
> i don't like to complain about pleroma Me neither, there isn't anything like it yet, that is proven to scale (mostly) reliably. There's Mitra which focuses even more on interop, but Rust isn't my thing and my brain shuts off after looking at it for an hour or two. Rust is a weird mix of C++, Haskell and Erlang that no matter how hard I try, I cannot wrap my head around.
@dcc@hj@sun Elixir isn't a hard language when you look at it with a clean mind. But if you decide to try it, don't go nose deep into Pleroma internals like I did, because that will be painful. The code itself is mostly very readable, but figuring out the flow of it is usually not pleasant. I've had many moments when I wanted to throw an IDE at the whole thing just to make it easier.
@sun@hj I think this can be even improved upon. Instead of having an instance-wide bubble timeline, it can be a user-specifiable timeline alá Lists. Instead of users, it would be instances.
And the Akkoma-specific Bubble functionality in the backend that replaces relays on their end, could be handled with the same mix task, but perhaps with a flag that switches the default handling. Although Akkoma might be doing some weird things when it comes to accepting becoming a member of a bubble timeline.
>but SOMEONE has to do the work there Yeah, I'm not feeling even barely competent enough for it too and I don't want to break things uintentionally again like I did recently.
@sun@hj I don't see any reasons why it should be implemented in the backend. Pleroma has relays which serve basically the same purpose. If you can set a timeline of instances in the FE, that's 90% of the functionality. Is there something I'm missing?
Not to turn this thread into another typical Akkoma vs Pleroma thread, but I think the bubble timeline (fetch all posts from instances there) in Akkoma's backend was specifically made to break compatibility with relays which where changed to be off by default.
@hj >User backgrounds on profile pages - probably no due to privacy concerns It's already implemented: Settings->Profile->User background (after banner)
@prettygood@SuperDicq@vic Maybe, I don't have a Pixel to try it on anyway. Microg should a normal uninstallable app (at least is on OSes that don't include it by default).
@prettygood@SuperDicq@vic Calyx is basically the same without the schizo part and uses microg instead of Google Play Services in a sandbox that is supposed to be secure.
@vic@SuperDicq It only runs on Google hardware because apparently Google hardware is the only truly secure one. Whatever that means.
I'm almost convinced that Daniel is some government implant and the only thing stopping me from truly thinking that is his extremely paranoid schizophrenia. I'll never use it anyway, since I can't trust an operating system written and still maintained by a schizo that has an extreme grudge against anyone that even slightly disagrees with any of his takes.
@SuperDicq The infosec crowd loves it and you can't expect any kind of reasonable thinking from that crowd. Daniel is so up Google's ass that literally anything that isn't from Google is deemed insecure. He has the same grudge against microg thanks to some old bug that got fixed years ago. He also blindly trusts Google's Titan "security" blackbox. grapheneos-british.png grapheneos-random-vpn.png