Less information loss -> Less params? Please correct me if I got this wrong. The Intro claims:
"The dot product itself is a geometrically impoverished measure, primarily capturing alignment while conflating magnitude with direction and often
obscuring more complex structural and spatial relationships [10, 11, 4, 61, 17]. Furthermore, the way current activation functions achieve non-linearity can exacerbate this issue. For instance, ReLU (f (x) = max(0, x)) maps all negative pre-activations, which can signify a spectrum of relationships from weak dissimilarity to strong anti-alignment, to a single zero output. This thresholding, while promoting sparsity, means the network treats diverse inputs as uniformly orthogonal or linearly independent for onward signal propagation. Such a coarse-graining of geometric relationships leads to a tangible loss of information regarding the degree and nature of anti-alignment or other neg-
ative linear dependencies. This information loss, coupled with the inherent limitations of the dot product, highlights a fundamental challenge."
yes,
since you can learn to represent the same problem with less amount of params,
however most of the architectures are optimized for the linear product, so we gotta figure out a new architecture for it
Lots of people who have relatively stable currencies (EUR, USD..) do not want to use bitcoin. What if bitcoin price goes down? How many extra steps is it to convert my USD to bitcoin and then back to USD? Do I only convert the 19.99 USD for my current purchase into bitcoin or do I put in more?
Do you solve these issues for customers? Or are you only targeting people who already are happy bitcoin wallet users? Are stablecoins part of your strategy?
Given how Visa,Mastercard,Paypal are seen as bad actors. Do you think you can capitalize on that, possibly partnering with Valve or something of that sort?
We as MoneyBadger create an invoice for the customer in their local currency e.g. USD. If they pay with Bitcoin Lightning, they have 3 minutes to complete the transaction at our offered exchange rate. We take on the risk of the price moving.
If they’re paying with one of the exchange wallets we support like Luno.com, VALR.com or Binance.com we do the same, and they can choose to pay with any currency supported by those wallets.
Refunds are processed at time of refund and are for the original amount in the currency of the invoice e.g. USD but at the exchange rate at the time of refunds.
It really all just works the same as paying with a credit card overseas would if you’re paying a EUR bill with USD funds.
At first I thought you made a website that gives me an empty Markdown file. But I am glad I downloaded it its actually a pretty nice template.
What are you personally doing with the yearly goals in that file. Are you copy and pasting them from last week, or are you typing them down everytime to re-iterate them (and possibly even modify) ?
Yeah, currently I am just copy/pasting the Yearly Goals section over. I want to eventually add a feature to allow someone signed up for the email to edit that part. Then someone could modify that goal section and have it correctly emailed each week.
Mercury sounds interesting. Requires a certain scale though (gravity is a bitch).
Considering just the initial mining and construction, bodies with low gravity and proximity to the earth feel like an efficient starting point, right? I always thought the moon would be a good place to bootstrap the first few thousand space habitats.
Your point about energy will probably be the biggest deal. Wondering how complicated it would be to ship a bunch of nuclear reactors to the moon. There seems to be quite a few companies working on small, "mass produced" reactors currently.
Added an opt-out for the navigational copilot on Mac -- just bring up the command pallet (CMD+SHIFT+P) and use the "Opt out of navigational copilot" command. Coming to Windows/Linux soon!
Note that we only send data to Open AI if you have a diagnostic indicating that you're calling a function that doesn't exist.
I also just used ElasticMQ in a docker environment. Did you see any specific downsides, when you looked at it? In which scenarios should I consider replacing it with your solution?
"The dot product itself is a geometrically impoverished measure, primarily capturing alignment while conflating magnitude with direction and often obscuring more complex structural and spatial relationships [10, 11, 4, 61, 17]. Furthermore, the way current activation functions achieve non-linearity can exacerbate this issue. For instance, ReLU (f (x) = max(0, x)) maps all negative pre-activations, which can signify a spectrum of relationships from weak dissimilarity to strong anti-alignment, to a single zero output. This thresholding, while promoting sparsity, means the network treats diverse inputs as uniformly orthogonal or linearly independent for onward signal propagation. Such a coarse-graining of geometric relationships leads to a tangible loss of information regarding the degree and nature of anti-alignment or other neg- ative linear dependencies. This information loss, coupled with the inherent limitations of the dot product, highlights a fundamental challenge."