Since I made this comment, Twitter announced their new Third Party Social Media policy, and it looks terrible and unnecessary.
https://help.twitter.com/en/rules-and-policies/social-platfo...
203 karma · joined June 21, 2014
Since I made this comment, Twitter announced their new Third Party Social Media policy, and it looks terrible and unnecessary.
https://help.twitter.com/en/rules-and-policies/social-platfo...
People have been tweeting links ElonJet trackers on Mastodon instances (including the official @joinmastodon account!), getting both themselves and the target Mastodon instance domains flagged. This is edgelord behaviour.
Twitter's policy is simple - do not dox people with real-time location information. Elon's jet has a PIA which limits legal use of broadcast ADS-B information (https://nbaa.org/aircraft-operations/security/privacy/privac...). Those tracker accounts are using non-public information.
Jack Sweeney, the guy who runs ElonJet, is on record saying he'll stop tracking if paid money. This is extortion. That is why Elon is pursuing legal action against him.
The only criticism I believe one can make here is that Elon's personal involvement (albeit brought on by attacks on himself and his family) has meant Twitter's moderation team has made enforcement of this particular ToS violation a priority. I agree that the solution to Twitter's previous bias is not more bias, and I look forward to Elon & the Twitter team coming up with a better solution for this.
Unfortunately left-minded techies have uncritically jumped on this narrative of Elon cravenly blocking Mastodon links because 'he feels threatened by it'. Just because someone has been very successful does not mean it is legitimate to mistreat them.
That is, perhaps something some can enjoy nostalgia for but ultimately not sustainable.
Calibre can just be used as a library, right?
We've built a UI builder design tool, in Cocoa and SwiftUI, for the Mac. The content you produce with it is meant to be consumed (using our SDKs) on mobile, but the authoring tool itself is a native desktop app. Of course the limitation of this is our app doesn't run on Linux or Windows, but our target user persona is highly likely to have a Mac.
We've made use of the built-in Document-based apps stuff (NSDocument and friends) in AppKit and it works nicely as a good desktop app citizen.
I've personally wanted to work on a desktop app for years (after growing up during the 90s and admiring the work of many desktop software vendors). I also think that given how almost all productivity work is done on desktop computers that the native software space is rather underserved.
It's interesting how much of the built-in frameworks on desktop are oriented around a document paradigm, for productivity software. Both AppKit/Cocoa on the Mac and the venerable MFC on Windows are great examples of this.
Actually doing building a non-trivial desktop app involved our team getting up to speed on the programming paradigms that have evolved over the last 30 years on the desktop. It really is materially different from the mobile apps many of us worked on previously.
https://apps.apple.com/ca/app/judo-in-app-experiences/id1564...
Cheers and thank you!
I expected more overlap.
I'm not the only one in comments to say this, but perhaps it is interesting to see multiple people reporting this.
https://world.hey.com/dhh/basecamp-s-new-etiquette-regarding...
If I recall correctly, something similar happened at Coinbase, too.
It does appear that the contingent of people with this attitude are a loud, sizable minority. Having them all leave in anger, however, isn't the death of a company despite the amount of noise. Perhaps, maybe even the opposite: without the agitation of an ideological few, the rest will be free to get back to work.
But yeah like I said with the other person who replied we're thinking of taking the reimbursement approach.
Cheers and thanks :)
Thanks :)
We're a remote-first company building a native app for designers to build their own no-code SDUI content for their mobile apps. We have a native editor app for the Mac, mobile SDKs for both iOS and Android, and cloud services.
We're early stage, design and product focused, and have a compelling and unique product.
Check us out at the Mac App Store: https://apps.apple.com/ca/app/judo-in-app-experiences/id1564...
Roles:
SwiftUI Developer (Mac, iOS): https://angel.co/company/judoapp/jobs/1681191-swiftui-develo...
Android and Jetpack Compose developer: https://angel.co/company/judoapp/jobs/1694684-android-and-je...
Backend Typescript Developer: https://angel.co/company/judoapp/jobs/1683975-backend-typesc...
Full Stack React / NodeJS Developer: https://angel.co/company/judoapp/jobs/1684053-full-stack-rea...
That's amore
https://github.com/orospakr/suppressor
I don't imagine it still builds. Perhaps I should have followed through with it!
Congrats to the author.
Entertaining, but clearly very necessary.
Note that I am not arguing that their responsibility is derived from their colonial past; but rather, from the handover itself. (arguably this whole mess really started with the New Territories lease. "99 years". Foolish.)
The app itself is a bit of a different take on the problem space than many of the other well-known offerings in the market. iOS only for now, SwiftUI, and built around enabling "Compelling & Comprehensible Input"-based language acquisition using video, audio, and text you've supplied yourself.
Interestingly - when I started the project I reckoned it would be about 2 years to shipping something useful, which would mean about Q3/Q4 2020. I'm starting to think that estimate was, shockingly, about right.
Cheers to everyone and their projects!
And I lack the technical knowledge or patience to manually do all the necessary option trading to build this kind of tail risk hedge.
The Cambria Tail Risk ETF was my next option, and it did give some positive returns over the Coronavirus crash, but sadly nothing like 3600%, so it didn't do all that much good as a hedge. I assume this is because being an ETF it is liquid, and therefore the entire point of buying options ahead of time is defeated.
edit: grammar.
Not about fear-mongering: rather, seems better to mitigate exposure to extreme harm rather than be anxious about the possibility of it happening.
I have one in my collection somewhere; I even tried to use it a couple of times as a daily driver, but sadly, the project was just too alpha at the time for that.
Certainly interesting that Sun was trying to use it (as relatively open hardware, from a hacker-friendly OSS project, it's was well suited to a skunkworks like that) for their JavaFX work, but it certainly wasn't their own "JavaFX Mobile smartphone".