Time  Nick       Message
10:43 Zughy[m]   One more reason to migrate: https://github.blog/changelog/2023-06-07-code-search-now-requires-login/
10:43 Zughy[m]   I was looking for a MT function to see what it does but nope, I can't if I don't log in
10:44 ROllerozxa hasn't this always been the case, code search requiring login?
11:36 celeron55  Zughy[m]: that's just stupid from github. it's as if they don't know they have competitors
11:38 Zughy[m]   I had to locally clone the repo to find the function (I didn't want to log in, as a matter of principle)
11:43 celeron55  (having said that, i'm not 100% sure if it makes business sense for github to host volunteer driven public projects. they might be focusing on paying private business customers in the future)
11:48 celeron55  (the problem of course is that no amount of marketing can beat the favourable position achieved by hosting volunteer driven public projects. maybe they will learn it before irrelevance, maybe not)
16:07 jonadab    Can't you just clone the repo and use grep -r ?
16:08 jonadab    I don't frankly care whether there's an online web-based search feature that requires login, as long as more traditional methods still work.
16:11 jonadab    Although, if a lot of people are cloning the repo just to do one quick code search and then nuking their local copies afterward, the bandwidth from that would add up for the host in the long run.  IN practice, I doubt it's a frequent enough occurrance to matter, though.
16:12 jonadab    Because *most* of the time, I think most of us only do code searches on repos that we've already cloned anyway.
16:12 celeron55  the effect on users here is minor, but you have to imagine what happens when you continue on that route
16:12 sfan5      (the selling point of web search is convenience)
16:13 jonadab    Since when is loading up a web page more convenient than a quick grep?
16:13 jonadab    Maybe for Windows users, I guess.
16:13 celeron55  if you're already on the web page, it's definitely more convenient
16:14 sfan5      I sometimes browse MT's github on machines where I don't have a git checkout of it ready
16:16 jonadab    Ah, hmm.
16:16 jonadab    Maybe I'm just weird, for always being sshed into my dev box regardless of where on the network I am.
16:17 sfan5      PS: ripgrep is a good alternative to grep
16:18 celeron55  i definitely don't have a dev box, other than my laptop. all of my servers are for production use
16:21 jonadab    I actually usually use the grep that's built into eshell, because it gives me a handy results buffer that will immediately open the file in question to the line in question if I hit enter.
16:36 celeron55  sounds useful. that's what github's search also does 8)
16:36 nrz        sfan5, is my MR fine, am i going in a good direction ? if yes we can merge and i'll continue the cleanup in the next days 🙂
16:42 MTDiscord  <warr1024> Searching a code tree is not a really important reason to choose a particular hosting platform, since that is one of the things most easily fixed by just automatically mirroring onto other platforms.  The key thing is that the central authoritative mirror support all the features you actually need (e.g. issue trackers, wikis, CI, etc) but be as free from vendor lock-in as possible, so that it's easiest to migrate to another one.
16:44 MTDiscord  <warr1024> I don't think any git hosting platform that's going to be large enough to host a project like MT will remain completely immune to enshittification; it's just mostly a matter of finding the right balance between enshittification-resistance and features, since a platform developer generally needs to allocate a finite pool of energy to one or the other.
20:41 Noisytoot  Using git grep is better than grep -r if you want to only search files tracked in git.