My theory is that there is quite a few servers that are chosing to defederate. The number of total servers continues to drop according to fedidb.
Or admins are just finding it not worth bothering with administering their own server and turning them off.
You can have the code to my kernel, sure. You don’t get a login on my machine, though, and you’re definitely not on the sudoers list.
It sounds like you want a way to collect articles, including full text offline, and organize them in a searchable way. Why do you need RSS for this? Just use a blogging platform where you can organize each post, list/sort/filter by date or topic or original source, and use the search functionality in the actual blog platform.
Dedicated units were available from brands like TomTom in the early 2000’s, and cell phones started getting it around 2007 or so (I remember very expensive blackberry plans had it around then). Android launched with it in 2008, and iPhones started allowing apps like Google Maps with turn by turn navigation by around the end of 2012 or so.
They weren’t the ones to come up with the name, so they have to follow what everyone else calls it.
It’s why I much prefer MacOS over Windows. The command line makes sense. The file and folder structure makes sense. The defaults can be a little bit weird but a little configuration can help me feel right at home.
No forum, email or word processor (even WordPerfect for the c64) or Notepad uses this
I think the convention of 2 newlines for each paragraph is a longstanding norm in plaintext. The old Usenet, list servs, plain text email, etc., was basically always like that, because you could never control how someone else wraps their text. 2 new lines would be a new paragraph no matter what, while single new lines could create ambiguity between an author’s intentional line break versus the rendering software’s decision to wrap an existing line.
For lists and the like, you’d want to be able to have newlines without new paragraphs, but you’d generally want ordered lists or unordered lists at that point.
For an obvious example of markup languages where newlines and carriage returns don’t have syntactic meaning, look at literally the most popular one: HTML.
So markdown was essentially enforcing the then existing best practices for pure plain text communication, to never use single line breaks except in lists.
Most UIs don’t even have a preview option, let alone need one, because they don’t require you to have a stick up your ass to ‘get’ using them.
It was pretty common before Markdown took over that forums and other user-input rich text fields used raw html (or a subset of html tags), or something syntactically similar to html’s opening and closing tags (BBcode, vBulletin markup, etc.).
Markdown was basically the first implementation that was designed to be human readable in plaintext but easily rendered into rich text (with an eye towards HTML). It’s not a coincidence that it took off in the early days of the “web 2.0” embrace of user-submitted content in asynchronous forms.
I get the complaint. But I think markdown makes a lot of sense as a way to store and render text, and that one compromise is worth it overall.
That dude was fired.
Exactly. To extend the junk food analogy, this is like making donuts from scratch in your own kitchen: customized to your preferences, maybe tastes better, but ultimately you’re still making a mess in your kitchen and eating unhealthy.