also lnkr

@voltmor полностью отказываться от консолей уже тоже необязательно, в набор свежего "невероятного" так же входит как перешивка консолей в линуксовый ПК, так и порты эмуляторов и ПК-игр на консоли

@th3rdsergeevich

ActivityPub servers written in PHP: Friendica, Pixelfed, Mbin, Hubzilla, Castopod, Loops, Streams, Forte, WordPress and Nextcloud plugins.

Fun times are ahead.

@panos @catodon-talks @julian wait, that can't be right. Lemmy does not do that, it doesn't have the top-level url in post AP object at all, neither I ever had this issue with Lemmy linkposts and I can't reproduce it now, it's original post url resolves correctly, even on Mastodon.
And NodeBB source at least gives the impression that it can pull the href from attachments?

@catodon @panos I just noticed that the link that's supposed to be the url of the original post is instead federated as the link from the post. Can't imagine this being intentional

@drq по касательной идею уже цепанули https://github.com/DenisSergeevitch/simcity3000-gta-mode
Но да, что-то поактуальнее было бы прикольно

Кажись, селфхостное решение дискордового вопроса пришло не совсем откуда ждали - lain обвайбкодился поверх mumble. Сейчас активно дошлифоввывается, но уже выглядит и фурычит недурно, вроде уже видеоконфы и стримы через OBS есть, пока не пробовал, правда. Заявляется смехотворное потребление серверных ресурсов, но это мы ещё посмотрим.
https://github.com/lambadalambda/kallisti
Планирую попозже захостить, сейчас пощупать можно на https://chat.kallisti.chat/, логин есть гостевой и вот сегодня ещё через федиверс появился.
Это давай, это надо.

@wakest fixed

@wakest fixed

@ZySoua
https://imgur.com/user/Artgasm
https://imgur.com/gallery/terrible-griffins-AYY0QUA

I've had enough of FEP-044f quotes. It was a heavily undercooked proposal that may have had some good intentions on paper, just maybe, but ultimately did more harm than good. It was fairly error-prone to begin with, and that was only made worse by a lot of fediverse servers underimplementing it, sometimes intentionally. Actually following it to the letter leaves you with a timeline full of unusable quotes that are left eternally in a pending state.
There is no good solution to this other than to withdraw it as an unreliable mechanism and rewrite the thing into something that makes sense. Until then, #plamenu will show pending quotes to its users as resolved while still following FEP-044f rules internally. As a result, the state of the quote post you're seeing in your timeline is no longer indicative of what your Mastodon followers would see should you repost or requote it. It's no longer my fault or my concern.

@drq

@wakest oh there is a number of super weird issues that I saw on mobile firefox specifically (not this one tho). I'll have to address this eventually

@wakest there are some funny issues with old CSS getting cached, can look like some big pink SVG icon all across the screen, I never saw it on mobile but a handful of times on PC, usually resolved with Shift+Ctrl+F5, still not sure what's causing this, as far as I'm aware the way I'm updating JS and CSS between releases should not reuse some obsolete browser cache.

But I never saw anything like this. What even is this cog, I don't think I have this image anywhere on the instance. Feels like some sabotage by Google Translate plugin to me lol

@wakest ooooh, thanks for that example! I forgot to check if chapters are working, seems like they do!

@wakest I'm not aware what Holo did exactly, but, again, in terms of server to server interactions, Plamenu will continue to play by the FEP rules. Quoting other Plamenu instance post won't cause any issues, quoting a post from some other instance A that don't respect this FEP will cause the issues for followers from instance B that do fully respect the FEP. In that scenario, Plamenu is just a middleman doing everything by the book, and the actual issue is the interoperability between instance A and instance B. I can't solve that, it's not up to me.

@wakest I'll continue to support full FEP-044f but will show the unresolved quoted posts to local users. This won't change anything for Mastodon instance that happens to be at the end of the federation chain, botched quote will end up pending either way. For Plamenu user the effective tradeoff is whether you can't see the quoted post and you are getting the same picture as the Mastodon server located down the line, or you can see the quote but chances are you are probably unaware that your mastodon followers can't.
None is perfect, and the only transparent solution to this it to disallow making quote posts at all, ever. At this point I don't want to make my and other users experience worse just because maintainers of other server implementation has decided to make theirs worse.

@wakest Oh I knew it would eventually happen and I missed something when I added support for inline media. Shouldn't be hard to fix.

Also I think I had enough of those pending quotes, honestly, fuck that, entire proposal was severely undercooked anyway. Aside from a few servers, barely anyone cared to properly implement FEP-044f and it's undeniably doing more harm than good if under-implemented. I think I'll make Plamenu display pending quotes as accepted ones and only hide it if it was explicitly rejected by the user (which I saw happening exactly once).

@wakest ok let's see. I'm having huge issues getting anywhere past the initial lookup on that peertube instance, still don't think it's in healthy state

@你好
@groeibschi@peertube.gröibschi.ch
@Вежливый_Лис

@wakest yep! (why the hell is it not already working)