pull down to refresh
662 sats \ 1 reply \ @Alby 25 Feb \ parent \ on: Stacker Saloon
PS here you can see our outages:
https://alby.instatus.com/
When I first read her I found a class she taught on money, which at the time I was incredibly annoyed that I couldn't take myself -- the readings / syllabus looked so interesting. I can't seem to find it now, but here's a recent one.
Looks like she's working on a new book, The Money of the Poor. Here's a podcast I found where she discusses it. I haven't listened yet, but will do.
Lots of cool stuff on her website. Seems like an eclectic thinker.
There is, but we stopped authenticating with LNDhub accounts, prioritizing using users own keys, without our knowledge.
Ie. you are not signing with Alby Account anymore, but with your keys stored in the extension.
@jinformatique1 but your previous auth is not lost. We've described the migration here: https://guides.getalby.com/user-guide/v/alby-account-and-browser-extension/alby-browser-extension/faqs-alby-extension/migrate-from-old-lndhub-setup
Please e-mail support@getalby.com, we will help you out!
Sorry for the confusion, it's for the good of all of you ;)
Hey @k00b,
I just heard KR is stepping away from SN. I don't know what his exact functions with SN were but just throwing it out there that if you need help with any non technical related things I am available to lend a hand.
Back in October, I suggested generalizing these kinds of threads into a protocol implemented via some kind of standard implemented via serverless code deployed to AWS or GCP.
Users could register these endpoints with the site, then select them from a drop down.
The endpoint would just need to take context in a standard form and return who got what sats. The site could expose these results for analysis to the community.
Those logs would show who's voting for what and how much they spend. And the responses could be analyzed as well.
Super simple example...
Request:
{ 'user' : @jeff, 'vote_sats' : 30, 'post_id' : 20807}Response:
{ 'recipients' : [[15, @DarthCoin], [10, @k00b], [5, @SomeCharity]] }It gets waaaaay cooler, the more context SN could inject into the request. (Eg. current vote count, total sats voted, current comment count, trust score? content URL? Age of post? Age of voter? Age of OP?)
would you roll back the functionality
No, not at all.
But if you really think about it; if you want to see ~econ in your feed, does the tag on the content really help that much? You're just gonna see the title of the post, and be like "Oh, cool...maybe I read this". It doesn't likely change the outcome of what you read. So, the tag, really only helps the people who don't want to see the territory content OR I suppose, people who want EXCLUSIVELY that territory's content. Which, is probably a rare way to browse SN.
curious to know what other cool tools
WAAAAY more control over zap flow
Stay with me here, the first sentence in the next paragraph is going to be jarring. But, if you think about it for a split second, my suggestion is step towards less centralization. As it stands right now, SN has a claim on 100% of zaps, and they've decided subjectively to set the split at 90-10 universally, and we trust them to forward it on according to those terms. But I see this like a centralized federal government declaring numbers for states. It works for some, but not others.
Territory owners should get a claim on 100% of the sats from any post and any comment in the territory. Then, the territory owner(s) should get to set a call-back URL, which is hit for every post, comment, and zap event, which gets the full context of the event, and then returns an object which represents the weights of where any zaps should go for that event. A protocol.
The territory owners would be able to set logic such as:
- Posters get 50% of the first 1000 sats, territory gets the other 50%, but poster gets 99% of anything higher, territory keeps the 1%.
- 13th day of the month, all zaps go to charity.
- Posters who are in the top ten, get 95% of zaps, else, you get 80%, balance goes to territory.
- Territory treasury gets 5% of all zaps. Territory can do their own games with this pile.
- Split revenue for 15 days across these specific names proportional to specific weights.
- A dice-roll on every zap, determines the split.
This 90-10 split is a subjective constant chosen by SN, which makes for a market-clearing number under certain conditions. If I had made 200K sats from the 10% rake, I'm 10000% sure, that I would lower the split cause if I didn't, ~econ2 would pop up. Conversely, it makes no sense to spend 100K to get 5K in "revenue". SN needs to 20x before we're looking anywhere near breaking event at the 100K.
Data
Just, lots more info about whats going on in the territory.
Tagging + API
Would like to be able to add value, by auto-tagging, programmatically, via after-the fact API.