on alternative instances, the about page gives wrong / easily misinterpretable information re: adding a search engine on chrome #43

Open
opened 2024-10-12 01:02:31 +00:00 by cynic · 3 comments

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.

image

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.

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. ![image](/attachments/8d7a9761-7ac9-425d-a318-71866f63cc73) 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.
Author

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

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
Author

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

  • pasting an image into the comment window
  • deleting the comment and reloading the page
  • deleting the reference/embed to the image in the comment

so im like 90% sure that image is orphaned, comment-wise

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 * pasting an image into the comment window * deleting the comment and reloading the page * deleting the reference/embed to the image in the comment so im like 90% sure that image is orphaned, comment-wise
Owner

Use case for image hosting?

1683667794726.jpg

Use case for image hosting? ![1683667794726.jpg](/attachments/9174726a-758e-4129-a0e0-bdb6738cbf26)
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lolcat/4get#43
No description provided.