Things will change forever, nods ex-Facebooker Alex Stamos

Video conferencing software biz Zoom has bought Keybase in a surprise move just weeks after hiring Facebook's one-time CSO.…

Seizures often herald the clinical appearance of gliomas or appear at later stages. Dissecting their precise evolution and cellular pathogenesis in brain malignancies could inform the development of staged therapies for these highly pharmaco-resistant epilepsies. Studies in immunodeficient xenograft models have identified local interneuron loss and excess glial glutamate release as chief contributors to network disinhibition, but how hyperexcitability in the peritumoral microenvironment evolves in an immunocompetent brain is unclear. We generated gliomas in WT mice via in utero deletion of key tumor suppressor genes and serially monitored cortical epileptogenesis during tumor infiltration with in vivo electrophysiology and GCAMP7 calcium imaging, revealing a reproducible progression from hyperexcitability to convulsive seizures. Long before seizures, coincident with loss of inhibitory cells and their protective scaffolding, gain of glial glutamate antiporter xCT expression, and reactive astrocytosis, we detected local Iba1+ microglial inflammation that intensified and later extended far beyond tumor boundaries. Hitherto unrecognized episodes of cortical spreading depolarization that arose frequently from the peritumoral region may provide a mechanism for transient neurological deficits. Early blockade of glial xCT activity inhibited later seizures, and genomic reduction of host brain excitability by deleting MapT suppressed molecular markers of epileptogenesis and seizures. Our studies confirmed xenograft tumor–driven pathobiology and revealed early and late components of tumor-related epileptogenesis in a genetically tractable, immunocompetent mouse model of glioma, allowing the complex dissection of tumor versus host pathogenic seizure mechanisms.

The Label's "The_Otherside" is this week's addition to Apple Arcade on the iPhone, iPad, and Apple TV. The game is described as both a turn-based RPG and a strategy board game:

Otherside is a turn based RPG and strategy board game where you will control four survivors who hope to push back the shadowy threat. Make your way through each level solving puzzles, fighting monsters, and destroying the spirit anchors that threaten our dimension.

Do you have what it takes to restore the town back to normal and save the day?

Apple recently updated the 13-inch MacBook Pro, and the $1,299 base model remains a popular alternative to the $999 MacBook Air. To help with your buying decision, read our comparison of the notebooks below.


The differences between the base 13-inch MacBook Pro and the MacBook Air are quite nuanced, with each notebook possessing some unique features.

What's the Same

• 13-inch Retina display with 227 pixels per inch and True Tone support


• Magic Keyboard with reliable scissor switch design


• Force Touch trackpad


• 2 × Thunderbolt 3 ports


• 3.5mm headphone jack


• 256GB of SSD storage standard, configurable up to 2TB


• Touch ID


• T2 security chip


• 720p webcam


• 802.11ac Wi-Fi, also known as Wi-Fi 5


• Bluetooth 5.0


• Three-microphone array with directional beamforming


• Dolby Atmos surround sound

Advantages of Base 13-Inch MacBook Pro

• The display supports the P3 wide color gamut for more vibrant and lifelike colors


• The display is brighter at up to 500 nits vs. 400 nits on MacBook Air


• Touch Bar


• Slightly better sounding speakers

Advantages of MacBook Air

• Up to 11 hours of battery life vs. 10 hours on base 13-inch MacBook Pro


• Weighs slightly less at 2.8 pounds vs. 3.1 pounds for base 13-inch MacBook Pro


• Faster RAM: 3733MHz LPDDR4X vs. 2133MHz LPDDR3 for base 13-inch MacBook Pro


• 6K display support vs. 5K on base 13-inch MacBook Pro

Performance

• MacBook Air / 1.1GHz dual-core Core i3: 1,002 single-core and 1,998 multi-core


• MacBook Air / 1.1GHz quad-core Core i5: 1,055 single-core and 2,645 multi-core


• MacBook Air / 1.2GHz quad-core Core i7: 1,102 single-core and 2,843 multi-core


• MacBook Pro / 1.4GHz quad-core Core i5: 927 single-core and 3,822 multi-core


• MacBook Pro / 1.7GHz quad-core Core i7: 1,036 single-core and 3,909 multi-core

• The base model 13-inch MacBook Pro for $1,299 has up to 91 percent faster multi-core performance than the base model MacBook Air for $999


• If considering the MacBook Air, upgrading to the quad-core Core i5 option is well worth the extra $100, as it is up to 32 percent faster than the base model and more closely rivals the base 13-inch MacBook Pro

Bottom Line

While the pandemic has been chipping away at the furry convention scene, other furs have stepped forward to try and give those in the community events to look forward to over the now dormant weekends. This had started with a group of Furnal Equinox members creating a digital replacement for their late March convention called Keep Calm and Carry Con - Furnal Isolation. More have started to spring up this spring.

They can have internet dealers dens, streaming dance competitions, and other staples that conventions are known for. Accessible from the safety of your own home.

