⌈⌋ branch:  freshcode

View Ticket

Ticket Hash: c4a1a4a8b55e0180ef9314ee95a425328a2e894f
Title: larger images
Status: Open Type: Feature_Request
Severity: Cosmetic Priority: Medium
Subsystem: Resolution: Open
Last Modified: 2020-10-18 10:49:18
Version Found In:
User Comments:
benibela added on 2020-09-30 13:06:14:
The images are scaled to  120x90 px large. 
That is okay on the website, but it looks extremely bad on Twitter that scales the image up to 507x376.45 px  again

mario added on 2020-10-05 22:32:08:

True. The twitter-upscaled images look disgusting at best.

  • Can't fix it right now. The server setup is borked currently (even wkhtmltoimage broken)
  • And this would require storing larger images for twitter. (not a priority really)
  • Some projects don't really have large logos or screenshots. So half might end up looking poorly in any case. (@ToDo: check, how many. When fixed, it shouldn't disproportionally disadvantage some projects.)
  • And of course, larger images are somewhat redundant for GitHub projects (no offense, but: all the offense)

Anyway, this might take a bit. (back and forth migration, new server)

mario added on 2020-10-06 23:55:43:

So, wkhtmltoimage is functional again. Found a workaround, with firejail still intact. (Wouldn't want to reign it without.)

Haven't looked into larger screenshots yet. But I'm hoping to get firefox --screenshot working once migrated.

mario added on 2020-10-18 10:49:18:

firefox --screenshot seems to work on the new server. So, larger images are certainly feasible. // Holding out till everything is migrated back however.