Default Textile Servers = Cafes too

[doodlemania2]

Is your feature request related to a problem? Please describe. When we initially set up Textile, the default "cafes" are specified as the Textile corporate servers I suspect.

Describe the solution you'd like Would be cool to have those emit from the textile cafes command so one can "remove" them (even at the risk of breaking Textile locally) and/or see them as part of the overall Textile apparatus. IE, even the main Textile servers are just big cafes, they should be treated the same.

Describe alternatives you've considered Make the Textile init process ask to "use default or specify custom cafe"

Additional context :)

[sanderpick]

By default, your vanilla Textile node won't be connected to any cafes... textile cafes ls reports 0 cause there really aren't any attached! You can totally run w/o a cafe, you're content is just not backed up and you won't have an "inbox" accessible over HTTP, which is a great help especially if you're not on a machine w/ a public IP address. That is to say, your peer is not easily discoverable.

[doodlemania2]

Woah, that's cool. So, in textile photos app, you're just defaulting to yall's corporate Cafes. I bet that's why my invites from phone can't get to my Linux node cause p2p fails of course cause different nets but then also, my Linux node is not joined to same cafe. So, question - how can one "join" the default corporate cafes?