Taking a screenshot - sometimes never finishes
complete
S
Sven
For many of my attempts to store a bookmark I get the message "taking a screenshot ..."
Yesterday I stored an URL for: https://www.dreikon.de/aktuell/social-media/linkedin-bildgroessen/#linkedin-bildgroessen-4564
and today it sill shows "Taking a screenshot ..."
Seems rather “random” whether it works. Sometimes the screenshot is created quickly, sometimes it seems to take a little longer - but sometimes it seems to try “forever” without it working!
Igor Lanko
complete
Obvious issues and inconsistencies seem to be addressed now, including the Notion full page screenshot issue.
Some EU sites may still fail, but this will be addressed separately and is not really a bug, just a lack of functionality to support various connections.
Thank you all for the input! Please feel free to create new related topics if any new issues arise.
Igor Lanko
Hey everyone!
I just pushed another batch of fixes that are meant to address some of the newer issues with the link artifact screenshots.
- You may have noticed that some screenshots failed by showing the title of the page, but the image itself was broken. This was addressed and shouldn't happen again. However existing failed link artifact screenshots won't fix themselves unfortunately, so please try deleting them and adding them again (sorry, just wanted to push the fix out asap. If you have issues with many artifacts, please reach out I'll help).
- Some sites, articles specifically, were failing. This should work much better now generally.
- Some sites do not use distributed networks (like Cloudflare or Vercel) and host directly on local servers. Collecta being from the Eastern US sometimes is unable to reach them or just takes too long to do that. Which in turn fails the screenshot. This is fixable by introducing a proxy server in between, which I'm working on. This is an additional spend however, so going to be honest here, I'll need to see how often does this happen to be able to justify the cost.
- Lastly, some sites do have enhanced bot protection that prevent Collecta services from reaching them. I'll need to research this subject a bit more. However screenshots do not seem to fail often because of this reason in particular, so I'll keep researching this, and will address separately.
Thanks again for all your feedback and prolonged patience with me :) Keeping this open for another few days just in case.
Hope you have a wonderful day.
S
Sven
Igor Lanko
Hello Igor,
First of all, thank you for your efforts to make the screenshot feature even more stable. I appreciate the effort and think it's one of the standout features of Collecta. Few other tools that I know of implement this so well.
In addition to the potentially cost-intensive variant for European sites, I would like to add an additional idea that might cover more cases in a simpler way.
This is an idea which I am familiar with from another tool, namely "Boardflow", and which I use extremely often there. It's the option of screenshotting a specific area via the extension. See this screen cast as an inspiration how this works in Boardflow: https://video.hofians.com/conversations/abd97909-22a8-502b-8546-3212391655ec
The advantages are manifold:
First, by making it a local screenshot through the extension, it eliminates all the problems you have when you do a screenshot on the server side.
Secondly, it also makes it possible to take screenshots of pages that are behind a login or a paywall.
Thirdly, and this is my practical experience, in at least 70 percent of cases it is almost more meaningful if I select a certain area of the website as the relevant one than to take a complete screenshot. (As one example see my screencast above of taking a screenshot of a youtube video without all the comments and video suggestions all around the page.)
The bottom line is that I estimate that in about 70 percent of all cases I would rather only take a partial screenshot, which I select because that is more meaningful and in about 30 percent of cases I want to preserve the complete content and therefore the current screenshot feature of the entire page would be important.
Mabe you like the idea as an additional method.
Kind regards,
Sven.
Igor Lanko
Hey Sven, sorry just saw this!
You described the use cases & needs for the partial screenshot perfectly, which is why I'm building the native macOS client https://collecta.space/feedback/p/macos-app-to-take-screenshots-anywhere.
Technically this could also be a part of the extension too, but I personally just prefer the native experience to often janky JavaScript-based screenshoters. Of course this limits the use for this feature to macOS users however, but this is a start.
But honestly I'd much rather dig into something like Rust / Electron and still build an app for Windows, than baking too much into the browser extension. Not sure yet!
S
Sven
Igor Lanko
Thank you for your efforts. The screenshot creation does indeed seem to work much more reliably now 👍
Here are a few more thoughts:
The advantage I see in a solution via the extension is:
➀ it is immediately available to all users
➁ it does not need to be installed (this is not always allowed on company notebooks)
With a Windows/Mac application I also see advantages like an increased usability (e.g. more possibilities for shortcuts, screenshots outside the browser; perhaps even offline support later on etc.).
But yes, from the user's point of view, I don't really care how it's solved anyway.
Now I would like to motivate you to provide a solution for Windows users immediately after the iOS solution. I work on Windows and Android myself - so will have to be patient 😉
➕
I can confirm from my current tests that we need an alternative way to generate screenshots locally. There are simply too many cases where there is no access to the current page on the server side.
(Most recently, for example, when putting together an Ikea wardrobe and trying to save the result → of course Collecta cannot access this information on the server side)
❓ Is there already an entry for the request to “Create local partial screenshot”, or should I create one?
Igor Lanko
Hey everyone,
I just shipped a few significant updates to the link artifacts screenshot mechanism, including the ability to try doing it again if it fails, as per Sven's suggestion.
I'm going to keep this report open for a few days to ensure we do see some improvements and hopefully less fails. If all is well, I'm going to share an improvement update to the Community / What's new popover, and talk exactly about what changed.
I'd appreciate it if you could test adding links directly or via extension, and see if you can spot any issues happening again. Please use this existing thread if you find anything.
Hope everyone is having a great day!
Cheers,
Igor
P. S.
If you're reading this from your inbox, the button at the bottom 👇 shouldn't take you to a 404 page anymore, but directly to this post :-)
S
Sven
Igor Lanko
The first tests were successful. The screenshots have worked so far.
In one case, however, the text of an article was NOT completely transferred. Is this perhaps an OG card you were talking about?
S
Sven
Igor Lanko
I now found a link that is NOT working - also "try again" gives no result - maybe because it contails the tracking-id-thing ...
The resulting URL you get redirected to works fine
Igor Lanko
Thanks for the catch, I just fixed this! Both of these URLs should work fine!
S
Sven
Igor Lanko
I get the error message "Something went wrong" when trying the URL!?
Igor Lanko
Sven, I'm sorry I'm not sure I understand. What's happening before you see this error?
Update: I think I know what you mean now. There was a server error that should be resolved now. Sorry for any trouble!
S
Sven
Igor Lanko
Sorry for beeing imprecise.
Just tried it again. If I add the bookmark ( https://bakadesuyo.us5.list-manage.com/track/click?u=b083212130155b748c7785081&id=d4e78a59ed&e=c66c7616d1 ) manually via Collecta site after hitting the Collect button I get the error "Something went wrong".
S
Sven
Igor Lanko
Just had two cases where I added linkedin URLs via extension to collecta.
Both show a broken image icon and no retry button
Igor Lanko
Hey Sven, could you drop me a message in chat (https://collecta.space/account/#anchor-support), I'll be able to help you. I might need to ask you a few details though. This looks like this specifically is unrelated to the screenshots though, but it might be something else.
Igor Lanko
Merged in a post:
Full page screenhot will not finish
D
Dennis
I tried a couple of times to make a full screenshot of a website. Unfortunately, the process of taking a screenshot did not finish, and the screenshot is not available
Igor Lanko
Since some screenshots can sometimes fail for various unpredictable reasons, an idea for a fallback I had is to show the OG card of the page or just an excerpt of the contents instead of the the “Taking screenshot” notice which obviously is useless when it's already failed.
S
Sven
Yes, I would also display an “alternative” information if the screenshot is not possible. I don't know what the “OG Card” is. Maybe you could also show the favicon of the page. An excerpt from the content is also an interesting idea.
What I would definitely like to see is: “An option (button ?) to manually trigger the creation of the screenshot again.
For some bookmarks the screenshot will not be so important. But for some pages I might really want to preserve the complete content - then it would be good to be able to start a new attempt.
Igor Lanko
Sven, sorry! OG (short for Open Graph) is a common standard of previewing the links. You know how you share a link on Twitter, or send it to someone in a preview image pops up? That's what I mean!
Yes definitely, retriggering a screenshot is also a good fix for this!
Igor Lanko
in progress
Thanks for the report, Sven. The page screenshot functionality is quite shaky at the moment, I admit.
I'm actively working on this right now, will share updates soon.