on alternative instances, the about page gives wrong / easily misinterpretable information re: adding a search engine on chrome #43
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
the /about page of e.g. neco.lol, page generation will use $SERVER_NAME for the name & shortcut fields, but 4get.ca for the critical search query one.
now a barely technically literate person would probably spot this, but anyone else, or just someone in a rush to copy+paste the information given to them into the indicated fields will create a search engine entry with the name of the instance they want, but that actually uses 4get.ca.
once again they'll probably catch this the first time they search something and notice it's the wrong instance, but blah blah blah probably a problem.
the config doesn't have a field for "server FQDN" sooooooooooo if you do fix this it'll probably be either by adding that or by grabbing the HTTP_HOST the client is hitting up to see the page in the first place.
also gitea allows arbitrary image uploads for issues???? and the upload happens before the issue is made?????? and you can just never make the issue and it might still be there????????? (testing this now)
brb switching my image upload scripts to use git.lolcat.ca as free storage
lol yea this sure looks like a live image to me. wonder how long these stick around. https://git.lolcat.ca/ attachments/ 68bc8282-131e-4aa2-a1ce-c28aab82f187
(spaces added so b1g gitea still doesn't think it's been referenced).
for the record i got that link by
so im like 90% sure that image is orphaned, comment-wise
Use case for image hosting?