Free Flarum hosting on an expert platform by FreeFlarum.com

Sanguine

maniraj1234 I don't think Google should crawl your API endpoint, as you don't want Google to direct visitors there. How did this /api/pages/1 URL end up there in the first place? Did you submit it manually? Otherwise, you should file a bug report with Flarum (see the SEO tag already on Github).

maniraj1234

Sanguine Did you submit it manually?

No, I have just submitted the sitemap and also used the tool "Fetch as Google" then it displayed this.

Sanguine

@Razor @Ralkage thanks for standing up for FreeFlarum! However, I do appreciate it if people (like @QTM) voice their sincere criticism. I do not see that as complaining actually. I welcome all perspectives and it can only make (Free)Flarum better. So thanks all for participating here! In the end we all have the same goal: make Flarum successful and run great forums.

QTM

Razor, this is not complaining, and it is not "meaningless" in any way; it is asking for a feature, and searching for an explanation as to why it is not implemented. I pretty much already knew the answer (ie. disk space, resources) but I wanted to confirm this. I too often don't "understand people" and ask myself why they would even bother posting in the first place, especially when their comment has no value.

Sanguine I do appreciate it if people (like @QTM) voice their sincere criticism. I do not see that as complaining actually.

Thank you.

I am extremely grateful for what @Sanguine has done and is offering with FreeFlarum, and am making the switch to this fantastic service as we speak.

The solution to my "dilemma" is not ideal, but it is workable; it just takes a bit more time and effort. This is how I go about it using Discourse, which is simple and fast (8 steps):

Alt-PrtSc (capture screen)
open Paint (it's always open)
Ctrl-V (paste screenshot image)
Crop, edit, markup, etc.
Ctrl-A (select all)
Ctrl-C (copy image to clipboard)
open post editor
Ctrl-V (paste image, it automatically uploads)

Externally hosted method (11 steps):

Alt-PrtSc (capture screen)
open Paint (it's always open)
Ctrl-V (paste screenshot image)
Crop, edit, markup, etc.
Ctrl-S (save to file)
open Imgur
find the file
drag to Imgur
copy Imgur link
open post editor
Ctrl-V (paste link)

So 11 steps vs. 8 steps, and I now have a file on my drive taking up space that I don't need. Maybe I can Ctrl-V directly into Imgur without saving the file - will try that shortly.

One more time, thank you very much @Sanguine for everything that you are doing.

Sanguine

QTM Wow, that's a lot of work! I run Linux and have a tiny script bound to PrtScn that a) takes screenshot b) uploads to my server c) copies URL to clipboard.

But I guess for Windows / Mac similar utilities exist. Perhaps this one? https://app.prntscr.com/en/index.html

QTM

QTM Maybe I can Ctrl-V directly into Imgur without saving the file - will try that shortly.

Yup, that works! Great, it doesn't reduce the steps, but at least I don't need to have a file on my drive!

Sanguine for Windows / Mac similar utilities exist. Perhaps this one?

Cool little App, thanks! Just tried it, and it works fairly well, but the link that it provides does not result in an embedded image in the post. Probably has to do with the source ...

http://prntscr.com/iql6pf

Sanguine

QTM Hmm right. They profit from ads, and have embedded the image in base64 so people cannot link directly. Oh well, they gotta pay the bills too ?

I see however that Imgur does allow direct linking, and there are several tools available. For example MyImgUr, which says:

Intuitive 1-click actions and simple settings to very quickly capture areas of your screen or specific windows and send them to Imgur for sharing

BTW, if you find the best Flarum-screenshot-embed method for Windows, perhaps you would like to share it here? I guess many other people would like to know about it ?

Sanguine

maniraj1234 also used the tool "Fetch as Google" then it displayed this

But why did you enter the /api/pages/1 URL there? It should not be a URL that Google fetches.

QTM

Sanguine Imgur does allow direct linking, and there are several tools available

I see ShareX on that list, which I already use for capturing screen video - will take a look to see if it fits my needs for static images. Thanks again!

Sanguine BTW, if you find the best Flarum-screenshot-embed method for Windows, perhaps you would like to share it here?

Will do for sure!

maniraj1234

Sanguine I didn't even know such URL exists, I just tried it with some page link. "/p/1-all-topics" and it said this.

Sanguine

maniraj1234 But /p/1-all-topics is not what is showed in the input box of your screenshot. So you must have pasted it yourself?
Update Sorry, I misread. You are right, I have updated the robots.txt. Could you try again? Thanks for reporting!

QTM

QTM I see ShareX on that list, which I already use for capturing screen video - will take a look to see if it fits my needs for static images.

Works great, and gives direct link to the PNG file which is better (IMO) than the short-link provided by Imgur which inserts an iframe and Javascript into the post which produces a frame with a header and footer.

I can post a general How To (in a new topic) on using it for embedding images in posts from external sources.

QTM

@Sanguine could you please add the following Extension (I love FontAwesome) ...

https://discuss.flarum.org/d/4981-fontawesome-bbcode-extension

Sanguine

QTM Looks cool! But last updated for beta6. I'd rather wait until beta8 is released and then see which extensions are being upgraded for the new interface.

Ref: https://github.com/AntoineFr/flarum-ext-bbcode-fa/blob/master/composer.json

Antoine

@QTM Sanguine My FontAwesome extension is ready to update to beta 8, the code is available on another branch : https://github.com/AntoineFr/flarum-ext-bbcode-fa/commits/next-back

QTM

Okie dokie, will wait for that (BBcode FA). BTW, I have it installed in beta 7.1 and it works fine.

Sanguine

QTM it works fine.

No doubt, but beta8 will break all existing extensions, so unmaintained exts will hold back a global upgrade on FreeFlarum.

Sanguine

FreeFlarum forums now have CSP and HSTS headers and score all ✅ on @clarkwinkelmann excellent Flarum Health Test:

Example:

During the upgrade, for a few minutes a bogus CSP header was live that would block JS execution. Sorry about that, everything should work fine now.

clarkwinkelmann

Sanguine nice job.

Minor note though if you plan to preload you need a maxAge of at least 6 months and includeSubdomains as described here https://hstspreload.org/. No need to include preload if you don't meet / plan to meet the requirements ?

Fla

Sanguine

did you remove / api / from robots? There will be a lot of garbage in the search.

example.com/api/discussions?include=startUser%2ClastUser%2CstartPost%2Ctags&filter%5Bq%5D=%20tag%3Avood&

that's how Google sees the page

Sanguine

clarkwinkelmann No need to include preload

Thanks! Fixed that.

Fla did you remove / api / from robots? There will be a lot of garbage in the search

According to his screenshot, Google parsed the API URL as an AJAX asset, so I was wrong that I assumed Google would see it as an independent URL.

Also, a quick check for discuss.flarum.org shows that Google has no indexed /api/* pages, even though this site does not have a robots.txt. So I concluded that the /api/ restriction is not necessary and perhaps even bad (if Google executes the Flarum JS).

Update: after removing /api/*from robots.txt today, I observed that Google indeed occasionally indexes these urls:

{
    "city": "Mountain View",
    "country": "US",
    "protocol": "HTTP/1.1",
    "remote_addr": "66.249.65.222",
    "request_time": "0.026",
    "status": "200",
    "uri": "/api/discussions?include=startUser%2ClastUser%2CstartPost%2Ctags&filter%5Bq%5D=%20tag%3Afitness&",
    "user_agent": "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
}

« Previous Page Next Page »