As a Brit who reads the NYT and knows Krugman mainly by his writing there, I found that Wiki piece enlightening and fascinating. I will make an effort to read him more widely. Thanks.
FWIW, I also enjoyed reading his latest NYT piece for its substance, observation and its humour:
What about the actual vs. perceived wear and tear on the ships(?) transporting the goods, do they experience 5 days worth of repair/upkeep (fuel?) needs, or 5 minutes? Maintaining the transport (vehicle, ransible, teleporter, whatever) has some sort of cost - TANSTAAFL.
+1 to the Bookmarklet, it's what I use now for another service and it's simple and works (and can be hotkeyed in most browsers); I suspect the GP did not find the docs with the bookmarklet option as it's on the User Settings page, not the Links page: https://www.linkace.org/docs/v1/configuration/user-settings/
> Browser bookmarks are actually not the same as the bookmarks I keep in LinkAce
You are not alone, I currently use Diigo with the same needs; the Diigo bookmark list is massive, unwieldy, goes back decades - the in-browser bookmarks are slimmmed down to just what I use commonly. What we really need is a new RFC "LinkDav" which follows in the footsteps of CardDav, CalDav and WebDav to round out our data portability lives. Want to try your hand at writing a RFC? :-)
On the Import docs section it just says "...in the HTML format" - there's a Chrome, Firefox and IE version of HTML Export from Diigo, it would be helpful to understand which one would be the best for import to LinkAce: https://www.diigo.com/tools/export
There is a standard already, called OPML that is already used in every RSS reader to store a list of feeds. Being XML behind, I'm sure it can be adapted to contain everything related to a bookmarking service; it's not a complete format like CalDAV and friends, but it looks like a solid base to build on.
OPML (I am familiar) could be used as a basis yep, but it's a file format which is more akin to vCard, vCal and iCal - CalDav, CardDav and WebDav are the transport(?) layers (API layers, operational layers, call them what you will) which sit on top of the file format standards providing the interoperability.
Conclusion: explicit is better than implicit, and what's more, in this case the implicit alternative was depending on a non-standard choice made in the specific tool for obscure, legacy reasons.
This fits almost any situation (explicit vs. implicit) and I'm a big fan - when mentoring I tend to say "yes that was the default when you looked today, how do you know it won't change tomorrow? If you want specific behaviour, be explicit don't trust defaults." (more or less, depends on subject - commandline switches to code loops, same advice)
I hit the 2000 HN post character limit pretty hard on this, had to delete all line items with "NONE - $0" in them and so forth to squeeze in all the data above. Pretend you see that in each item above. :)
This was basically a de-badged Dell Inspiron 7000 clone (guessing same factory of origin), it had the cutouts for Dell stickers on the lid but had a generic AMIBIOS (or was it Phoenix?) instead of a Dell branded, but otherwise all the same hardware, all Linux friendly (added my own PCMCIA card for modem/NIC).
A .com will cost < $100 for 10 years at most registrars and as you've noted, this is for personal use (not company branding, e.g.) so the name is not that important. I'll posit that most folks know how bad the name squatting business is around the internet and nobody really thinks hard about somethingreallyobscure.com so long as it's not confrontational in some way (religion, politics, swearing, etc.). But I will say "anything ending in .com has more implicit trust" - I'm always mentally questioning if any link from one of the new gTLDs is just a spammer/ne'er do well.
Been here, done what you're doing, there's a .com out there with a fun and interesting name which somehow resonates with your personality. Think long term - avoid trademark/copyright branded words in the name, avoid being too narrow in case your hobby changes, easy to type and spend some time really thinking about plurality - I've discarded a lot of ideas simply because it would lead to other people going "was that with or without an (s) on the end?" - same with double-letters in the middle, just avoid them. I try and focus on 5-6 syllables max which break on natural language barriers (English).
To put an example to the other comments, look up the history of the XYZ domain - in a nutshell, they had a fire sale selling domains for pennies to gain market share. Besides normal people, three groups descended upon it: spammers, squatters and hackers. 6 years later and the entire .xyz space is blocked in Enterprise firewalls (source: my workplace) due to that behaviour, preventing me from getting to valid tech sites on the TLD. The XYZ image is still tarnished from cheap domain fire sales at the beginning of it's life - I'd never pay $50 for anything in .xyz today.
To contrast, the .io space entered at what, $50 USD? and continues to be expensive to maintain year over year, providing a natural monetary resistance barrier to the same three groups of people (spammers, squatters and hackers) and seems to enjoy a healthy respect amongst internet users; most consider it a tech-type domain space with tech worker dollars buying the domains for real sites, I even owned one for a brief period when they came out.
While I only named .xyz above, my (enterprise) company blocks several other TLDs as well like .info, I'll check .icu when I'm back after holiday but would not doubt it's blocked. Corporate IT subscribes to some sort of hosted service, I would not doubt other companies are using this same service (name-brand).
I think it's just part of some generic category of strict blocking used by the hosted service - there's a lot of other stuff blocked, we generally don't get reasons as users other than it being the corporate security posture. We are a business partner of many firms (some have high security due to their needs) so our company trends in that direction - maintaining compliance is a big deal, entire team(s) manage it at various levels.
Do you know the name of the service? Blocking .xyz names as a whole would cut your company's employees off from accessing sites like Engine.xyz, ABC.xyz, and Starship.xyz.
> To put an example to the other comments, look up the history of the XYZ domain - in a nutshell, they had a fire sale selling domains for pennies to gain market share. Besides normal people, three groups descended upon it: spammers, squatters and hackers. (...)
I don't know which point you were trying to make, but as far as I could tell that's the business model that's being followed by all vanity gTLDs.
The only nuance I've noticed is that there are a bunch of domains being sold for peanuts with the caveat that after a year or two it's price is hiked to somewhere in the range of 30-50$.
We used to use Freshmeat.net for this for a really long time, Slashdot moved it over to Sourceforge but then it died in 2014. http://freshmeat.sourceforge.net/
Neat! I added the top level RSS [1] to The Old Reader [2] and it pulled up just fine (validation), the title shows up as "xfer" by default but otherwise works fine for this reader.
