Medium bans user for Chrome extension that opened articles in incognito mode
twitter.com
twitter.com
Own your content, use eveything else as tools.
These days, the question I usually ask is, "Can I walk out of this and what do I have to do if I need to?"
I'm not sure why the hell anyone would do anything else to be honest. It has been an insane proposition putting content on something you don't control.
Medium’s promise is “you focus on writing, we’ll deal with distributing.” They don’t live up to that promise in lots of ways, but it’s hard to fault someone for not wanting to deal with the tech.
This is why I don't write articles. The investment vs return is low based on the exit costs, risks and benefits.
For the topic's problem, I'd love to see some automated setup app that would take a "VPS host account", and do all of the installation/configuration to support service(s) running Free software to accomplish a high level task (eg a blog). Like a graphical NixOps with precanned configurations.
You'd need to initially cut down the number of options (say VPS account must be at one of 2 hosts, domain must be at one of 2 registrars), but I think the main problem would be trying to straddle so many abstraction levels.
How to overcome this? Maybe it would be enough to be in some mobile app stores with a distinctive memorable name (despite the horrible UX on mobile), and have a slowly accreting fanbase. Then every time these issues flare up someone would say 'Install LibreZooks to run your blog" in addition to all of those "just use DO and Docker" comments. People do seem to be moving to Mastodon slowly with the current happenings, but decentralized-first stuff can never match the advertising saturation of well funded surveillance companies.
There's also the difficulty that many people these days aren't publishing just to publish, but they're publishing as a side hustle or hoping to get rich. So middlemen like Medium that promise to extract as much as possible and then share a cut have another leg up over "default options" like running Google ads or whatever.
How about car repair? As a car enthusiast, I think anyone who fails to invest time and energy to really understand how cars work, from cv joints to TPMS systems, is putting themselves at the mercy of repair shops that can be capricious.
And financial planning, and yard care, and zoning policy, and. . .
Point being, life is too complex for everyone to be an expert in everything they depend on. And we all depend on things where we’re not even expert enough to know the implicit assumptions and dependencies we’re taking on.
I don’t think we can break through that. I’d love to be wrong, but I just don’t see a way for people to have deep understanding of every tool they use while still doing the stuff they want to do.
The other concern is legacy. I’m getting up there in age. I would like some of my work to continue to be useful after I retire without me paying for domain renewals or worrying about hosting. Without my intervention a github.io site will probably outlast a onionisafruit.com site.
Then maybe group them on a domain with subdomains or just subpages?
You're not on Reddit, pal.
Super easy to maintain as publishing is always just a commit away and if you're feeling fancy you can pivot to your static site generator of choice later
It's always a question if risks, and they're miniscule for both GitHub and gitlab
GitHub Pages (or GitLab Pages, if you prefer) will host your website for free. You don't even have to know HTML to make your site look fancy, just basic Markdown; GitHub will run your Markdown files through the Jekyll static site generator by default (this can be disabled by adding a blank ".nojekyll" file to the root of your repository).
Assuming you have a GitHub account and that you only need to serve static (HTML/JS/CSS) files, launching a site with your very own domain name is as easy as:
1. Buy a domain from the registrar of your choice
2. Create a repository called "<yourusername>.github.io" and a "index.md" or "index.html" at the root
3. Go to https://github.com/<yourusername>/<yourusername>.github.io/s..., select the "master" branch as the publishing source, and enter your domain (excluding the "www.") under "custom domain"
6. Go to your domain registrar's website, and find your DNS settings. Create four "A" records pointing to GitHub's IP addresses: "185.199.108.153", "185.199.109.153", "185.199.110.153", and "185.199.111.153". Create a "CNAME" record pointing "www.<yourdomain>" to "<yourusername>.github.io"
Then if GitHub decides to block/censor/ban you, all you have to do is switch to a different provider (or potentially self-host). If your registrar blocks you, you can transfer your domain to another one.
What if your hosting provider or authorities seize your domain?
But definitely don’t buy a domain through a content platform. Buy it from a registrar and manually link it to whatever hosting/content platform you’re using. Preferably hosting with offsite backups that can actually be used to reconstitute a site elsewhere.
Feels like there must be alot of limitations, like not for profit, limited bandwidth/pageviews per month, and must be github project oriented etc or?
> You can use GitHub Pages to showcase some open source projects, host a blog, or even share your résumé
> GitHub Pages is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)
> In addition, your use of GitHub Pages is subject to the GitHub Terms of Service, including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity
> GitHub Pages sites have a soft bandwidth limit of 100 GB per month
https://docs.github.com/en/pages/getting-started-with-github...
There are certainly better hosting options out there that provide more freedom, but GitHub Pages is nice for someone who just wants to get a personal site up and running without much fuss.
Or if you want to do it yourself, just install a Ghost Docker container in some spare space of that $5 Digital Ocean instance, and you are ready to go.
With a $5 DO instance I've got a self hosted recipe book (RecipeSage), Bookmark Service (LinkAce), blogging platform (Ghost) and also use it as a Socks Proxy. I've got nightly backups for $1.5 and everything was as easy as docker-compose up.
I understand non-technical people suffering the issues of internet deplatforming, but for a self-named "The Practical Dev" ?
When Medium was better, it was easy to get a good domain for the same handle as your Twitter, with a good UI/readable final product. It's changed a lot since and kinda sucks now, but it's a step up from people using Pastebin as their blog.
As far as I am concerned everyone should just move to substack at this point.
But not so fast about Substack... they recently started showing modals.
In the end, running a website costs money. What are you going to do.
There's no reason for authors (who are Substack's customers) to want to make the platform more annoying for readers (some of whom are the author's customers). If the author is not making enough money (perhaps because Substack has started taking a bigger cut to cover costs) they need only to improve their writing and/or put more of it behind the paywall in order to get more subscribers.
Does anyone have a uBlock rule to drop them all?
/* Substack modals, nags, etc. */
[class*="frontend-components-SubscribePrompt"] {
display: none;
}
Saved as "Substack" and applied to any page/domain which uses Substack.Otherwise, for UBO, these two should work:
###.frontend-components-SubscribePrompt-module__subscribeDialog--2_6UY.frontend-pencraft-FlexBox-module__flex-align-center--21WCV.frontend-pencraft-FlexBox-module__flex-direction-column--2sph3.frontend-pencraft-FlexBox-module__flex--fK-9V
###.frontend-components-SubscribePrompt-module__background--2DQPj
I suspect Substack vary their element names (e.g., the "2_6UY" and "2DQPj" strings in the above list), so that substring matches as I've used in my CSS example should be more robust.UBO uses the Easylist blocking syntax which ... I can't seem to find documented, so I'm guessing as to the specific patterns. Corrections/clues welcomed.
In this case, it's even harder because it's about maintaining a website synchronized with a mailing list.
Make something open source and ad-free and they'd all run to it, I'm sure.
I agree, so maybe we should work towards making it easier for them.
I was thinking about spending my Christmas break fixing Friendica bugs, but now I'm suddenly thinking about building my own ActivityPub blogging platform (though no doubt one already exists). But of course that's not going to be enough; it needs to be trivial to deploy and host, at little cost. I believe many cloud hosting providers have a free tier. Would be nice if something like this could be easily deployed there. Create a tool that sets the whole thing up, handles the DNS name, the payments, and deploys the site.
In fact, it would be nice if ISPs offered something like that for free with your internet connection, to finally do justice to that 'S' in their name.
So much early web lost from URLs like http://www.myisp.net/~username/
Users can continue authoring on those platforms but can begin promoting their own-domain version and gradually move their users off.
I know sometimes there is a project that looks good but the maintainers are impossible to get along with. Thus there is sometimes a need to start over. Most of the time though what platforms need is more people to help out: fix bugs, write documentation, translate the UI, run UX tests. That is all the thankless unseen when it works work that makes good commercial projects more polished than most open source projects.
It's quite weird to see people fawning over the latest startup blogging platforms in 2022.
While people have been migrating to/from medium and substack, wordpress.com has been here the whole time, and it's still quite OK. The killer feature it has, of course, is that because it is open source you can export your data and run it yourself should things go sour (or if you just outgrow it).
Whatever features substack/medium/whatever closed source platform may have that you think you really need, the anti-feature of lockin is not worth it.
I understand the need for things like substack to grow an audience, but I maintain that someone who really wants to run a blog for many years should own their audience.
Substack lived long enough to become the villain. It was honestly quite the heel turn, but they’re all in.
As far as I am concerned everyone should just move to ${random_new_platform} at this point.
[1] https://notes.ghed.in/posts/2022/substack-centralization/
> Medium decided to ban me because I built a Chrome Extension to automatically open Medium articles in incognito mode.
And, here's Medium Rules link:
They should have some rules for themselves: "1. Don't become clowns."
In those days, there was no super world power America. There was no UN. There was no successful secret fraternity that espoused ideals like freedom of expression. There were just kings deeply seated in self interests.
This online world feels much like it is the same.
Man I truly do not like Medium, if i land on an article i just close it immediately!
Even something like getting some cheap hosting and spinning up a WordPress installation will work well (and is easily backed up, exported off-site etc).
You can for example use Ghost to host your content, then syndicate it to Medium. But just sticking a website on the internet is pointless if no one will see it.
I've sent them a final email asking for info on the issue, after that I'm removing all my content from the platform.
(Edit: I’m not asserting that it is in fact a violation, but that its having been approved suggests it didn’t seem like one to the Web Store folks, at least, and maybe Medium should have addressed this by trying to get it removed rather than banning the user.)
Maybe user software shouldn't be enforcing arbitrary ToS, but should instead obey the user? Do we really want corporations colluding with each-other to enforce their whims over us through their products that we are surrounded by, and are becoming necessary for modern life? What next, disk firmware scanning for copyright violations?
I'm sorry if this comes off as harsh, but I am sick of people using the ToS (that a company can make up at will) as any kind of justification, pro- or against. They can and do write anything they want there.
Hosted by them or self-hosted.
Not affiliated in any way. Just like the idea.
someone should assemble and post a list of all tools that makes medium better?
But I don't post using medium that often.
I use GitHub README.md for my journal. I have been journalling in the open since 2013 and I am up to 700 entries. (See my profile)