ben_thatmustbeme"ttk.me/ t4bV1" wastes an extra letter, and twitter i think will interpret the first part as a URL and create the link, which negates the original point of them
ben_thatmustbeme"ttkme:t4bV1" is not recognizable as a URL, and also is ambiguous tt.kme? ttk.me? t.tkme? works for this case only because those others are not TLDs, but makes processing messier for sure
csarvenPoint being that you can never control how something else will interpret the characters "a b". It is just a string using an arbitrary pattern which is not inline with any existing or widely used system. This is in contrast to "a/b" which at least mimics what is known and arguably meaningful for many.
csarven"a b" in status updates that are not hyperlinks is equivalent to "view only" citations. Pick up any academic paper (in PDF) and see the reference section - just some string that one has to copy/paste elsewhere to retrieve the information - bad UX IMO.
csarvenDoes it any practical use? Is there any documentation / survey on people copy/pasting "a b" and then changing it to "a/b" to retrieve the resource?
ben_thatmustbemewhy is that needed. its intended to say you never need to click back as there is nothing more there, but in the rare case you do actually care, i want it known that this is published elsewhere
rhiaroI definitely get people complaining about links to posts that don't contain anything extra. But I think if I broke the links, I'd get an equal amount of people complaining my links weren't right (documented on wiki)
ZegnatI think rhiaro makes a good point. When is the original post enhanced enough that it is worth linking to? PSC is used for posts when there is no extra content to be had at the website, but comments, likes, etc could count as extra content
ben_thatmustbemeZegnat indeed. I honsetly have removed PSCs entirely as I feel that is the case, but I do see their use. the UI of a link thats not labeled as a link to the same content is frustrating UI
LoqiA permashortcitation (or permashortid), abbreviated as PSC is a short non-hyperlinked citation to a post permalink, in contrast to a permashortlink which does hyperlink to a post https://indiewebcamp.com/PSC
kylewmZegnat: I've seen lots of people who blog a lot and measure these things say they get MANY more readers when they post on Medium rather than their own site
ZegnatSo, I am not a big Medium user. How does Medium help with discoverability? I often end up on Medium only because people link to good articles. People link to good articles outside of Medium too, and I read those too.
ZegnatSo the daily digests do not actively help author’s discoverability. Because that is the big part here: why would an author be more “discoverable” on Medium than on a personal blog.
Kongalooshrhiaro: how do you feel about storing your information. You use a DBMS, but it seems like there's a lot of people just storing things as html.
KevinMarks_“You can get a site up and running in PHP in a few minutes, and that’s the problem. It used to be the terrible choice you made when you needed to get something done on the Web, but increasingly JavaScript has replaced it as the default terrible choice.”
kylewmKongaloosh: "a lot of people just storing as html" would be an exaggeration. it's an interesting approach, but i think maybe only 1 person here does it
aaronpkKongaloosh: I store everything in files (yaml+markdown) but have a database which indexes everything except the post content. makes it easier to query by tags and date ranges
aaronpki havent had my personal site db fail yet, and I have managed to keep quite a few mysql DBs around for many years. I think the bigger reason I like this is I don't have to worry about syncing data between my laptop's DB and the server's
aaronpki'm much less confident in my ability to admin a postgres database, even though there are so many things about postgres I like better than mysql
kylewmaaronpk: that bastianallegier project sounds really similar to what you do, flat files with some redundant data in SQLite (intead of mysql) for indexing
aaronpkhrm. i normally don't like templating engines because they invent their own syntax and php *is* a templating engine, but i'm seriously considering using the Blade engine from Lumen http://lumen.laravel.com/docs/templates