Post AQe0lAbHkLxZSSkrs8 by doable@floss.social
(DIR) More posts by doable@floss.social
(DIR) Post #AQXFGme6Np2xgOK0NE by akib@hostux.social
2022-12-12T06:18:15Z
2 likes, 2 repeats
Dear @Codeberg users,Please add all related topic to your repository's topic list. This makes it easy for all to discover repositories.#GitHub uses its unethical nasty invasive AI to recommend you repositories. @Codeberg is ethical, so it doesn't use your personal information. So please add topics to increase your discoverability.And if you use unethical #GitHub and don't use @Codeberg, #GiveUpGitHub today!https://giveupgithub.org/https://codeberg.org/
(DIR) Post #AQXq9AKI9W8R77HoA4 by Anselm@troet.cafe
2022-12-12T17:52:19Z
0 likes, 0 repeats
@akib @Codeberg This sounds like an excellent advice, except... just popping up the list of completions takes ~10 CPU seconds on a webkit 4.0-based browser running on a Haswell i5. Before I start to diving in: Is this a known problem? Is there, perhaps, even a known solution (other than switching to firefox or chromium)?
(DIR) Post #AQXq9AvrtoC0zerojQ by akib@hostux.social
2022-12-12T18:34:52Z
0 likes, 0 repeats
@Anselm @Codeberg For me too. I think it is to fetch the topic list, parse it and list it.
(DIR) Post #AQXq9BRlzBiIabnISe by Codeberg@social.anoxinon.de
2022-12-12T22:45:23Z
0 likes, 0 repeats
@akib @Anselm You're talking about performance problems while editing the repo topics?
(DIR) Post #AQXsZrOwp4J498Jx3I by Anselm@troet.cafe
2022-12-12T23:12:23Z
0 likes, 0 repeats
@Codeberg @akib I do, yes. I go to a repo, hit "Manage Topics", click the input field, and I get >10 seconds of 100% CPU (with no network activity) until a popup containing (at this point) python, linux, rust, javascript appears. When I click an entry, there are again >10 seconds before the "python" tag appears (this is on luakit).
(DIR) Post #AQZ03oxNN0pg5ZcM1A by Codeberg@social.anoxinon.de
2022-12-13T12:11:08Z
0 likes, 0 repeats
@Anselm Yes, I know this behaviour. It's the same on my old hardware. Sadly, I'm not a frontend developer, and my attempts to discuss / fix it haven't worked out so far.~f@akib
(DIR) Post #AQZiHlK04txGqterCK by Anselm@troet.cafe
2022-12-13T20:26:31Z
0 likes, 0 repeats
@Codeberg @akib Hm... I'm not too fond of the various biotopes of the javascript ecosystem myself. In particular, I'm not sure whether I should be concerned that webkit doesn't retrieve the unminified version of index.js. Still: From briefly poking around in the minified version I'm rather sure what takes the time is putting all available tags into the popup. Making that interruptible should really fix the problem.
(DIR) Post #AQZr0oVXsU2fOm3EuG by Anselm@troet.cafe
2022-12-13T20:31:30Z
0 likes, 0 repeats
@Codeberg @akib Trying to find the sources of that index.js, I end up confused: gitea is hosted on github? Shouldn't gitea of all packages self-host? Ah well.
(DIR) Post #AQZr0p6le5ofGDSxvM by Codeberg@social.anoxinon.de
2022-12-13T22:04:30Z
0 likes, 0 repeats
@Anselm We'll likely switch to the soft-fork https://forgejo.org/ with the next release, and it's obviously hosted here.@akib
(DIR) Post #AQZr0q4g3LjqG1UoIy by Anselm@troet.cafe
2022-12-13T20:50:41Z
0 likes, 0 repeats
@Codeberg @akib So, I'm rather confident that the time is spent calling topicDropdown.dropdown in web_src/js/features/repo-home.js, which somewhere in a jquery plugin creates 1e3s of elements. But experimenting with that looks like a lot of scaffolding work, and frankly I had hoped this wouldn't turn into a gitea or, even worse, jquery problem. Ah well. Perhaps we should simply raise a gitea issue (on, argh, github)?
(DIR) Post #AQZrCsb4V4uXYWODMu by Codeberg@social.anoxinon.de
2022-12-13T22:07:07Z
0 likes, 0 repeats
@Anselm You can also try and report it to Forgejo https://codeberg.org/forgejo/forgejo/issues/We'll forward in worst case :)@akib
(DIR) Post #AQe0Y2oFOyfDWwYj44 by doable@floss.social
2022-12-15T21:24:46Z
0 likes, 0 repeats
@akib @Codeberg where exactly do i do this? in the repo settings? couldn't find it there on first look ^^'
(DIR) Post #AQe0Y3K9UMBV7tUCnI by Codeberg@social.anoxinon.de
2022-12-15T22:10:10Z
0 likes, 0 repeats
@doable If you visit your repo (not the settings), there is a "manage topics" button below the description.A little confusing, I admit.@akib
(DIR) Post #AQe0lAbHkLxZSSkrs8 by doable@floss.social
2022-12-15T22:11:00Z
0 likes, 0 repeats
@Codeberg @akib ahhh, okay I'll check it out later, thank you for the help!!
(DIR) Post #AQheH8oUPCdWrw2xqC by Anselm@troet.cafe
2022-12-17T16:18:19Z
0 likes, 0 repeats
@Codeberg @akib So, I've created https://codeberg.org/forgejo/forgejo/issues/132 – let's see what happens. I have to say I'd like limiting topic matches to 100 (say) even beyond that problem. Nobody wants to scroll 10'000 topics in frequency order...