HN user

jekrb

256 karma
Posts7
Comments98
View on HN

Libra/Diem was told by regulators to not move forward with the project. They were very early days, and trying to "do it right" in which the administration said "not at all".

Similar also happened with Visa... check when they were publishing in-depth reports from their crypto arm and then suddenly stopped.

What is to stop centralized blockchains from incremently increasing fees to the level of CCs over time?

Then users will just go to a different chain that provides a better outcome.

theres no reason a bank couldn't take a stablecoin deposit and fractionally lend against it

thats effectively what already happens with their own internal ledgers anyways

the excuse is actually the other way around i think

banks are an excuse to have closed source ledgers that don't operate efficiently for internet capital markets

if they wanted to, they could open source their ledgers and let anyone make them faster, more interoperable, more programmable, etc.

stablecoins operate on infra that is more like linux for finance, anyone can contribute to blockchain rails and even run their own nodes

What if the work these folks do to increase market efficiency does produce real-world value, as slower verifiable economic information would increase periods of uncertainty and price slippages?

Or the HFT engineers producing research and products that speed up general compute, such as accelerating SHA and ED25519 signature verification, so that their trading shops get information faster?

I wonder if there are actually a lot of third-order, downstream effects that society gets by paying engineers to just make computers and telecommunications faster.

I think everyone will have different behavior sec for their funds, with the options now ranging from simply committing a 12 or 24 word seed phrase to memory and buying ETF shares.

There is shamir secret splitting, multisig, MPC, secure enclaves with biometerics, etc...

There will be apps like Fuse wallet: https://www.fusewallet.com/

There will be phones like Saga: https://solanamobile.com/hardware

I think how one handles their wallets will be much like how people make their espressos. Some will just stick k-cup in a machine and hit a button, others will become full-blown coffee enthusiasts that carefully measure their beans, de-static their grinds, and extract for the exact right amount of time.

This should actually be quicker and easier to prove than something like gold ETFs (e.g. SPDR) or other commodity ETFs.

The custody provider (e.g. Coinbase is the custody provider for most of these ETFs) should be able to simply show wallet addresses for all the Bitcoin they hold.

Two reasons.

1. Low fees. I think five of the ETF filers even have 0% fees for first 6-12 months. Compare this to Coinbase, where the fees will seem astronomical in comparison (maybe this drives Coinbase fees down.)

2. There is a non-zero number of people in the family office investing world that don't want to deal with learning new tech and just want to call up their stock person on the phone to buy them something.

One I didn't see the other's mention is that in Line Goes Up, Dan calls secure-scuttlebutt (SSB), a p2p messaging protocol, a blockchain.

IIRC Dan was relying on a sentence from an outdated, archived documentation site made by an open source contributor many years ago. The core SSB devs then had to try to convince people that Dan was wrong about their project. Dan refused to admit he was wrong, despite a lack of blockchain in the open source code, and just pasted a screenshot of the old docs.

Well yeah this is how he gets paid. It's not about being informative about a class of technology, its about generating clicks to get more patreon subscriptions and youtube ad payments.

For me it was less the commute time and more planning around traffic.

Even if the commute was 30 minutes (a good day), I'd usually need to buffer time to plan for being late due to traffic accidents and construction (frequent).

Switching to remote work gave me back at least an hour every morning, and at least 1.5 hours in the evening. Anecdotally this has led to massive performance and quality of life increases.

This takes me back to how we used to write JavaScript on websites for towns/cities at a company I used to work at.

Really a joy to read.

The lack of multi-device support was a constraint that gave me a different perspective of interactions on the web.

My ssb keypair was on a work laptop, so when I changed jobs and had to give my laptop back, I lost my keypair. Now, I could have exported the keypair and continued to use my "account" on my new laptop. The network would have synced on my new device, and I'd get all my posts and pictures back. But decided to embrace the constraint instead.

When I rejoin the network, I'll have a new keypair, and no post history. I think this can have an interesting effect on how we view our attachment to data.

It's been a while, but I used to be an active SSB user.

I hosted SSB pubs and used to post on patchwork semi-regularly.

I thought it worked pretty well as a social network. I discovered new and interesting ideas from folks that I don't see much on mainstream social media.

I haven't followed the space much recently, and I'm curious about how it has evolved over the last year or so.

My favorite memories on SSB:

Someone promoted a book that they had written, and we arranged for a sales transaction by talking purely over the network. I sent them some amount of Bitcoin, and they sent me the PDF of their book. It felt very personal to work with the author directly, and side-step payment processors.

I loved taking my laptop out on the train or to a coffee shop, and replying to threads and publishing a post to SSB while offline. Something about reading other peoples ideas while disconnected, and then writing my thoughts, and having them automatically sync to the network when I got back on my WiFi at home, gave me a different perspective on ways to use technology.

At the agency I used to work for, we used GitLab CI/CD.

We were able to do a manual rollback for each deployment from the GitLab UI.

https://docs.gitlab.com/ee/ci/environments.html#retrying-and...

Disclaimer: I work at GitLab now, but my old agency was also using GitLab and their CI/CD offering for client projects for a couple years while I was there.

At that agency they have even open sourced their GitLab CI configs :) https://gitlab.com/digitalsurgeons/gitlab-ci-configs

I used to work for a company that rented a WeWork space to meet with clients in NYC. I only opted to work out of it once or twice, for a change of scenery from my typical office. I think the location was the main perk, since I then got to spend a day in NYC.

Working fully remote now and I enjoy that much more than being in any office setting.

Digital Surgeons | New Haven, Connecticut | Web Developer | ONSITE

Job description:

- Your projects will range from architecting and engineering CMS websites, web apps, platform integrations, internal tools, DS branded products, and other technical problem solving designed to build the bridge between brands and consumers.

- Collaborating with designers, strategists, creative thinkers and technologists to architect and execute forward thinking applications, campaigns and websites.

- Building intuitive content management systems and administration areas.

- Crafting creative and intricate user interfaces and experiences. Helping to perfect our ever-growing infrastructure and internal tools to maximize output.

- Contributing to and releasing open source tools and libraries that DS and the wider community can benefit from.

Link to job posting: https://www.digitalsurgeons.com/careers/web-developer/

Have you tried Brave browser on mobile? It's quite fast and blocks ads.

A couple issues with Safari I've seen since it's slower to adopt web standards:

- buggier websites from devs who don't have iPhones. Since there are some quirky inconsistencies with how webkit handles css vs other browser rendering engines it's easy not to catch those quirks if you don't have an iPhone to check them with. And once users point them out, it's a pain to fix without a physical device.

- a smaller web feature set than chrome/Firefox. For instance, Safari doesn't allow localstorage while in incognito. I think it supports serviceworkers and webrtc now but it took years to get them.