281–290 of 377 posts
> The web is meant for free speech. Your content shouldn’t be jailed for being controversial.
You mentioned your profile was taken offline after being mistakenly caught in their spam filter. Shouldn't spam blocking be a basic function of a publishing site? Obviously in a perfect world there wouldn't be false positives, but sometimes these things happen. Your content wasn't banned for being "controversial".
Earlier quoted context omitted.
> I shouldn't have to pay money to get around a pay wall for a project's technical documentation. But that's on the project, not Medium; and if they want to be paid for the work that goes into their documentation, what's the problem? I mean, seriously, Medium is $5/month, for loads of advertising-free content. Why not just subscribe?
Has the project team any say in this, or is it just Medium doing their thing?
Earlier quoted context omitted.
Netlify simply adds an abstraction layer over a task which I don't want to be performed __AT_ALL__. I don't care if I'm doing it myself or someone else is on a server somewhere on my behalf. It is utterly stupid to have all that to serve a static file.
So write HTML and push that directly to your webserver.. what do you want from the world haha Forgive me for suggesting the first thing that popped into mind, could you run the generator script locally and also push the /public dir which your server then serves directly?
A much better option. Still have to deal with the de-facto boilerplate of every html file: head, body, header, footer. Which is why I built something that does it in the browser for me.
> Forgive me for suggesting the first thing that popped into mind, could you run the generator script locally and also push the /public dir which your server then serves directly?
Same as CI - adds an extra step to the process. But as I said, services like Netlify come and go and the news might slip by you and catch you off guard. If I had to go down that road, I have ~10 raspberry pi's 6 of which are currently booted up. A 5 line shell script could easily do that. But again - I see no point in doing it if there's no need for it.
I've had Medium do this to me and in server logs for my homepage I found hits from a Medium owned subnet preceded by hits from a Slack robot. Then some more Medium requests with a referrer from my other social media. Definitely not automated. It seems like Medium manually reviews any story (and user!) that crosses some threshold of traction.
If so, then yes, they have a curation team that is manually reviewing articles for extra distribution across their network. As a publishing partner, I have a copy of their guidelines--mostly stuff that can be done at scale. And mostly what they are doing is trying to find the right topics to feature the article in.
I'm wouldn't be surprised if they have some sort of prioritization system to deal with the volume of articles along the lines of what you describe. If an article is getting traction and hasn't been reviewed, then do it quick.
What I find funny in this post is it goes to great lengths to encourage you to stay off walled gardens and then there's this: "The web is meant for free speech. Your content shouldn’t be jailed for being controversial."
People who like Medium almost always say they like it for the distribution.
So people who say you should host your own blog should be more clear about where you get distribution from.
Almost always, you are going to get distribution by trying to siphon readers away from other walled gardens. But you are almost always working with these massive systems you don't control. Google SEO, Twitter & FB followers, etc.
And even if you manage to siphon away a user and get their email address, you still have to deal with GMail's spam filters. You're never really in control, that's a pipe dream.
I stopped clicking on links which have medium.com domain. It will be a premium article. Medium is choosing anything under premium payment wall, without explicit consent from Author. We need an alternate to this platform
It seems to me that the author completely missed Medium's import tool in his/her "mirror your blog" section. The tool is specifically made to prevent SEO issues when syndicating content from your own blog. https://help.medium.com/hc/en-us/articles/214550207-Import-a... There's no SEO risk as the author alludes to. This is Medium's tool for dealing with that.
I've had Medium do this to me and in server logs for my homepage I found hits from a Medium owned subnet preceded by hits from a Slack robot. Then some more Medium requests with a referrer from my other social media. Definitely not automated. It seems like Medium manually reviews any story (and user!) that crosses some threshold of traction.
Had you marked your article for distribution, i.e. behind the paywall? If so, then yes, they have a curation team that is manually reviewing articles for extra distribution across their network. As a publishing partner, I have a copy of their guidelines--mostly stuff that can be done at scale. And mostly what they are doing is trying to find the right topics to feature the article in. I'm wouldn't be surprised if the…
Earlier quoted context omitted.
What's the best static site generator that meets the following requirements: a) Doesn't use node.js. b) Has built-in syntax highlighting for C#, SQL, PowerShell and Rust at a minimum. c) Is also good at "photo journals" or galleries. I played around with Hugo, but the themes were ugly and it was very weak at managing pictures associated with an entry instead of the entire site.
Some time ago I asked myself the same question. Ideally I wanted not so much a generator but rather something that is completely self-contained. Essentially add a markdown or html file, commit and move on. Surprisingly enough I couldn't find anything that does that so I ended up building one myself. Doesn't support syntax highlighting at the moment but I've considered looking into it. Perhaps I should open source it…
The simplest solution I've used is to just have a Makefile that indexes and stitches together pages using cat/sed/ls. Sure, you have to run make (and possibly make upload if you're not doing it live), but it's not so bad.