Love the fact that it's entirely in the browser without an app too.
1,005 karma · joined May 1, 2017
working on flexpa.com
Love the fact that it's entirely in the browser without an app too.
The last Chrome release related to this was in September: https://blog.chromium.org/2020/09/chrome-86-improved-focus-h... where they safelisted a number of protocols in registerProtocolHandler().
I'm extremely impressed with the progress that IPFS has made - I'm an active (daily) user, and have implemented archiving systems with their tools. Clusters and pinset management in particular have improved substantially, browser support for ipfs:// natively has started to roll out - to name two things I've worked with recently. The libp2p project itself is another example.
Why wait for travel restrictions to be lifted?
EDIT: I meant of course our parents, not us - there might be a few 90-year old readers among us though :)
> Well this is an exceptionally cute idea, but there is absolutely no way that anyone is going to have any faith in this currency.
The very nature of an innovative idea is that few people see it.
Vercel makes it really easy to deploy isomorphic JavaScript applications, to the point where I barely have to think about the runtime context. Thinking back to the ~2015 era, it feels like magic in comparison.
People often retort that no one cares about decentralization, well we're going to find out if that's really true over the rest of the decade.
From Recital 39 of the GDPR:
"This requires, in particular, ensuring that the period for which the personal data are stored is limited to a strict minimum. Personal data should be processed only if the purpose of the processing could not reasonably be fulfilled by other means. In order to ensure that the personal data are not kept longer than necessary, time limits should be established by the controller for erasure or for a periodic review."
In the context of F500, I've seen compliance efforts around this that have mandated deletion in the case of inactivity for consumer applications that most people would have reasonably assumed would have been kept around even if they didn't log in.
This is hinted at in the article "...to better align with common practices across the industry, the company said on Wednesday." And if we're going to take a cynical view, wouldn't it be that Google would never delete user data (the source of their revenue) unless they absolutely had to?
This will be especially true looking forward to the post-COVID relaunch of tours and festivals.
To the false negatives problem itself though, I think your implicit assumption is the correct one - that false negatives are a bigger potential problem than false positives. In my experience, the false positive rate on declines was immaterial to the business. The impact of a false negative is definitely a different question.
This would have saved years of development efforts and maintenance on treasury operations for my team at a previous gig (in the live events/ticketing space, who are probably going to read this comment - hi guys).
This part of the project is called Azimuth - and can be used for other things: https://github.com/urbit/azimuth
SSB doesn’t have a root node, so if you think of yourself like an island the data transfer required from your first “bridge” is going to depend on what you are bridging to.
In practical terms, if you join one of the SSB pubs published in their documentation, you’ll sync whatever is on that pub.
There are plenty of high quality, _critical_ comments and discussion to be made on this submission and broader subject - why eschew that in favor of flamebait?
edit: You've since edited your comment, but I still think it could be substantially improved if you want an interesting (and provoking!) discussion.
If anyone is wondering about this, the basic business challenge you have to solve is being in the right place at the right time. This kind of thing is very sticky once its in place, and most startups don't realize the complexity in the domain early enough for a stand-alone service to make sense to them.
I think as far as startups in this space go, the best path forward would be to nurture an open source project in the long term.
I ended up open sourcing my work after the pivot here: https://github.com/affiga/scaledger
Affiga provides customer data for transactional businesses.
I’m looking for people who (still!) want to work with Ruby, and who are at least a little skeptical of JavaScript SPAs.
Remote only, but US/Canada based is easiest for me to work with.
I’ve raised a small seed round, but not enough to pay a FAANG salary. You’ll get full transparency of the company’s cap table and balance sheet though, and we’ll negotiate an actually-generous equity split.
On the flip side, you’ll spend basically all of your time building and none of it in synchronous meetings.
The team so far is just me, but I’ve got a track record of success — including a successful exit (universe.com sold to Live Nation).
Contact via email in profile.
* Immutable entries
* An API introspected directly from a PostgreSQL schema
* GraphQL subscriptions for real-time updates
It does so with a Node server written in TypeScript (with the excellent Postgraphile library), and a PostgreSQL database.
Scaledger is designed to be used as a service for recording transactions (called postings) between accounts, and reporting their balances through an entity called ledger. This is particularly useful when you have to track the balances for thousands, or even millions of users. You've taken a payment, but now you've got to keep track of who is owed what? Scaledger is good for that.
The basics are pretty simple, but I've tried to be thoughtful about the kinds of details that most startups get wrong when they're trying to do things like track user balances: using floats for money, making transactions mutable, etc.