In this particular case only Article 13 could be a problem, but it’s this represents the kind of wonderful things that are becoming impossible because of regulation, walled gardens breaking net neutrality, etc.
Net neutrality is what the web was like in its early days before it was usurped by commercial interest. Nowadays regulations appear to be the only feasible way to retain net neutrality.
The biggest advantage with medium is the visibility of your blog post. Why not just use google blogspot website if all you want is just adhoc blogging?
Agree. I find my use case for a small, personal site cum blog perfectly satisfied by Github Pages. Plain HTML and CSS, no Javascript. Now that Github Pages has Let's Encrypt support, there's no need to front it with Cloudflare (though the SSL support right now is not without bugs. The auto-renewal for my domain has been stuck for months now.)
Honestly I do perfectly fine with a host and some autogeneration. I have considered just editing the raw HTML and keeping it in git, but it seems a tad pointless.
This is really, much faster than pastebin (no captcha) and doesn't require registration like gist.github.com.
I think it should say on the homepage that the content is parsed as markdown (it's in the howto but could be summarized as one word that is starting to be quite universal (even Reddit uses it)).
Very neat, I'm going to use it often, thanks.
edit: yes and HTTPS would be nice, Cloudflare does it for free and automatically for instance (Heroku too and I'm sure many others)
edit2: Also it's removing newlines: http://txti.es/yw35f (should be test and test2 on two lines).
May I suggest ability to have simple E2E encryption, so you, the service provider aren't aware of the shared content, thus can reduce legal complications.
The encryption key should be passed in the fragment portion of the URL like http://txti.es/{POST_ID}#{E2E_KEY}. Else, it's still being sent to the server (and potentially logged or intercepted).
47 comments
[ 3.2 ms ] story [ 102 ms ] threadMaybe add `https:` to it. Free with letsencrypt.org
Eww ;)
Isn't it "come", short for become?
First entry:
> : along with being : AND —used to form usually hyphenated phrases
But that's how it often is as a non native speaker ... Everything is fine until you have the strangest misconception.
I think it should say on the homepage that the content is parsed as markdown (it's in the howto but could be summarized as one word that is starting to be quite universal (even Reddit uses it)).
Very neat, I'm going to use it often, thanks.
edit: yes and HTTPS would be nice, Cloudflare does it for free and automatically for instance (Heroku too and I'm sure many others)
edit2: Also it's removing newlines: http://txti.es/yw35f (should be test and test2 on two lines).
That's probably because it uses Markdown for formatting so you need an extra carriage return to actually push it to a new line.
http://txti.es/abjr
For content small like this, GUN or SSB is better.
Also, Txti supports edits, currently on GUN can do mutable & immutable data - IPFS & others are only immutable.
One request: could you support "raw" in addition to json, xml, etc? So it would just be the text exactly as entered?
Question- what are your plans on handling abuse? And what are you requires to store by law?
May I suggest ability to have simple E2E encryption, so you, the service provider aren't aware of the shared content, thus can reduce legal complications.
Example:
* Have a encryption key generated on client side
* Share link will becomes http://txti.es/{POST_ID}/{E2E_KEY}
* You, as service provider, only stores POST_ID and its encrypted content.
* Link sharer passes the complete URL around, which contains the key to unlock the content
* Content are fetched and decrypt on client side