Obsidian has a webpage to markdown paste/drag function, but IME it's hit or miss.
2,175 karma · joined August 2, 2012
I think you should put in a simple privacy statement that comes down to "Archivy won't make any external requests" if it's going to be as simple as that, and then stick to it like glue. If it's not that simple, be accurate to whatever room you'd like to leave yourself, and then stick to that.
Not having a statement like that leaves the future open for a future git pull to change the landscape. Technically the statement won't stop that, but it'll keep the project accountable.
FWIW it's way more important for this sort of thing because it's a stack you have to invest lots of time and notes into and buy into long term. Were I going to run a personal wiki, I'd be very interested in knowing I could likely use it for a long time.
The opinionation that removes synonyms will kill any chances of this working with legacy IMO. Any significant doc base will hit myriad issues that come down to "I didn't like that form of it." I was initially OK with the idea of a parseable subset, which would be useful, but this goes too far with a "one way only" attitude. No thanks.
That said, someone should do what the project claims to do, without gutting the language. A formalized subset of CommonMark that only skips formally indescribable specs but otherwise preserves everything else would be useful in some situations. It might even become the defacto CommonMark spec if it's easier to implement.
The open office movement should be all anyone needs to see to believe that the no-office movement will have legs. We perpetuated an employment style for years that widely known to be worse for both employees and employers on many levels than a traditional layout, and merely absorbed that as the cost of doing business.
If it works well it'll hit all the much faster, but in tech, anyway, all you need to hear is "less overhead" and "cheap office rental" to know it'll become popular no matter how well it does or doesn't work. I dunno other knowledge worker industries but I can't imagine they're much more altruistic.
Speaking specifically of my own lane, tech, I think you might underestimate how many people--particularly people of color--never make it into the "industry pipeline" because of lack of local opportunities. Those of us who came into the tech industry from the side in the 90s know the school doesn't make much difference at all in most jobs, it's just a predictor of whether you've otherwise prepared. The initial preparation tends to be self-driven, in the best employees, and they exist everywhere. The biggest differentiator comes down to whether someone gives you a shot, and that’s almost entirely about contacts and location for name-brand-company SWE positions.
However much competition there will be then, there's more now with everything chunked up. We're talking about an existing situation. Widening the applicant pool to cheaper applicants can't do anything but help an employer.
The fact that the people doing the hiring probably enjoy those salaries too is maybe the biggest counterargument I'd have to my own prediction and the reason I think it'll take a bit to change. I'm firmly convinced that's one of the phenomena that have kept college degrees inflating--cognitive dissonance around admitting you shouldn't perpetuate your own experience.
FWIW, I think a lot of techies would probably love to have the freedom to live wherever they want and make a decent living. The comp gold rush has been fun, but the industry will arguably be better when it's gone. But the transition period--especially for those of us already at FAANGs or similar--that gets spicy.
Personally I'm hoping it means in a decade or so I can pseudo-retire to an easy remote job somewhere cheap enough to be happy on what an easy remote job pays. Given how hard actual early retirement can be to swing nowadays, that'd be a great holdover strategy to have available.
Nowadays, you could just hire from the flyover states, find all the good techies that didn't make the pilgrimage to one of the traditional hotspots, and train them on the last bits on the job for not very much more money than an international team, when all costs are accounted.
It'll be interesting seeing the trajectory of tech salaries over the next however long though. That part didn't happen either but probably will now.
I can't imagine why someone would pay a Bay Area FAANG salary for any job that could be fulfilled at Arkansas costs. That makes it a really positive outlook for Arkansas techies, maybe a little less so for us in San Jose. I'm sure there are special cases and vanity teams, and culture moves slowly sometimes, but if things truly spread across so will the comp.
What I expect to really take off, though, is things like managed IT you do from home for some manufacturing company somewhere--small groups embedded or servicing larger companies that can be hired and spun up more cheaply from elsewhere in the country.
Basically, everything that people said would happen (but didn't work out) with globalization in knowledge worker industry, I personally expect to actually happen and work out with "domestication" of it to include a large segment of remote workers. The business considerations are mostly the same, minus the cultural, governmental, and time zone barriers that prevented it from working.
It was also a very different place when I started (before Fx4) from when I ended (just before FxOS was killed).
When I started it was a place full of passion, with a lot of technical vision going on (Fx4 was a major reboot and there were a number of side projects going on that showed promise), albeit not necessarily a lot of obvious strategic vision. I'm sure there was more behind the scenes with John Lilly, whose leadership I hired into, but I lost confidence after he left and suddenly it seemed like the message was "desktop is dying, mobile is everything."
Wasn't our mission success based on having enough market share to win a seat at the standards tables and win a place on the "supported browsers" test plan for major websites? Getting a significant part of the shrinking desktop market we'd already executed well on in the past and that competitors were idling on might be better than getting a little of the mobile market that companies with greater resources were bouncing off of left and right, no?
Intranets and SaaS apps are still a thing, and offices still use desktop, so there'd still be a core audience right? Maybe mobile browsers can be different and less standardized than desktop browsers and that's OK? Maybe it has to be? Maybe it even should be while mobile browsing incubates? Maybe browsers won't even be the primary way websites interact on mobile and they'll use client apps instead?
That was a confusing pivot for me at the time, and Mozilla's strategy was to both put all the momentum on mobile and to kneejerk to a rapid update model for the desktop browser, inspired by Chrome. Problem was that destroyed the desktop add-ons community because it turns out you can't do that when you have a monkeypatch/binary extension model with high coupling, and Jetpack/Add-Ons SDK wasn't mature enough or powerful enough yet to replicate most existing add-ons.
It also exhausted the users because the existing flow of having to explicitly approve updates on launch still remained, only now it was frequent enough to disrupt workflows--you never knew when launching a web page meant having to navigate the updates dialog first. Google had designed their browser ecosystem and usability around that update model, it wasn't something you could just graft on. By the time we figured it out Chrome had picked up a decent chunk of the community.
The company then more or less doubled in size, in no small part bringing in a bunch of people from mobile and related sectors that didn't have the FOSS culture in their backgrounds. That culminated in the development of FxOS, which I always felt like was treated as an unwelcome fork by the platform team. Maybe it was because of the need to support two fundamentally different forms of interaction, two different models of security, two different distribution and update models, two different lots of things in wrapping Gecko with an application vs. wrapping it with an OS. That also divided the company, since there were now two broadly different technical missions going on, albeit sharing code.
When considering the success of FxOS vs. KaiOS, it's worth thinking about the drag having two competing priorities in the same company causes, and how that might clarify when the 3rd party is doing the fork instead. Conflicts like "how do you release a fix for Fx the browser when it'd zero-day FxOS the phone and you can't get an update through the carrier for two months" may not be so much of a problem to figure out without that tension. I'm extremely impressed with what Fabrice and co. have able to pull off with KaiOS, and I bet lightening that load helped a lot.
When I left, after it was plain FxOS was not going to succeed at that time, in that environment, it was still a place full of passion--but it was now also a place equally full of frustration, and not with a lot of strong leadership going on and a sharply muted FOSS culture. Seemed like there were a lot of missteps and platitudes, but not a ton of optimism. I was very happy to see Servo come to fruition and Quantum be released, because I honestly expected Mozilla to go down in flames before they could get the desktop browser to a state where people who'd defected would install it again.
I'll always treasure my experience with Mozilla--and having worked at two FAANGs now since, I agree the level of talent was equal or greater at Mozilla. But I do have to admit I wish I'd shifted that five year period about 2-3 years earlier across the board. I came in right after the really good part, I think.
And I do have to wonder if that talent would remain as good without the strong FOSS culture that incentivized me to be there. I worry when I see people like Ian getting laid off too, because there's simply no way that can be about talent. If he doesn't still fit there, that implies a level of change with which I'd have been deeply uncomfortable.
Don't get me wrong, Apple is OK at consumer audio. The Homepod is nice, so are the APPs. Even Beats aren't too bad nowadays. But they haven't released consistently better audio products than Audeze, Sennheiser, Sony, M&D, or even Bose--their closest comparison, since both Apple and Bose lean hard on DSPs for their SQ.
I suspect the second version of these headphones will be pretty excellent. Apple does learn from its mistakes, whatever they'll end up being. Trick is Bose and Sony will have learned from their mistakes too. It'll be interesting to see if Apple ends up being able to compete on audio, not just style.
I wouldn’t play really competitive shooters that way but it’s low enough to not bother me even in mouse/keyboard FPS (for the PC services). For controllers it’s completely negligible, like playing with a Bluetooth device or on a 2015 TV.
That said, I’m in Santa Clara County near one of the major Shadow datacenters, probably the others too, and I have gigabit. I am in the ideal situation you describe.
So is a lot of the world though. US is super rural for its economic weight but that’s not the norm. Most developed countries have much higher density and better networks. I think we’ll probably just end up dragging behind the curve until we mesh the flyover states better.
Ambien has costarred in a few of those "I'm sorry, they did what?" stories. It can make your behavior random if you don't fall asleep quickly or get woken early.
Things sure were heavy before the internet got fast.
There are a number of programming languages and APIs with excellent documentation, but theirs were above and beyond.
Finder actually fills the screen (the Apple app I did originally test since it used to represent reference windowing behavior) but only in list mode, which happened to be my default. In icon mode it does the old school top-to-bottom thing, as I found out after the replies.
But Chrome fills the screen, OmniFocus fills, Keyboard Maestro's editor fills, Firefox fills, etc. I think a lot of third party apps will fill the screen since it seems to come down to whether the dev gives it a different aspect ratio than native to "show all content." Most stuff seems not to do so anymore, presumably because that behavior is weird.
But to your point, apparently Safari was a huge oversight on my part and it's definitely not as consistent as I thought it was. Sorry if I got hopes up.
That said, to the extent an app will do that at all, opt-click-max or title bar double-click is the way to do it. Otherwise you're stuck with one of the screen snap apps that can also redefine the buttons for you.
Even within the current era, render on server, render on client, ajax (the mix), etc.
We're seeing it now in gaming. Vidcards are the cost of a whole system now, games have become huge, and fast storage is still expensive; but bandwidth is increasing along with A/V streaming being perfected, so someone figured out how to minimize apparent control latency and now games are streaming. Once vidcards get cheap and SSD storage capacities catch up to 150GB games it'll flip back until the balance tips again.
If you don't hide the dock/start bar it maxes to its limit, if you hide it goes to the bottom. Maybe it was unclear when I didn't mention it'll max side to side too if the bar is on the bottom. If bar is on the side it'll leave a gutter on the side.
TL;DR it's a normal maximize--doesn't cover the doc or menu bar and you can float windows in front of it since it's not full screen mode.
Assuming you have "zoom" set in System Preferences | Dock, double-clicking the title bar does that too, I believe.
I don't want to paint these as silver bullets. I still deal with my anxiety disorder on a regular basis. I just feel more able to look at it in third person a little to defuse some of the worst bits.
Edit: I'm always hesitant when someone uses the word advice, so I gave a vaguer reply than I needed to. I won't give advice but will give a little more detail.
Looking at the original list, the specific ones there I also have tried to improve with varying success are stoic philosophy, nutrition and fitness. But I'll also add sleep, since of them, sleep has had the most immediate effect that I've noticed. However, there's a chicken/egg thing there if you're too uncomfortable to sleep. I used a short course of sleep meds, but those have their own risks so YMMV.
Stoic philosophy is good to aspire to, but it's more end goal than technique IMO. It's a good thought yardstick, though, for what you "should" be feeling if you can step outside yourself a little.
So I took the comment's point as that there are multiple potential causes for a given manifestation, and chronic conditions in particular are confusing because they invariably end up with physical -and- mental symptoms. There's something to be said for exploring easing the one you can do by yourself, at least to some extent. Mindfulness, slow breathing, and some of those other techniques helped me too. No matter which aspect is primary and which aspect is secondary, easing the mental stress some can still help.
I believe RubyMine is the same, if not all of the other paid IDEs in the Toolbox. They all include WebStorm's functionality since you can build a web app in pretty much anything, at least on the back end.
That also lets you do a one-field quick task entry that includes +collaborators or an arbitrary number of @tags, Those appear to be the two pieces of data you capture beyond the descriptive text. You get a few more than ten projects too, which is the max number you support for the most expensive plan.
The big obvious difference is the pricing model. You're $80 a month for unlimited users on the annual startup plan, vs. $5/mo/user for Todoist Business. For an org of any size, Todoist would get more expensive for sure.
But under that 16 team member break even point, it sure looks like you're implementing a pretty sharp subset of standard features. And when you consider Todoist Premium is $3/mo/user (so now a 27 person break even) and can be used for simple workgroup collaboration as long as you don't need centralized billing or a team admin interface--which seems squarely like your target based on the simplicity pitch--you're very much on the high side of pricing, but with a minimum of features.
I'm not saying there's no advantage here, but I certainly can't tell what it is from your landing page. Once you're at enough users where the pricing makes sense, I'd think you'd really miss a lot of other standard functionality. Unless there are queries, due dates, the ability to attach a comment chain (or at least a notes field!) to the task, etc, I wouldn't think this would cut it. If those features do exist, they're too well-hidden before signing up.
My guess is his choice of phrasing was influenced by Adams, given he was reportedly an sf/f enthusiast, but it's a pretty standard sort of geeky small talk reply.
Did sound an awful lot like they thought the suit was ill-timed and half-baked, though. I might have been misled by editorial content in the reporting.
To your point, I'm sure it caches a fair amount of that analysis in its .obsidian directory, but to mine, it can still calculate them from scratch on a new (or newly synced) note set. It does so invisibly the first time it sees the Vault (or the new file in the Vault directory, if you add it from elsewhere), so it's still portable, just with an indexing phase if you want to show a backlink or graph pane.
The important thing for me is that most other plaintext notes editors support the forward [[links]] that are the only real "source" data. The implied backlink analysis is just that, results of an analysis. It'd be nice for the cache to be portable, but not necessary.
Transclusion is where I'd agree with you, since that actually appears in the notes themselves rather than as part of an active sidebar. You're more or less stuck with proprietary software that knows how to look for anchors and render their targets inline, at least until/unless we get a generic format for it. But so far that's been more a reason I can't have transclusion yet than a reason why I'd move off plaintext notes in a directory.
The library is properly an example of a DBMS: database management system, it's only "a database" informally to lay users.