Post B6wPG1Bke820uVbtxI by hj@shigusegubu.club
(DIR) More posts by hj@shigusegubu.club
(DIR) Post #B6fDxuVeL1hznflIKe by kirby@freerobuxextremist.com
0 likes, 0 repeats
where tf is the favicon thats supposed to be next to my name
(DIR) Post #B6fEIYu1rnlOrx0q2a by phnt@fluffytail.org
1 likes, 0 repeats
@kirby It's a frontend config you need to enable on the backend iirc.
(DIR) Post #B6fEIZ7952FtWd9JU8 by lain@lain.com
0 likes, 0 repeats
@phnt @kirby statements dreamed up by the utterly deranged (pleroma dev team)
(DIR) Post #B6fERa0P8U0ktbIK5Q by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt it's enabled already. every other favicon shows up next to other peoples handles
(DIR) Post #B6fERaBOTcnlRgR6DQ by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt it shows up on other instances too. did a weird develop regression cause this problemo
(DIR) Post #B6fFSyVpbaHr98Dugy by phnt@fluffytail.org
0 likes, 0 repeats
@kirby The favicon works when you GET /favicon.png on FRE. Try refreshing FE without using cache Ctrl+Shift+R or something similar what your browser uses. The only change on the backend is that the favicon now has an immutable cache for one day, but that shouldn't be the issue.
(DIR) Post #B6fFSygSy2nHg7CPGi by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt i've f5'd like 3 times already and even going in an incognito chromium window shows the lack of an icon. i also tested visiting fre from firefox and no favicon shown even from there, so its not a web browser issue
(DIR) Post #B6fFvf8yhE3bTQDHYe by phnt@fluffytail.org
0 likes, 0 repeats
@kirby Does devtools network tab give any clues when in incognito windows? Is an error showing up there for the favicon, or console?
(DIR) Post #B6fFvfODmYFaEhLSJk by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt no lol
(DIR) Post #B6fGEtD6cZcmbPJPU0 by phnt@fluffytail.org
0 likes, 0 repeats
@kirby Weird, cc @hj
(DIR) Post #B6fGEtP9tlGXCmx2Gm by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt @hj FRE is a hj-support-less land we use 2.6 fe because modern fe is too slow for my liking. i would bet money this isn't a fe problem though because back when 2.6 was still the latest release of pleroma the favicon rendered fine
(DIR) Post #B6fGGeDvJS2ohVX6OG by hj@shigusegubu.club
2 likes, 0 repeats
@kirby @phnt have you tried recent versions of FE? it should be faster than that god awful version (the one with the loader)
(DIR) Post #B6fGLmkB3unKZd4LoW by kirby@freerobuxextremist.com
0 likes, 0 repeats
@hj @phnt i tried the one that was in develop back in december, didn't feel as buttery smooth as this fe which agitated me when i used the develop fe for a few months so i went back
(DIR) Post #B6fGQCvJfWVivWO7DU by hj@shigusegubu.club
1 likes, 0 repeats
@kirby @phnt what exactly is "buttery smooth" about it, specifically?
(DIR) Post #B6fGoLEsP53PfP2rOy by phnt@fluffytail.org
1 likes, 0 repeats
@hj @kirby I think it's a backend bug, the favicon for the user is returned as null: https://freerobuxextremist.com/api/v1/accounts/kirby
(DIR) Post #B6fGpEcWUreJQfX1Oa by kirby@freerobuxextremist.com
0 likes, 0 repeats
@hj @phnt i go to load a tiemline, and it will load instantly
(DIR) Post #B6fGpEovkjZe39Kvjc by hj@shigusegubu.club
1 likes, 0 repeats
@kirby @phnt i don't get it. Loads instantly to me on recent develop + minor fixes branch.
(DIR) Post #B6fH4tdUHgN6yqS0Cu by kirby@freerobuxextremist.com
0 likes, 0 repeats
@hj @phnt timelines did never load quite as fast on the new fe, perhaps that's cause i was using firefox before and chromium tends to play nicer with new fe but i dunno. i also noticed a timeline tearing issue a couple of days ago when i was wandering around shigusegubu but it seems like you fixed that
(DIR) Post #B6fHF25BjZg04cEzZY by phnt@fluffytail.org
1 likes, 0 repeats
@hj @kirby It probably failed to scrape the favicon and set the DB record to nil, which would then get passed as is to the account view. Or something like that.
(DIR) Post #B6fHPfC3AzjQGjWHGC by hj@shigusegubu.club
1 likes, 0 repeats
@kirby @phnt there's literally nothing different when it comes to loading timelines between FE versions, if it loads faster or slower it's your backend responding slower or faster. The "god awful" version only had additional "initial load time" (thus the loader) on page refresh.
(DIR) Post #B6fHPucpnh4M89ANai by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt @hj is there a test for this
(DIR) Post #B6fIHs2hcSIll1zloW by phnt@fluffytail.org
1 likes, 0 repeats
@kirby @hj Yes, multiple. But if the http request timeout or failed because the instance took a nap due to some heavy load or similar like network dying, it will null out the favicon value in the DB until the next update cycle. If you check logs for Instance.get_or_update_favicon or Instance.scrape_favicon you might get the reason. My guess is that what happened.select host, favicon, favicon_updated_at from instances where host = 'freerobuxextremist.com';if you want to confirm that.
(DIR) Post #B6fIHsTzyy8V7glZMO by phnt@fluffytail.org
1 likes, 0 repeats
@kirby @hj Yes, I know it's kinda stupid to scrape your own favicon, I'll probably look into changing that.
(DIR) Post #B6fIJKAyVOOZIkYeCe by kirby@freerobuxextremist.com
0 likes, 0 repeats
@phnt @hj last fetch was earlier today supposedly
(DIR) Post #B6fILJownUSCmLCo5I by phnt@fluffytail.org
1 likes, 0 repeats
@kirby @hj Yep, it's nulled out.
(DIR) Post #B6fJ17bQc7lF30obs8 by mint@ryona.agency
0 likes, 0 repeats
@hj @phnt @kirby :ebussy: "What makes you think smoothness is a metric?"I don't know, maybe my own fucking eyes. Here's the best case scenario, instance accessed over LAN, F5 pressed on /about page while logged out which should make the least amount of requests. My current FE (I think 48c739027c was the last time I merged upstream, it's been all cherrypicks onwards) loads three times faster as fluoride FE at its latest commit (cb638d57e8).Screenshot_20260525_221911.pngScreenshot_20260525_222606.png
(DIR) Post #B6fJ17nprzgZfUcWDA by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby now that is something i want to see. Actual metrics.Any more detailed stats? Also what browser?
(DIR) Post #B6fJmCgJY55WPSYEFM by mint@ryona.agency
0 likes, 0 repeats
@hj @phnt @kirby Something that isn't the latest Google Chrome (specifically Firefox ESR 140). Not gonna bother with the metrics.
(DIR) Post #B6fJmCxKWohPGEVolk by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby best I can tell just from your screenshots it loads more JS in one go, and only thing that comes to mind is that we migrated away from webpack to vite somewhere between 2.6.x and now.We also added bunch of stuff that we should probably separate better I guess.>"What makes you think smoothness is a metric?" I don't know, maybe my own fucking eyes.>Not gonna bother with the metrics.make up your fucking mind
(DIR) Post #B6fKhNjP8cw9BcGFjU by mint@ryona.agency
0 likes, 0 repeats
@hj @phnt @kirby Semantics. I've made up my mind ever since I tried to fix double scrollbars after three columns got merged and switched back to older version; thankfully JS blobs aren't nearly as prone to code rot as native software so there's zero downsides to staying on older patched version indefinely instead of dealing with bootleg pisskey with blur effects.
(DIR) Post #B6fKhOJYyBrOzlB85o by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby what double scrollbars?Can you cooperate so we could improve the FE for everyone's benefit, especially yours?
(DIR) Post #B6fL6eDKzbN1XwJGnw by mint@ryona.agency
0 likes, 0 repeats
@hj @phnt @kirby There's been a second scrollbar next to notification column that took the whole screen on either FF60/68 or Pale Moon.
(DIR) Post #B6fL6ePkFTIMAQ7B8y by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby I see. No longer thrilled about supporting meme moon, or firefox of that matter. Or anything that just randomly breaks compatibility (safari)
(DIR) Post #B6fMgPFiCHbrWT2FU0 by phnt@fluffytail.org
0 likes, 0 repeats
@mint @kirby @hj tag: palememe and other meme browsers
(DIR) Post #B6fMgPh0YnRat7o31s by mint@ryona.agency
0 likes, 0 repeats
@phnt @kirby @hj That was about 4 years ago. Nevertheless, "everyone's benefit" apparently doesn't include "meme browsers" so I have literally no reasons to cooperate.
(DIR) Post #B6fMgPznQwTNpOb3JY by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby nothing we can do to help people who keep shooting themselves in the foot and blame the others for it.It's not as much browsers being "meme" as much as it is about how debuggable stuff is on said browser and how compatible it is. Case in point: I can't even load modern pleroma-fe on palemoon because apparently some operation is insecure (inserting CSS stylesheets?) and I can't debug it because palemoon's debugger doesn't let me pause on exceptions and stack traces don't work with sourcemapped sources for some reason.We can work on optimizing page load and assets size/separation if that helps, but you're not gonna update anyway.Users aren't cooperating. Browser isn't cooperating, Everyone's angry.It's all so tiresome.
(DIR) Post #B6fMys5hiMwYB09vLk by i@declin.eu
0 likes, 0 repeats
@hj @phnt @kirby @mint the pros of akkoma not shipping a default frontend, everyone can run their own https://git.freesoftwareextremist.com/bloat instead of being tied to a default
(DIR) Post #B6fMysenbt13vqZx3I by hj@shigusegubu.club
0 likes, 0 repeats
@i @phnt @kirby @mint >prosyou can literally do the same in pleroma
(DIR) Post #B6fNIsIKfPpabFbWBk by phnt@fluffytail.org
0 likes, 0 repeats
@mint @kirby @hj Look, there's not many users using browsers that are long after eol, or forks of long eol browsers (meme browsers, also including browsers like Servo or Ladybird). At some point it stops being used and thus issues reported. And if it gets reported, it gets easily and quickly forgotten and buried in issues. That's the reality of how development works. It's the same with the backend, you aren't compiling Pleroma with Elixír from 4 years ago that is something like a year eol. The backend should be compilable, but some dependency requires 1.15, while possibly not even needing it. Oban is I think one of them and second is Plug. Yet you probably don't expect the backend to run on 5+ year old Elixir/OTP versions. The fact it probably works is only because little breaking changes were introduced. A workaround for early versions of OTP 22 was removed like a year ago during refactoring for 1.18 I think.
(DIR) Post #B6fNIsYzfT9tQvOp9s by mint@ryona.agency
0 likes, 0 repeats
@phnt @kirby @hj That's what I was talking about when mentioning code rot. Frontend is just a bunch of scripts smushed together running which is browser's responsibility.
(DIR) Post #B6fNIsiZ5soZubsT4q by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby and you're running an irresponsible browser tbh
(DIR) Post #B6fNTDExe90OSPxNQW by mint@ryona.agency
0 likes, 0 repeats
@hj @i @phnt @kirby Except you can't unless you maintain your own fork and deal with merge conflicts whenether the bundle gets updated.https://git.pleroma.social/pleroma/pleroma/src/branch/develop/priv/static
(DIR) Post #B6fNTDXOXbkbNaa69w by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby you just put your frontend build into /frontends/frontend-name/frontend-version and tell backend to serve that instead of builtins.
(DIR) Post #B6fNssYTB0xFpeJvDk by phnt@fluffytail.org
0 likes, 0 repeats
@mint @i @kirby @hj You can set a different primary frontend and in next release also your preferred frontend per browser (via a cookie). It's technically already in 2.10.2, but broken after merging a PR that fixed another issue. It wasn't tested since that PR that I think I merged :puniko_sorry: I have a fix for that already.
(DIR) Post #B6fNsswvi4WL3VlSLY by mint@ryona.agency
0 likes, 0 repeats
@phnt @i @kirby @hj I serve it with nginx anyway.
(DIR) Post #B6fNst8yzGA5etP58K by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby >your shit sucks>i have these problems>no i will not cooperate>actually all of my problems are already solved by my 41 patches and workaroundswoe unpatched vulnerability be upon ye
(DIR) Post #B6fOt6ObofQIiHNWTY by mint@ryona.agency
0 likes, 0 repeats
@hj @i @phnt @kirby I tolerated soybox users, I'm not here to tell what frontend someone should or shouldn't use since it doesn't affect me. At least it didn't until client-side webp compression (which you yourself don't use, mind you) was forced upon everyone rawdogging Pleroma without as much as an ample warning.
(DIR) Post #B6fOt6vDrPVkLQdZJI by mint@ryona.agency
1 likes, 0 repeats
@hj @i @kirby @phnt See, even local pedophile landlord agrees.RT: https://tsundere.love/objects/79701e01-85dd-44ce-b874-cb03579f8493
(DIR) Post #B6fOt7IGTjwVUtPyE4 by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby we can change the default and probably will. How do we "give an ample warning", exactly? Show another annoying notification that everyone hates?
(DIR) Post #B6fOxYsxpnhOELhf6m by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @kirby @phnt >(which you yourself don't use, mind you) I use it on phone but not on desktop.
(DIR) Post #B6fPHbmukkQd1XQska by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint if you don't wanna send annoying notifications don't set annoying defaults
(DIR) Post #B6fPHbyc3FmnbouDz6 by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint how do you know ahead of time if default is annoying or not
(DIR) Post #B6fPOz9kGjETWgd4Hg by mint@ryona.agency
0 likes, 0 repeats
@hj @i @phnt @kirby You do that already for some other shit so why not.https://git.pleroma.social/pleroma/pleroma-fe/src/branch/develop/src/components/update_notification
(DIR) Post #B6fPOzRTCpPWPevDua by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby yeah sure but it's meant to be used SPARINGLY. Like once a few years. And webp compression didn't seem to be that big of a deal to justify that.Settings synchronization however is a big deal and that popover will be back on unsuspecting users who didn't press "never show again"...and people who did will still complain that they didn't get warned.
(DIR) Post #B6fPYFaAZ9Qj4rPHA8 by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint ask or something
(DIR) Post #B6fPYFmDqL4TgF2twu by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint we did and you didn't pick up the phone
(DIR) Post #B6fQPQOT6I5dxKHzA8 by i@declin.eu
0 likes, 0 repeats
@hj @phnt @kirby @mint yeah, the problem with the pleroma-fe loading screen isn't that it's a meme feature, but that it has to exist at all, or at some point, it would take a few seconds each new tab and that it somehow made it to a release in that state before the complains finally got you to fix itsame thing with client side processing, lain could have made it a backend config via the existing pipeline if they felt it really needed to be a default, that way all clients would do webp instead of just pleroma-fe
(DIR) Post #B6fQPQbwICrid6ak9w by hj@shigusegubu.club
0 likes, 0 repeats
@i @phnt @kirby @mint >but that it has to exist at allI know, I know. Look, it's an SPA, it's gonna have SOME loading time either way. It was meant to show SOMETHING during that time, i.e. show what's going on if it's stuck loading some resource or there's some problem. I thought people would rather have SOMETHING but turns out that people would rather see white screen (unless it really gets stuck or errors out)>same thing with client side processing, lain could have made it a backend config via the existing pipeline if they felt it really needed to be a default, that way all clients would do webp instead of just pleroma-fei do believe it's already a backend config, but users have no say in it, if admin enables compression - you don't have a way out except for cyanide or other instance. when done on FE user gets to choose. Simple as. Simple to implement.
(DIR) Post #B6fQVsoAMwJporO9ke by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint true, the trust has eroded to the point where every other admin runs 2 years old fe or a fork so it's probably pretty difficult to do now
(DIR) Post #B6fQVsy5m2G6Je25Ds by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint >every other adminlike who? spc? poast? akkoma admins? people who don't update out of principle?
(DIR) Post #B6fQbXklYz9oFxUtgO by mint@ryona.agency
0 likes, 0 repeats
@i @phnt @kirby @hj Speaking of settings synchronization, would it save all the settings including defaults in user's DB column? Would that make user's settings that were previously set to old default overwrite instance's settings including that for attachment molestation?
(DIR) Post #B6fQbY0ibfux3QxdY0 by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby why would you care? It's not like you're gonna use it.
(DIR) Post #B6fR0EYI5ds5wcR3IG by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint it's half the instances tagged in your post at least
(DIR) Post #B6fR0EuGlvS72mibYG by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint so like what, 2% of the instances I interact with?
(DIR) Post #B6fRrYzunwKshemnL6 by mint@ryona.agency
0 likes, 0 repeats
@hj @i @phnt @kirby I am being forced to use it by the nature of this realm being a federated network. The question is whether it could even be changed server-side without having to fix it for each and every user individually.
(DIR) Post #B6fRrZDNzr6xNR5YKu by hj@shigusegubu.club
0 likes, 0 repeats
@mint @i @phnt @kirby pleroma-fe uses user profile storage for settings synchronization, no special API. It's literally just a "profile update" endpoint.It's been using it for customizable post actions and navigation pins before. Inside it uses a homebrew implementation of https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type , meaning it won't overwrite entire thing on a change, all changes are tracked separately and merged on sync.Settings are migrated from unsynced to synced storage once per session if it has anything.Only settings that user touched are saved, same as it ever was.If there are problems you know what to do (don't tell us about it, make 6 workarounds and complain online how bad devs are)
(DIR) Post #B6fSNibOd9WTl2eMxU by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint it's a bigger part for me. if you want real metrics maybe fedilist has it
(DIR) Post #B6fSNipvl79IU7Ryc4 by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint not really interested in the size of your non-cooperative complainers circle.
(DIR) Post #B6fSVs7n6sUvbkgs40 by menherahair@eientei.org
0 likes, 0 repeats
@hj @i @phnt @kirby @mint get some sleep man
(DIR) Post #B6fSVsLyG9qAJjKCAK by hj@shigusegubu.club
0 likes, 0 repeats
@menherahair @i @phnt @kirby @mint i wish i could
(DIR) Post #B6wPG1Bke820uVbtxI by hj@shigusegubu.club
0 likes, 0 repeats
@mint @phnt @kirby just poppin' in to say that I'm working on optimizing build size and load speed https://git.pleroma.social/pleroma/pleroma-fe/pulls/3500pleroma-fe should load faster at a cost of parts of it loading on-demand