pull down to refresh
We operate ~Music from a separate account and a separate wallet. This practice of separating collective activity / finances from that of the individuals - that has been around since before Julius Caesar proclaimed the corporations bill of the Roman Empire into law - makes it a lot easier, because there is no risk of commingling, also not of the accounting.
This month it took me a little over an hour to account the P&L and reconcile with wallets, because I did it 100% manually, including recognition across income sources (fees versus zap apportionment.) I intend to automate this (externally) and if I find any roadblocks, I'll raise an issue on the GitHub repo.
The only feature that would make it easier on the SN side would be account delegation, but note that there's operational risk with that too. For now we've solved it for ~Music with shared credentials, which is anyway happening because I've not seen a good multisig solution for LN yet.
I intend to automate this
FYI, there's snappy. It powers @nitter and @hn. I don't know whether it's going to be useful to you, but I thought I'd let you decide. The README sucks, but so far I have been the only intended user.
Also, since the API changes (which I understand) without announcements (which would be nice), it could be nice to maintain it together.
I think @WeAreAllSatoshi stopped his mining posts because of the required maintenance of his JavaScript code.
lol, just realized my second commit was "god mod init"
Thanks. I have a working but unpublished (because it is sloptained, not maintained) javascript lib. But I promised for this one I'd write it in Python and will publish it.
I can probably get you alerts on API changes; I'd want that for the python implementation anyway (even though it'll be extremely narrow in scope.) Graphql is "self-documenting" so we can just diff json (even on closed source) and for SN we can even ingest commits and be prepared before publish. This in turn we can also automate (I have a framework but I'm not happy with it as-is yet) and have bots trace back to code commits with some minimal cognitive debt by only reading lines that matter to relevant APIs.
I'll look into what it takes to notify downstream public github repos.
If you do this, I'll create an animated meme with you as the main character, similar to the one at #1450231.
Ever since a comment you made about supply chain attacks, I've been depicting you in this Final Destination scene:
(I'll probably create it anyway at some point. I think creating animated memes is one of my callings.)
This video is age-restricted and only available on YouTube.
Since you're apparently logged in to youtube maybe you can run:
yt-dlp --cookies-from-browser <yourbrowsername> -t mp4 -o myvid.mp4 "https://www.youtube.com/watch?v=6HrTgWedKG0"and share it through a non-spooky, non-nazi, non-KYC platform... like... idk... your filesharing vibe thing from the other day? thx ❤️
supply chain attacks
They're real but the bigger threat right now is Claude. I'm down to 9 apps through obtainium and 3 through f-droid, on my insecure day-to-day phone. Soon 8, when I purge amethyst. I have migrated an older version of Amber into a an emulator pending replacement. That's what the world has come to in 2026: "no, i don't trust you, bro".
yes, I just let it stop working after I noticed it wasn’t posting. I probably could have written the code more defensively, but that’s ok
There are a few reasons:
- faster horses were in high demand when automobiles were invented
- custom domains are about growth and growth (having more people posting and discussing stuff) is in high demand
- custom domains are related to downstream work and getting them done will improve that work
- I was supposed to be working on general territory improvements after my payment engine refactor but have had to work on wallets instead
- territory pools are highly interactive/require coordination so it's not as trivial as it seems
I would also like it to be easier to know how much I earned from ~security this month
Ah we do not show monthly revenue in the charts until the calendar month has passed. I agree this would be nice.
I think this has also been requested many times.
It hasn't afaik.
- faster horses were in high demand when automobiles were invented
I figured you'd say that. Is that really relevant here, though? It implies that you think the features I mentioned shouldn't be built.
I think such phrases need to be used in the appropriate context. It makes more sense when asking people on the street what they want, rather than when long-term users are repeatedly requesting a feature in an existing product without being prompted.
- custom domains are related to downstream work and getting them done will improve that work
Ok I did not know about this, thanks
- custom domains are about growth and growth (having more people posting about and discussing stuff) is in high demand
That I can agree with, but isn't growth also about churn? You don't grow if more people are leaving than coming in. I don't know if (enough) stackers are leaving for this to be important, though.
- i was supposed to be working on general territory improvements after my payment engine refactor but have had to work on wallets instead
Yes. I'm basically asking why these general territory improvements, that you would have spent your time on, are less important than custom domains.
- territory pools are highly interactive/require coordination, so it's not as trivial as it seems
Surely easier than trying to use the internet in a way it's fighting you?
Anyway. You don't need to reply to this, I know you're busy. Just wanted to let you know my thoughts
Is that really relevant here, though?
It is. That anecdote reminds us there are different kinds of demand:
- apparent demand
- latent demand
You are asking why we aren't meeting apparent demand. Part of my answer is that we are meeting latent demand at the cost of not meeting apparent demand.
It implies that you think the features I mentioned shouldn't be built.
Taken literally, I can see how that is implied. It's not what I meant.
isn't growth also about churn
It is and churn is about two things:
- retention
- attracting new people
On a relative basis, we are very good at retention and bad at attracting new people. So we should bias toward attracting new people.
Surely easier than trying to use the internet in a way it's fighting you?
I don't understand this one.
Because I wanted to finish what I didn't get to finish last year. /s
I can assure you that custom domains are just one of the many features we have planned for territories. And it's not the only feature currently in development.
I would also like it to be easier to know how much I earned from ~security this month
That's a nice idea and you should feel free to open an issue for it. On the repo topic, while our repository is a great way to track the development of our features, I agree that we should do a better job keeping everyone updated here on Stacker News.
which, afaik, only one person has requested
P.S. We don't base our decision to implement features solely on the number of requests they receive, unless something is critical. We'd like to build what we believe will be most valuable to the community as a whole.
I can assure you that custom domains are just one of the many features we have planned for territories. And it's not the only feature currently in development.
Tbh, this sounds corporate.
We don't base our decision to implement features solely on the number of requests they receive [...] most valuable to the community as a whole.
Are you going to use custom domains? Is @k00b going to use custom domains? Which (existing) members of this community you think are going to use custom domains, such that it's the "most valuable [feature] to the community as a whole"? Or am I misunderstanding how you meant that?
Sorry for this possibly hard question, but I think it's important to ask and think about.
Or am I misunderstanding how you meant that?
I think so. Given the big picture, the things I've shared in my comment, we believe custom domains are one of the most valuable things we can work on for "the community as a whole" because they are upstream of growth.
Which (existing) members of this community you think are going to use custom domains
Custom domains are to a large extent about the opposite: attracting people from outside the existing community.
I intended to use them for ~hyperlinks, for example. It’s a human-curated, constantly updated, list of interesting links. Can't thank everybody enough for their interest!
There's some personal bias in what you think of custom domains, I've always thought that territories could gain more independence, giving them the ability to be a website it's a great first step.
I've always thought that territories could gain more independence,
Same, in a “territories should feel like territories” way, all the way back to when we decided how to even call them, but …
giving them the ability to be a website it's a great first step.
… this sounds more like one of the last steps.
@k00b @sox I have a question: why is @sox working on custom domains, which, afaik, only one person has requested, instead of on territory features that are, afaict, in higher demand? Stackers have been trying to work around the fact that they are missing for quite some time now. For example, ~econ, ~HealthAndFitness, and now ~Music are managed by multiple stackers.
I have started to think about a co-founder for ~security, too. I would also like it to be easier to know how much I earned from ~security this month, so I know how much I am still paying for it myself. I think this has also been requested many times. Satistics have improved, yes, but I don’t see how they can answer this question.