layout: post title: "Residential VoIP in Canada: Not looking so good" created: 1087203003 categories:
Brad’s talking about Primus Talkbroadband and how their entire network recently went down, and how this reflects on them:
When your entire VoIP network crashes you prove a number of things:
You must have a single point of failure, which means that somebody in your organization doesn’t get that whole "up-time and reliability" thing.
You should not be charging anything like the price you are charging for the service, given that you have demonstrated a lack of interest in investing in reliability (ie: re-read the first point).
You have power washed any good will or early adopter enthusiasm out of the product.
This does not yet seem to be a good business proposition for an investor or a prospective customer.
Brad Gibson’s Current Thinking: What happens when the Category Killer Dies?
After the network problem and some further thinking, I might be just about ready to stop using Primus for now. I’ll tell you why:
I’m glad I experimented, and I’ll likely keep trying out different options, but I don’t think Primus meets my needs as a reliable provider of primary line services. For now, two cellphones is going to be the answer.
A : [[podcast]]
URL : https://shows.acast.com/reasonstobecheerful/episodes/episode42.techforgood
Series : [[Reasons to be Cheerful]]
~00:09:43 Digital revolution has to be combined with democratic revolution
~00:15:25 [[Data commons]]
~00:15:50 [[Participatory democracy]] rather than just consultation
~00:19:52 [[Community mesh networks]] in [[Red Hook, Brooklyn]] and in Detroit
~00:22:26 Mesh was only network that worked in Red Hook during [[Hurricane Sandy]].
~00:23:01 Red Hook mesh works in emergency and to help those who have no connection otherwise
~00:36:30 [[Connectivity]] is fundamental to human life these days
~00:37:22 The deep value of something like WiFi is in empowering people (same true of repair cafes?)
~00:40:32 [[Bristol Approach]], damp sensing
These are general notes about #do-good
[[onshore wind]] is good.
Once an onshore windfarm has secured a contract to supply energy, it can be fully operational within about two years, compared with four or five for offshore projects, according to the trade body RenewableUK.
Electricity from onshore wind is also about 20% cheaper than offshore, which is in turn cheaper than nuclear or gas.
โ PM to put nuclear power at heart of UKโs energy strategy | Energy | The Guardian
Discuss and Connect
Working out howย you should help is worth puzzling over. Join some EA Groups.
Engage in CTZN’s EA group!
Talk about the change you wish to see in the world, and the roadblocks you hit in making that happen. Reward someone for doing good.
Build lists of useful people, organizations, and resources
Identify impressive math students or graduates
[2019-07-21] hacked seaborn to display vs on pairplots
[2019-07-21] hacked seaborn to display vs on pairplotsยงused inspect to extract directly from local variables, lol
https://github.com/mwaskom/seaborn/blob/master/seaborn/axisgrid.py#L1340-L1341
I’ve had nondeterministic behaviour due to random seed
was not propagated, but with a patch it’s possible to achieve
# TODO careful.. need to do this ONCE
bootstrap_orig = sns.algorithms.bootstrap
def bootstrap_hacked(*args, **kwargs):
return bootstrap_orig(*args, random_seed=0, **kwargs)
sns.algorithms.bootstrap = bootstrap_hacked
https://github.com/mwaskom/seaborn/issues/1924
logging.basicConfig(
format='%(asctime)s %(levelname)-8s %(message)s',
level=logging.INFO,
datefmt='%Y-%m-%d %H:%M:%S')
However if you are a well-mannered person, you don’t want to mess with other loggers and you’re probably providing your own logger method
This is a bit horrible
https://stackoverflow.com/a/28330410/706389
For my personal projects I’m using logzero which has got a single line setup method. However, for code I’m sharing with other people I prefer to have as little external dependencies as you can
e.g. libraries should never configure logging
https://www.reddit.com/r/learnpython/comments/69grzn/logging_confuses_me/dh6ngvo/
[2019-09-17] could publish in r/python?ยง[2019-09-17] sometimes it makes sense for your library to configure other loggers (e.g. requests)ยงseparating network retrieval and storing in database. with generators can do it simultaneously
mts = int(r.timestamp)
if newest is not None and oldest is not None and newest > mts > oldest:
logger.info('Fetched everything for %s', thread.name)
break # interrupt, thus interrupting fetching data
db.insert_message(thread, r)
import ast
import traceback
import inspect
src = ast.parse(open(__file__).read())
def find_name(lno: int):
# TODO end_lineno is not set??
node = None
for x in src.body:
if x.lineno >= lno:
break
node = x
[tg] = node.targets
return tg.id
class Namer:
@property
def auto(self) -> str:
stack = inspect.stack()
fr = stack[1]
lno = fr.lineno
return find_name(lno)
N = Namer()
aaaa = (
1,
N.auto,
)
bbbb = (
2,
N.auto,
)
print(aaaa)
print(bbbb)
generators, decorators and random dynamic things with examples