Hi everyone,
After I asked our insurance agent why our property insurance will be
going up $800 this year, she sent the following reply from the company:
/On a side note, it appears the condition of this building has
drastically deteriorated over the years. The current condition of the
building is below average and is unacceptable. We will remain on this
account for one more year but please be advised that we will be setting
this account up for nonrenewal. If the insured is able to provide proof
of building updates and proper maintenance, we may be able to review
this account again for eligibility. In additional, updates would allow
us to approach other carriers for alternate quotes./
*If we lose our property insurance and are unable to find another
company (unlikely and, if we can, the rate will be high), we will
probably not be able to refinance and we will lose the building. *
**
Our agent thinks they are basing their evaluation of the building
condition only upon seeing the exterior, possibly on google street view.
That is why they have asked to do the inspection that I have already
told you about. I think that will happen on Thursday 2/13
We need all hands on deck over the next 2 weeks to make the building
look as good as possible, inside and out. That means:
- fire safety equipment all in working order, NO clutter, no fire hazards
- condition of any wiring as good as possible
- exterior condition as good as possible, no graffiti, clean, EH windows
fixed and window sills repaired and painted, new awning up
- any roof trouble spots fixed
- general interior condition should look as good and safe as possible,
general painting where needed, everything clean and in working order
- fixing anything that could be seen as a safety hazard.
I propose an emergency meeting tomorrow evening at 7pm to get organized
to tackle these things.
Laura
We then translated the aligned genome and found that these inserts are present
in all Wuhan 2019-nCoV viruses except the 2019-nCoV virus of Bat as a host
[Fig.S4]. Intrigued by the 4 highly conserved inserts unique to 2019-nCoV we
wanted to understand their origin. For this purpose, we used the 2019-nCoV
local alignment with each insert as query against all virus genomes and
considered hits with 100% sequence coverage.
Surprisingly, each of the four inserts aligned with short segments of the Human
Immunodeficiency Virus-1 (HIV-1) proteins. The amino acid positions of the
inserts in 2019-nCoV and the corresponding residues in HIV-1 gp120 and HIV-1
Gag are shown in Table 1. The first 3 inserts (insert 1,2 and 3) aligned to
short segments of amino acid residues in HIV-1 gp120. The insert 4 aligned to
HIV-1 Gag. The insert 1 (6 amino acid residues) and insert 2 (6 amino acid
residues) in the spike glycoprotein of 2019-nCoV are 100% identical to the
residues mapped to HIV-1 gp120. The insert 3 (12 amino acid residues) in 2019-
nCoV maps to HIV-1 gp120 with gaps [see Table 1]. The insert 4 (8 amino acid
residues) maps to HIV-1 Gag with gaps.
Although, the 4 inserts represent discontiguous short stretches of amino acids
in spike glycoprotein of 2019-nCoV, the fact that all three of them share amino
acid identity or similarity with HIV-1 gp120 and HIV-1 Gag (among all annotated
virus proteins) suggests that this is not a random fortuitous finding. In other
words, one may sporadically expect a fortuitous match for a stretch of 6-12
contiguous amino acid residues in an unrelated protein. However, it is
unlikely that all 4 inserts in the 2019-nCoV spike glycoprotein fortuitously
match with 2 key structural proteins of an unrelated virus (HIV-1).
https://www.biorxiv.org/content/10.1101/2020.01.30.927871v1.full.pdf
Omni door electronic latch is not letting people in, building is locked and
people are
trying to get in for a class
can someone with a key go there and let them in?
-jake
I'm calling it! Hope to see you all there! Some items to discuss:
* cleaning for insurance inspection (urgent)
* omni meetings (someone should go)
* money (not enough)
* new members (people waiting)
* key card list (needs pruning)
* big projects (kitchenette? epoxy floor?? pallet racks??)
* planting trees in the floor (not urgent)
* breeding mouse-cockroach hybrids & putting them in charge
* techno-pessimism support group
Hello,
I just wanted to find if the software Thursday night events were going on
currently or any other frequent opportunities to get involved beyond the
Tuesday Hardware nights?
Thanks,
Zac
---------- Forwarded message ---------
From: Yardena Cohen <yardenack(a)gmail.com>
Date: Mon, Jan 27, 2020 at 3:45 PM
Subject: Re: [sudo-info] Getting started
To: Zac R <zrobin16(a)gmail.com>
Hi Zac, right now the best time to meet others at Sudo is Tuesday
night hardware hack night. It seems to be the only regularly occurring
event right now. If you want to find people to talk about software,
you might try the sudo-discuss mailing list.
there's a payphone mounted on the front of Omni, by the front door.
When we installed it, it was working and when you would lift the receiver, it
would connect to the asterisk server in the rack, and say "Press 1 to connect
to Sudoroom, press 2 to connect to Counter Culture Labs..."
and there were VOIP phones in CCL and sudoroom that would ring when it was
used.... I wanted to set it up so the phones could beep the door open while
someone was on the line.
Presently the receiver on the payphone is broken, but we have a replacement. I
am willing to repair the phone and get the system back up and running, if
someone with software skills is interested in helping tune up the asterisk
server and configure the phones indoors.
We also need to clean the graffiti off of the phone. This needs to happen ASAP
as there will be a building inspection by the insurance company and we need the
outdoors to look good.
The alternative is to remove the payphone and maybe "someday" put it back but
that would be a step back.
Is anyone interested in collaborating on this? Obviously the priority is to
clean the appearance of the phone and replace the handset, so that it doesn't
detract from the appearance of the building.
-jake
FYI - it would be great to have a new sudo room delegate! Anyone interested?
An overview of what's entailed: https://sudoroom.org/wiki/Omni_Delegate
In the past, sudo room has stepped up when the larger Omni collective has
lost its path, so to speak, toward stewarding an actual commons - wherein
decisions are made collectively, and delegates are actually delegate
representatives in a spokescouncil.
Omni is slipping, and at the risk of a community group that is intimately
tied with our very foundations. Please step up - we need all sorts of help
right now:
- Noise complaints and issues with the building manager across the way on
48th
- Property insurance may pull out of insuring us given dilapidated state of
building
- Dilapidated state of building, general
- Desperate need for funding / support for refinance before our mortage
balloon payment in Jan 2022
- Upcoming fire inspection (Feb/March), property insurance inspection
(2/13), and property tax exemption (county) inspection (Feb)
- Upcoming property tax exemption app annual filing (massive amounts of
work)
- Stalled kitchen renovation (not enough funds)
Reply here to this thread, talk with people, join an upcoming meeting or
work party, or reach out privately if you'd like to help!
Love and solidarity,
Jenny
---------- Forwarded message ---------
From: Jenny Ryan <jenny(a)jennyryan.net>
Date: Wed, Jan 29, 2020 at 11:00 PM
Subject: Re: [omni-discuss] Late night basement events
To: Laura Turiano <scylla(a)riseup.net>
Cc: commons <commons(a)lists.omnicommons.org>, discuss <
discuss(a)lists.omnicommons.org>, <consensus(a)lists.omnicommons.org>
There are significant problems with this "decision," and since it did not
acquire consensus in actuality (I blocked as remote sudo room delegate on
the pad), I must speak up to revert this statement.
Apologies, Laura, as I know very well how much effort you've put into this
issue and attempting to resolve it.
A) This proposal was never submitted to the Delegate's List a week prior to
its decision-making process, as is protocol, but rather brought up suddenly
at a Delegate's Meeting amidst a haze of elicited fear, uncertainty, and
distrust by less-than-informed community members.
B) All proposals must be submitted to consensus at least a week prior to
being consensed upon, so that delegates have time to confer with their
collectives. Just a friendly reminder: we are a collective of collectives
experimenting with radical participatory democracy - not a standard
nonprofit board in which representatives make uninformed decisions on
behalf of uninformed groups.
C) Not one of the basement events actually run by SPAZ has elicited any
noise complaints - specifically, the events that have elicited noise
complaints were SKAST (third-party, midsummer), Putivuelta (third-party,
December) and FYE (December, and somehow exempt from this decision?).
I am not trying to come at anyone - just merely clarifying the actual facts
of the matter.
Given that none of our actual processes for decision-making and
self-governance were employed, this decision is, imho, moot. Nevertheless,
SPAZ decided to hold off on any upcoming events (to the detriment of their
own expenses for storage and equipment maintenance, despite events still
being approved such as FYE's late-night event that will utilize SPAZ
soundsystem on Friday), I call a hard block and look forward to having
actual discussions with our respective collectives and seeing you all at
the next delegate's meeting on Thursday to clear up the very many
miscommunications clearly at play here. It is also likely that SPAZ will be
ready to submit their membership application at this meeting - I will
submit it on their behalf in advance of the meeting. Because that is, in
fact, how we operate.
Love and solidarity,
On Fri, Jan 17, 2020 at 5:28 PM Laura Turiano <scylla(a)riseup.net> wrote:
> I want to let everyone know who wasn’t at the delegates meeting last night
> about a decision that was made.
>
> Due to neighbor complaints and ongoing conflicts about use of the basement
> for late night events, the delegates unanimously decided to not allow late
> night events by anyone other than member collectives. Once a protocol for
> such events is approved and other conflicts are resolved they will consider
> allowing outside group events again.
>
> Member collectives having late night events need to coordinate w the
> commons wg to ensure there are no further complaints.
>
>
> Laura
>
>
> Sent from my iPhone
> _______________________________________________
> discuss mailing list
> discuss(a)lists.omnicommons.org
> https://omnicommons.org/lists/listinfo/discuss
>
Hey all,
First off I wanted to apologize to Rayc, Sierk, Louis, and Jenny for acting
out too much of my frustration in sudo earlier tonight. I was being
sensitive about the state of the space and should have been more thoughtful
in responding instead of reacting!
Wanted to clarify that Ian gave me a call back and we are going to work
together tomorrow night at the hardware hack night to sort out the pile of
PC equipment that is in the entrance of the space. The plan is to dismantle
the pile and redistribute the pieces appropriately as soon as possible,
with an ultimate deadline of next Monday.
I'll be helping to do a run to Tech Exchange both for donations and for
e-waste recycling.
Take care all,
Matt
Dear Sudo Room,
Here's your invoice! We appreciate your prompt payment.
Thank you for stewarding the commons.
Love and solidarity,
Omni Commons
------------------------ Pledge Summary --------------------------
Invoice # : 2006
Invoice Date: 02/01/2020
Due Date: 02/25/2020
Terms: Net 25
Amount Due: $4,000.00
The complete version has been provided as an attachment to this email.
---------------------------------------------------------------------
