pull down to refresh
Day 179 of snailposting everyday 'til BTC hits $100k.
__@_'-'
Is your server responding with a Location header?
POST and GET shouldn't matter for redirects using 302 even though GET is recommended.
I've seen HN using redirects after posting a comment.
I'm only posting this reply because I'm starting to deal with business taxes. 1099s for dollar amounts paid over $600.
It's a feed-driven collection of emulators that run in a browser and support cross-device savings thanks to a Dropbox integration. You can create your own game and emulators collections and play literally from everywhere.
I often start playing something on my tvbox, then resume on my tablet or iPhone, and all the saves are automatically syncronized.
I cut the cord.
First I used LNC besides payments failing from time to time it worked great until LNC went down for me for some unknown reason
Then I switched to NWC using alby hub. And it works for the most part but I always get 5 to 10 failed payments it seems like per day or every few days
The auto withdrawal feature worked like a charm. Works great. As someone who doesn’t get a ton of lightning payments it’s often cool to see tiny payments be made to my node.
On one hand I see Darth’s argument but I side with you. What’s the point of LN if a node can’t consistently handle 1 sat payments a few thousand times a day. The more we use it the better we can improve the protocol to meet the needs of the users.
Eating everything but meat. Mostly...
It's been tried a countless times, by myself included... here's some of what I've learned:
ICANN DNS isn't really broken enough and censorship of it is an imaginary problem. If Alex Jones and the State of Iran have functional websites, censorship isn't a valid concern.
Simply because of how the internet is architected, whatever system we try to displace it with still rides on legacy DNS. All we can really do is abstract it which doesn't solve for much.
Usability is an almost impossible problem too because of the above, everything browser related depends on SSL. So now you're not a naming system but inventing a whole new application stack.
Name squatting is a positive market function, and new systems make bad trade-offs trying to prevent it. Squatting must be possible since the point of authoritative namespace is because scarcity, so it must be market liquid.
My next stab at it will be non-authoritative naming from a social graph, where there is no one true "MyCompany dot com" for example, but rather, MyCompany is keyword derived from you and your social graphs address book- that resolves to a public key.
That's the other thing, we don't really need a new name->ip address system, we need human readable names for Public Keys for things like Nostr.
An arbitrary suffix can scope these keywords into contexts (.nostr) for example