jonnydubowsky

Joined 9 years ago

Karma
390
Submissions
266
Member since
Oct 5
[ my public key: https://keybase.io/jonnydubowsky; my proof: https://keybase.io/jonnydubowsky/sigs/bm6r6rwcPAGAx5i5C02psDa068cpuxddzQpKpOQZjKI ]

Verifying my Blockstack ID is secured with the address 1CShwUu8qJJzEmktUtDQ8Rjn9ss7DU83j https://explorer.blockstack.org/address/1CShwUu8qJJzEmktUtDQ8Rjn9ss7DU83j

View on Hacker News

Recent submissions

Comment · 2 years ago
Comment · 3 years ago
I'm curious as well...are there any protocols in place for emergency services or police interactions?
Comment · 3 years ago
you win the internet today.
Comment · 3 years ago
USDC is now back up from $0.82 to ~ $0.97
Comment · 3 years ago
great landing page! going to try out Abstra cloud right now. I love to see, in one glance, what it does, a gif of it doing it, and the code sample.
Comment · 3 years ago
that took a turn.
Comment · 3 years ago
Recently captured so eloquently in the manifesto from Andor:

There will be times when the struggle seems impossible. I know this already. Alone, unsure, dwarfed by the scale of the enemy

Remember this, Freedom is a pure idea. It occurs spontaneously and without instruction. Random acts of insurrection are occurring constantly throughout the galaxy. There are whole armies, battalions that have no idea that they've already enlisted in the cause.

Remember that the frontier of the Rebellion is everywhere. And even the smallest act of insurrection pushes our lines forward.

And remember this: the Imperial need for control is so desperate because it is so unnatural. Tyranny requires constant effort. It breaks, it leaks. Authority is brittle.

Oppression is the mask of fear. Remember that. And know this, the day will come when all these skirmishes and battles, these moments of defiance will have flooded the banks of the Empires's authority and then there will be one too many.

One single thing will break the siege.

Remember this: Try.

Comment · 4 years ago
Wait this happens to you on Tinder too?
Comment · 4 years ago
Comment · 4 years ago
Us this the beginning of some Back To The Future moment in this timeline?
Comment · 4 years ago
Comment · 4 years ago
Thanks for introducing a new (to me) term, i.e BANANAS. Upon searching i discovered a few others:

NIABY: Opposition to certain developments as inappropriate anywhere in the world is characterised by the acronym NIABY ("Not In Anyone's Backyard"). The building of nuclear power plants, for example, is often subject to NIABY concerns.

NAMBI: ("Not Against My Business or Industry") is used as a label for any business concern that expresses umbrage with actions or policy that threaten that business, whereby they are believed to be complaining about the principle of the action or policy only for their interests alone and not for all similar business concerns who would equally suffer from the actions or policies.

BANANA: is an acronym for "Build Absolutely Nothing Anywhere Near Anything" (or "Anyone").The term is most often used to criticize the ongoing opposition of certain advocacy groups to land development. The apparent opposition of some activists to every instance of proposed development suggests that they seek a complete absence of new growth.

NOPE: (Not On Planet Earth)To leave an uncomfortable situation, usually quickly.

LULU: Locally Unwanted/Undesirable Land Use planning.

NOTE: Not Over There Either (meaning is same NIMBY)

Comment · 4 years ago
The Rarible exchange contract supports all kinds of external royalty interfaces, among them two that Rarible defined themselves, being an early player in the NFT space:

https://hackernoon.com/enabling-nft-royalties-with-eip-2981

ERC721, 1155 & 2981 together act as a toolkit for the encoding of royalty administration.

For example, if an NFT collection owner only implemented one of Rarible’s royalty distribution schemes mentioned above, another marketplace that’s not aware of that interface can simply call the common registry’s getRoyaltyView function. It tries to query all known royalty interfaces on the token contract and translates any response to a commonly useable result.

Collection owners who haven’t put any royalty signaling scheme into their contract can deploy an extended “override” contract and register it with the common registry. This registration method will ensure that only collection owners (identified by the owner public member) can call it

The Rarible exchange contract supports all kinds of external royalty interfaces, among them two that Rarible defined themselves, being an early player in the NFT space:

For example, if an NFT collection owner only implemented one of Rarible’s royalty distribution schemes mentioned above, another marketplace that’s not aware of that interface can simply call the common registry’s getRoyaltyView function. It tries to query all known royalty interfaces on the token contract and translates any response to a commonly useable result.

Collection owners who haven’t put any royalty signaling scheme into their contract can deploy an extended “override” contract and register it with the common registry. This registration method will ensure that only collection owners (identified by the owner public member) can call it

```function royaltyInfo(uint256 _tokenId, uint256 _salePrice) external view returns (address receiver, uint256 royaltyAmount);```

The interface also completely works off-chain, so marketplaces that trade assets on alternative infrastructure can still query the creator fee without knowing anything else besides the interface signature of the EIP-2981 method.

PaymentSplitters: Sending NFT Royalties To More Than One Receiver.

Open Zeppelin's PaymentSplitter primitive allows setting up individual split contracts that keep funds safe until their payees claim them, and their receive function requires the bare minimum of gas to run. NFT collection builders can create an inline PaymentSplitter containing the wanted list of beneficiaries and their respective share amounts and let their EIP-2981 implementation yield the address of that split contract.

Comment · 4 years ago
Great blog post! "Plato didn't write his dialogues on Microsoft Word, and neither should you".
Comment · 4 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton