pull down to refresh
0 sats \ 0 replies \ @k00b 2h \ on: The tallest building in Cuba Construction_and_Engineering
Where?
They release updates here: https://www.mining.build/
It doesn't look like there have been any product announcements lately.
If you want to be fully self-sovereign, I'd recommend running Start OS on a mini PC and running AlbyHub.
If you want medium self-sovereignty, Alby Cloud will allow you to pay Alby to run a node for you.
If you don't mind storing money with someone else, I'd recommend coinos.
Guides are in the FAQ: https://stacker.news/faq#how-do-i-attach-a-wallet
Do you have to have them on a 24/7/365 server to operate correctly?
To receive 24/7 your wallet needs to be online 24/7.
Would you be able to use up all Cowboy Credits before taking Sats?
That's how it currently works.
Would CCs being given be translated into Sats and sent to the wallet?
CCs do not convert to sats. They're like a gift card that you can't trade-in for money. CCs can only be paid to SN. SN tallies the CCs it earns and chooses to pay the exact same amount out as sats through rewards and territory revenue.
I've been holding off out of fear that it's too much gore and doctor drama, but I like the real time angle.
My aunt is an ER doc and I once asked her what her favorite shift to work is and she said 48 hours continuously lol.
Leading hypothesis is that saunter's attached wallet times out slowly, and because we have network error retry logic on the client, we retry as it times out, then those retries time out, which triggers the retry again, and so on.
I've disabled the retry logic on the client for anything that costs money. We are currently trying to reproduce to confirm this is the exact issue.
If your nostr zaps are not proxied, we don't know if they are paid so we do not produce zap receipts. Do you have the proxy enabled?
When we bought a smoker at costco many years ago, a guy noticed we were having trouble fitting in my car. He offered to load it in his truck and drop it off because he was going the same way. It was so awesome it was scary.
Yep, views and store procedures have to be defined in migrations sadly.
sndev psql can help you inspect stuff pretty well though.stackernews=# \dv
List of relations
Schema | Name | Type | Owner
--------+-----------------------------+------+-------
public | all_days | view | sn
public | all_months | view | sn
public | days | view | sn
public | hot_score_constants | view | sn
public | last_24_hours | view | sn
public | today | view | sn
public | zap_rank_constants | view | sn
public | zap_rank_personal_constants | view | sn
(8 rows)
stackernews=# \dm
List of relations
Schema | Name | Type | Owner
--------+-----------------------------+-------------------+-------
public | all_days | view | sn
public | all_months | view | sn
public | days | view | sn
public | hot_score_constants | view | sn
public | hot_score_view | materialized view | sn
public | item_growth_days | materialized view | sn
public | item_growth_hours | materialized view | sn
public | item_growth_months | materialized view | sn
public | last_24_hours | view | sn
public | reg_growth_days | materialized view | sn
public | reg_growth_hours | materialized view | sn
public | reg_growth_months | materialized view | sn
public | rewards_days | materialized view | sn
public | rewards_today | materialized view | sn
public | sat_rank_tender_view | materialized view | sn
public | sat_rank_wwm_view | materialized view | sn
public | spender_growth_days | materialized view | sn
public | spender_growth_hours | materialized view | sn
public | spender_growth_months | materialized view | sn
public | spending_growth_days | materialized view | sn
public | spending_growth_hours | materialized view | sn
public | spending_growth_months | materialized view | sn
public | stackers_growth_days | materialized view | sn
public | stackers_growth_hours | materialized view | sn
public | stackers_growth_months | materialized view | sn
public | stacking_growth_days | materialized view | sn
public | stacking_growth_hours | materialized view | sn
public | stacking_growth_months | materialized view | sn
public | sub_stats_days | materialized view | sn
public | sub_stats_hours | materialized view | sn
public | sub_stats_months | materialized view | sn
public | today | view | sn
public | user_stats_days | materialized view | sn
public | user_stats_hours | materialized view | sn
public | user_stats_months | materialized view | sn
public | user_values_days | materialized view | sn
public | user_values_today | materialized view | sn
public | zap_rank_constants | view | sn
public | zap_rank_personal_constants | view | sn
public | zap_rank_personal_view | materialized view | sn
public | zap_rank_tender_view | materialized view | sn
public | zap_rank_wwm_view | materialized view | sn
(42 rows)
Then, I'll usually just search in
primsa for them. I'll be going through and deleting some of these unused views soon. I'll create a doc for them all while I'm doing that.