From Edward Loveall to ~edwardloveall/scribe
Hey, thanks for the link. I'm not really interested in integrating something like this right now. It's not that I disagree with it or anything, but I don't want to take on that complexity or learn a new tool. If someone else out there wants to take a shot at it and thinks they can do it in a nice way, you included, please feel free! Edward On 12 Jul 2023, at 8:18, Bastien wrote: > Hi, same problem here. Do you think it's possible to integrate a solution like this : https://github.com/FlareSolverr/FlareSolverr to bypass cloudflare verification ? > > Thanks.
From Edward Loveall to ~edwardloveall/scribe
Looking at the page, it looks like a cloudflare page. Like one of those "We're checking to see if you can access this page" pages. It looks that way because javascript embedded in the HTML response has "/cdn-cgi/challenge-platform" and if I search that I get links to [this cloudflare /cdn-cgi endpoint documentation](https://developers.cloudflare.com/fundamentals/get-started/reference/cdn-cgi-endpoint/). I'm not sure exactly but it may be that cloudflare is blocking your server. If that's the case, I'm not sure what else I can do for you, unfortunately. Also, you mention that your curl request "properly returns HTML". For clarity, I wanted to say that is should _not_ return HTML. It should return the JSON response of the graphql call. It's returning what we thought it might be in previous emails, but it's not correct. Sorry to jump on that if you knew that, but I wanted to make sure we were on the same page. Edward On 11 Jul 2023, at 17:13, Lenny wrote: > Sorry for the late reply, here is the result of running that command. It properly returns HTML. > > ``` > /home/lucky/app # curl -X "POST" "https://medium.com/_/graphql" \
From Edward Loveall to ~edwardloveall/scribe
Hmmmm... That error looks like it's trying to parse an HTML response (that starts with `<`) as JSON. It's working over here on my end so I it's not on Medium's side. Maybe it's blocking your network access? Can you try to make a similar request from inside the docker container? Here's the curl equivalent: ``` curl -X "POST" "https://medium.com/_/graphql" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json; charset=utf-8' \ -d $'{ "query": "query{post(id:\\"b62607a43a8c\\"){title createdAt creator{id name}content{bodyModel{paragraphs{name text type href layout markups{title type href userId start end anchorType}iframe{mediaResource{href iframeSrc iframeWidth iframeHeight}}metadata{id originalWidth originalHeight}}}}}}", "variables": {} }' ```
From Edward Loveall to ~edwardloveall/scribe
Alright, I updated it and pushed to a branch: el-docker-crystal-update It built/ran for me locally, but can you give it a try to make sure it's not just me? Edward On 29 May 2023, at 15:29, Lenny wrote: > Hey, > > yea I'm basically building a docker image from the repo and then running that using an ansible role like this: > > > ---
From Edward Loveall to ~edwardloveall/scribe
Interesting. The main scribe instance (scribe.rip) doesn't see this bug, so I assume you're probably deploying differently than I am. Can you tell me a little more about your environment? If you're using docker I found a thread that looks pretty similar and may be helpful to you: https://forum.crystal-lang.org/t/help-with-static-build/4936 Edward On 28 May 2023, at 11:10, Lenny wrote: > Hey, > > recently this error started showing up on my instance. Version: 2023-05-21 > > > This is what I see in the logs:
From Edward Loveall to ~edwardloveall/scribe
Hi Limanic. I just pushed a new version that should fix your error. Edward On 9 May 2023, at 19:36, Edward Loveall wrote: > Thanks Lomanic. > > Carbon is a shard for sending emails. Since Scribe doesn't send emails, > would you be up for removing carbon entirely? You'll have to remove it > from a couple other places like src/shards.cr, spec/spec_helper.cr, and > spec/setup/reset_emails.cr. > > If it ends up being more difficult we can use your original change. It
From Edward Loveall to ~edwardloveall/scribe
Small change today in version 2023-05-21. * Fix - Remove unused carbon shard which should fix build failures Edward
From Edward Loveall to ~edwardloveall/scribe
Thanks! Applied. Edward On 19 May 2023, at 9:48, ~extremelyonline wrote: > From: extremelyonline <opnxng@tuta.io> > > --- > docs/instances.json | 1 + > docs/instances.md | 1 + > 2 files changed, 2 insertions(+) > > diff --git a/docs/instances.json b/docs/instances.json
From Edward Loveall to ~edwardloveall/scribe
Thanks Lomanic. Carbon is a shard for sending emails. Since Scribe doesn't send emails, would you be up for removing carbon entirely? You'll have to remove it from a couple other places like src/shards.cr, spec/spec_helper.cr, and spec/setup/reset_emails.cr. If it ends up being more difficult we can use your original change. It would be nice to remove it though since I don't ever plan to send emails via Scribe. Edward On 9 May 2023, at 18:29, ~lomanic wrote:
From Edward Loveall to ~edwardloveall/scribe
Sorry, wrong subject line in that last announcement. Fixed in the "Re:" Edward On 6 May 2023, at 13:09, Edward Loveall wrote: > Hello subscribers to the scribe list! I've released a new version 2023-05-06. > > * Upgrade - Scribe is now running Lucky framework version 1.0.0 and crystal version 1.8.1 > * New - If embedded media has a caption, it will now be displayed > > > Edward