Below is a comprehensive list of conventions. Last updated May 2nd, 2020 12:18 ET.

Please feel free to place any not listed here in the comments below and we will look into adding it if it appears legitimate.

read more

PSA Peugeot Citroën and IBM today announced a partnership to help various industries within the Internet of Things economy to analyze data to deliver new services from connected vehicles.

Today IBM and Eurobank announced the first cloud-based digital platform for online international commercial trading. Using IBM's industry-leading Digital Experience software, with advanced cloud capabilities and social offerings, Eurobank is uniting exporters and importers from around the globe to enhance international trade operations and increase transactions.

Bank of Montreal (BMO), CaixaBank, Commerzbank and Erste Group have joined an initiative launched by UBS and IBM in 2016 to build a new global trade platform based on blockchain technology. This new platform, called Batavia, is built to be openly accessed by organisations of all sizes anywhere in the world, and can support trade finance for transactions across all modes of trade, whether goods are being transported by air, land or sea.

ANZ, Commonwealth Bank, IBM Scentre Group and Westpac have jointly launched a live pilot for Lygon, a new digital platform using blockchain technology to transform the way businesses obtain and manage bank guarantees that are often required as part of a retail property lease.

It may be tempting at the start of a new project to create the first database tables manually, or write SQL scripts that you run manually, especially when you first have to spend a significant amount of time on sifting through all the migration libraries and then some more to get it working properly.

Going through this process did slow me down at the start of the project but I was determined to use a migration tool because hunting inexplicable bugs that only happen in production just to find out there is a definition mismatch between the production and development databases is not fun. Using such a tool also motivates you to write both the setup and teardown steps for each table while the current design is still fresh in your mind.

At first I considered a standalone migration tool because I expect them to be very good at that single task. However, learning the idiosyncrasies of a new tool and trying to make it fit seamlessly into my development workflow seemed like more trouble than it is worth.

I decided to stick with a Common Lisp library and found the following seven that work with PostgreSQL and/or Postmodern:

• Postmodern-passenger-pigeon
• database-migrations
• cl-migrations
• Mito
• Crane
• Orizuru-orm
• cl-mgr

I quickly discounted Crane and Mito because they are ORM (Object Relational Mapper) libraries which are way more complex than a dedicated migration library. Development on Crane have stalled some time ago and I don't feel it is mature enough for frictionless use yet. Mito declares itself as being in Alpha state; also not mature enough yet.

I only stumbled onto cl-mgr and Orizuru-orm long after making my decision so I did not investigate them seriously. Orizuru-orm is in any case an ORM which I would have discounted because it is too complex for my needs. CL-mgr looks simple, which is a good thing. It is based on cl-dbi which makes it a good candidate if you foresee switching databases but even if I discovered it sooner I would have discounted it for the same reason as CL-migrations.

CL-migrations looks very promising. It is a simple library focusing only on migrations. It uses clsql to interface with the database which bothered me because I already committed to using Postmodern and I try to avoid adding a lot of unused code to my projects. The positive side is that it interfaces to many different databases so it is a good candidate if you are not committed to using Postmodern. It is also a stable code base with no outstanding bug reports.

The two projects I focused on was Postmodern-passenger-pigeon and Database-migrations because they both use Postmodern for a database interface.

Postmodern-passenger-pigeon was in active development at the time and it seemed safer to use than Database-migrations because it can do dry runs, which is a very nice feature when you are upgrading your production database and face the possibility of losing data when things go awry. Unfortunately I could not get it working within a reasonable amount of time.

I finally settled on Database-migrations. It is a small code base, focused on one task, it is mature and it uses Postmodern so it does not pull in a whole new database interface into my project. There are however some less positive issues.

The first issue is a hindrance during development. Every time the migrations ASDF system (or the file containing it, as ASDF prefers that all systems be defined in a single file) is recompiled it adds all the defined migrations to the migrations list. Though each one will only be applied once to the DB it is still bothersome. One can then clear the list with (setf database-migrations::*migrations* nil) but then only newly modified migration files will be added. The solution then is to touch the .asd file after clearing the migrations list.

The second negative point is quite dangerous. The downgrade function takes a target version as parameter, with a default target of 0. This means that if you execute downgrade without specifying a target version you delete your whole database.

I am currently using Database-migrations and it works well for me. If for some reason I need to switch I will use cl-migrations.

Using Database-migrations

To address the danger of unintentionally deleting my database I created a wrapper function that does both upgrade and downgrade, and it requires a target version number.

Another practical issue I discovered is that upgrades and downgrades happen in the same order as they are defined in the migration file. If you create two tables in a single file where table 2 depends on table 1 then you can not revert / downgrade because Database-migrations will attempt to delete table 1 before table 2. The solution here is to use the def-queries-migration macro (instead of def-query-migration) which defines multiple queries simultaneously . If you get overwhelmed by a single definition that defines multiple tables the other option is to stick with one migration definition per file.