bump node_db max_count to 80

src/mesh/generated/mesh.pb.h

@@ -112,7 +112,6 @@ typedef enum _Constants {
 } Constants;
 
 /* Error codes for critical errors
-
  The device might report these fault codes on the screen.
  If you encounter a fault code, please post on the meshtastic.discourse.group
  and we'll try to help. */
@@ -278,7 +277,6 @@ typedef struct _Location {
 } Location;
 
 /* Debug output from the device.
-
  To minimize the size of records inside the device code, if a time/source/level is not set
  on the message it is assumed to be a continuation of the previously sent message.
  This allows the device code to use fixed maxlen 64 byte strings for messages,
@@ -397,7 +395,6 @@ typedef struct _Position {
  Default: "'bout three meters-ish" :) */
     uint32_t gps_accuracy; 
     /* Ground speed in m/s and True North TRACK in 1/100 degrees
-
  Clarification of terms:
  - "track" is the direction of motion (measured in horizontal plane)
  - "heading" is where the fuselage points (measured in horizontal plane)
@@ -439,24 +436,20 @@ typedef struct _ToRadio_PeerInfo {
 /* Broadcast when a newly powered mesh node wants to find a node num it can use
  Sent from the phone over bluetooth to set the user id for the owner of this node.
  Also sent from nodes to each other when a new node signs on (so all clients can have this info)
-
  The algorithm is as follows:
  when a node starts up, it broadcasts their user and the normal flow is for all
  other nodes to reply with their User as well (so the new node can build its nodedb)
  If a node ever receives a User (not just the first broadcast) message where
  the sender node number equals our node number, that indicates a collision has
  occurred and the following steps should happen:
-
  If the receiving node (that was already in the mesh)'s macaddr is LOWER than the
  new User who just tried to sign in: it gets to keep its nodenum.
  We send a broadcast message of OUR User (we use a broadcast so that the other node can
  receive our message, considering we have the same id - it also serves to let
  observers correct their nodedb) - this case is rare so it should be okay.
-
  If any node receives a User where the macaddr is GTE than their local macaddr,
  they have been vetoed and should pick a new random nodenum (filtering against
  whatever it knows about the nodedb) and rebroadcast their User.
-
  A few nodenums are reserved and will never be requested:
  0xff - broadcast
  0 through 3 - for future use */
@@ -539,16 +532,12 @@ typedef struct _Data {
 } Data;
 
 /* The bluetooth to device link:
-
  Old BTLE protocol docs from TODO, merge in above and make real docs...
-
  use protocol buffers, and NanoPB
-
  messages from device to phone:
  POSITION_UPDATE (..., time)
  TEXT_RECEIVED(from, text, time)
  OPAQUE_RECEIVED(from, payload, time) (for signal messages or other applications)
-
  messages from phone to device:
  SET_MYID(id, human readable long, human readable short) (send down the unique ID
  string used for this node, a human readable string shown for that id, and a very
@@ -557,7 +546,6 @@ typedef struct _Data {
  nodes() (returns list of nodes, with full info, last time seen, loc, battery
  level etc) SET_CONFIG (switches device to a new set of radio params and
  preshared key, drops all existing nodes, force our node to rejoin this new group)
-
  Full information about a node on the mesh */
 typedef struct _NodeInfo { 
     /* The node number */