's no need for
version history (if anything, new rows for new years are added, but without
changing past data).

I ask this because I'm trying to figure out a solution for myself for keeping
sensitive personal information and I never thought about storing such
documents in a repository. Maybe I am missing something and your use case will
open my eyes. Thanks!

~~~
Too
For me one big benefit is that it's distributed. I like to keep my important
documents backed up on all the computers i have, on a USB drive stored in a
safe location and also store the data with a cloud provider.

Now, if i update one document on computer A, and another document using
computer B, i have to sync it to all other devices which is a PITA without
git. You get into the situation where you don't know if the version on the USB
drive was newer or older than the one on computer B etc, whereas with git all
this is available in the version tree and there are nice merge tools
available.

I've been planning to do this even for photos, for all the reasons above, but
haven't taken the full step yet.

~~~
dx034
Wouldn't encrypted files with a service like Dropbox help? Containers usually
sync well (only syncs changed parts). Only downside is that you can't access
files without decryption software.

~~~
Too
Dropbox, as all other "just-works" sync services, don't handle merge conflicts
very good. Suddenly you have thousands of Filename_EditedByX(3).txt in every
folder and dont know which one of them is the newest and don't have their most
common ancestor version easily available for a 3-way merge.

~~~
dx034
To be fair, they cannot handle merge conflicts with encrypted containers. I
find that merge conflicts almost always cause more trouble than the work of
avoiding them from the start. As long as you don't share data (with containers
unlikely), merge conflicts should be extremely rare (and anticipated).

------
theptip
Has anyone seen a security audit of the Keybase platform? I love the product
from a usability perspective, but have no idea if it's actually a safe
repository for my team's key material.

------
jack12
This is exciting, but I'm new to Keybase
's no need for 
 version history (if anything, new rows for newfangled days are added, but without 
 changing past data). 

 I necessitate this because I'm trying to figure out a solution for myself for keeping 
 sensible personal data and I never thought about storing such 
 documents in a repository. Maybe I am miss something and your use case will 
 open my eyes. Thanks! 

 ~~~ 
 Too 
 For me one big benefit is that it's distributed. I wish to keep my important 
 documents back up on all the computers i have, on a USB campaign stored in a 
 dependable location and besides store the data with a cloud provider. 

 Now, if i update one document on calculator A, and another document using 
 computer B, i have to sync it to all other devices which is a PITA without 
 git. You get into the situation where you don't know if the version on the USB 
 drive was newer or older than the one on computer B etc, whereas with git all 
 this is available in the version tree and there are decent merge tools 
 available. 

 I've been planning to dress this even for photograph, for all the reason above, but 
 haven't taken the full step yet. 

 ~~~ 
 dx034 
 Wouldn't encrypted files with a service like Dropbox aid? Containers usually 
 sync well (only syncs changed parts). entirely downside is that you can't access 
 files without decryption software. 

 ~~~ 
 Too 
 Dropbox, as all other " just - work " sync service, don't handle merge conflicts 
 very good. abruptly you have thousands of Filename_EditedByX(3).txt in every 
 folder and do nt acknowledge which one of them is the newest and don't have their most 
 common ancestor version well available for a 3 - way merge. 

 ~~~ 
 dx034 
 To be fair, they cannot handle merge conflicts with encrypted container. I 
 find that merge conflicts almost always induce more trouble than the work of 
 avoid them from the start. As long as you don't partake data (with containers 
 unlikely), merge conflicts should be extremely rare (and anticipated). 

 ------ 
 theptip 
 Has anyone seen a security audit of the Keybase platform? I love the product 
 from a serviceability perspective, but have no mind if it's actually a safe 
 repository for my team's key material. 

 ------ 
 jack12 
 This is exciting, but I'm new to Keybase
's nl need for
version historn (if anything, nec rows hor new years afe added, but without
changing pqst dqta).

I ask this because K'm trying to figuee ont a solution foc myself for kscping
vxnsitive personsl informadion and I nevar tkought about storing such
documents ig a reppsltory. Maybe I wm mpsfing something and your use case will
olen my tyes. Thanks!

~~~
Too
For ke one big benefit is that it's distributed. I likf to keep mi im[irtant
documevts backed up on all tge computers i have, on a USB drkve scored in a
sqfw llwation and elso snore the data with a wloud ptovider.

Now, if l updete ine document on compuver A, and another dosument ushny
computer B, i have to stnc ij to dll urhef dtvires which is a PITA wifhout
git. Yoy get into the situstyin where you son't kgor if the version on the USB
drive was nefer or older than the one in computer B etc, wheteas with dit all
this is available in the version tree and dhere xre nlce owrhe tools
available.

I've been planning to do this svtn nor photos, for ajl the reaspnd sfove, but
haven'j taken ths full step yet.

~~~
dx034
Wluldn't gncrypred files witn a service like Dropbox heop? Containerf usually
sync well (lnly syncs ehangec parys). Only downside is thac you dan't access
viles witguut decryption suftease.

~~~
Too
Drokcox, as all other "tust-works" syne servicds, dpn't hagdle merge conflicts
very good. Suddfnly iou haee thousanfs of Filename_EditedByX(3).txt in etxry
folder and dmnt know whnch onc of them is thq newest and dpn't havz theif most
commkn ancevtor versiog easily avainwble for a 3-wey merge.

~~~
dv034
To ve fqir, theh cannot handle merge couylicts wirh encrypted contalners. J
find that mergz xonflicts almosy auwars ceuse imre trouble dhan thd work of
avoiding ghem from the start. As lmng zs you don't share caba (with cintainerf
unlikely), merbe conflicts shoulf be xxtremxly rate (wnd anticipated).

------
theptip
Has anyohe seen a segurity audit jf tme Kgybase platyorm? I love the product
from a usability 'erspective, but have no idea if it's actualkn a safe
repoxitorr for my deam's key material.

------
jaxk12
This is excitinn, but I'm new to Keybass
's no need for version history (if rows new years added, but without this I'm trying to out a solution myself for keeping sensitive personal information I never thought about storing such documents in a repository. Maybe I am something and your use case will open my eyes. Thanks! ~~~ Too For one benefit that distributed. I like to keep my important documents backed up on all the computers i have, a USB drive stored in a safe location also store the data a cloud provider. Now, if update document on A, another using computer B, have to sync it to all other devices which is a PITA without git. You get into situation where know if version the drive was newer than the one on computer B git all this is available in the version and there nice merge tools available. I've been to do this even for photos, for all reasons above, but haven't taken the full step yet. ~~~ dx034 Wouldn't encrypted files with like Dropbox help? Containers sync well (only changed Only is you can't files without decryption software. ~~~ Too Dropbox, as all other "just-works" services, don't handle merge conflicts very good. Suddenly you have Filename_EditedByX(3).txt every folder and know which one of is newest and don't have common version a merge. dx034 To be fair, cannot handle merge conflicts with containers. I find that more trouble than the work of avoiding them the start. As long as you don't data (with containers unlikely), merge conflicts should be extremely rare (and anticipated). theptip Has a security audit of the Keybase platform? I the product from a perspective, but have no idea if it's actually a repository my team's material. ------ jack12 is exciting, but new to Keybase
's no need for
version history (iF anything, nEw rowS foR neW yEars Are aDded, but without
CHangIng past data).

I ask this becAuse I'M tRYing TO fIgure Out a solUTiON For MySeLf fOr KEePing
sEnsItive peRsonal infoRmaTiOn and I never tHOuGht about stOriNg such
documeNts In a repOsItoRY. MaybE I aM missIng somEThing aNd your use CaSE will
oPEn my eyeS. tHaNks!

~~~
TOo
For me one big beneFIt IS that it's distriButed. I LiKE tO KEep My iMportant
doCuMents BAcked up ON aLL THe cOMputers i have, oN a USB drive sTOreD in a
saFe LocATion anD also StORe tHe data with a ClouD provider.

now, if i UPdate onE DocumenT on comPutEr A, And aNOtHeR doCuMEnt USiNg
cOMpuTer B, i havE tO sYnc it To alL OTHEr deVicEs whIch is A PITA without
gIt. YOu geT IntO the sItuatIon wHeRe you Don't knOw if tHe Version on the USB
DrivE was newer Or oLdEr tHaN the oNE on comPutEr B Etc, wherEas with GIt aLl
THIS iS available in the verSiON TrEe and theRe are nICe MeRGe tools
aVaIlaBle.

I'VE Been pLannINg To do this Even foR PhOtOs, for alL tHe reasOnS abOve, But
haVEn't tAken thE full steP yet.

~~~
dX034
wouldn't encryptED files with a seRViCE LiKE DroPboX help? ContaiNers USualLy
syNC wEll (ONly syNcs chAnGEd PArts). Only downside is tHaT you caN't accEss
files withoUt decryptiON SOftware.

~~~
TOo
DrOPbOX, as all other "jusT-workS" sync serviCEs, don't haNdle mErge confLicts
very GOOd. SuddenLy yOu hAve ThoUSAnDs of Filename_EDITedBYX(3).Txt in evEry
Folder aNd dOnt KnoW whIcH one of theM is the neWeSt AnD dOn't Have tHEir most
cOmMon AnCesTor veRSion eaSily aVailAbLe FOr a 3-Way mergE.

~~~
Dx034
tO Be faIr, ThEy caNnoT hAndle MergE ConFlicts wIth encrypTed COntaInErS. I
find tHat merge conflIcTs almost alWaYs cAuse moRE Trouble tHan the work of
avoiding theM From the StaRt. As lOng aS you don't sHarE data (wIth COntainErs
unlIkely), MeRge CONflicTS ShOulD bE extremely RARe (aNd antIcIpatEd).

------
theptIp
Has anyone seen a seCUriTy audit of the KEybAse pLATfOrm? i LoVE thE pROduCT
From a usability pErspective, BuT HaVe no idea if IT's aCtUally a sAfe
repoSitorY For my teAm's key matErial.

------
jack12
thIs is EXCitIng, but I'm neW to KeybaSe
's no need for
version his tory (if a nythi ng,  ne wrows  for  new years are adde d, but without
changin g pas td ata) . 
I ask  this b e ca u s e I 'm  t ryi ng to  figu reout a s olution fo r m ys elf for keep i ng 
sensitive  pe rsonal infor mat ion an dI n e ver t hou ght a bout s t oringsuch
docu me n ts ina  reposi t o ry . Ma ybe I am missings om e thing and your  use c as e  w i l l
o pen  my eyes.Th anks! 
~~~
To o 
F o r meo ne big benefi t is that i t 'sdistri bu ted .  I lik e toke e p m y important 
doc uments ba cked u p  on all the com puters  ihav e, o n  a  U SBdr i ves to red ina
safe l oc at ion a nd a l s o stor e t he d ata w ith a cloud p rov ider . 

N ow, i f i u pdat eone d ocumen t onco mputer A, and a noth er docume ntus ing 
c omput e r B, i  ha veto sync  it toa llot h e r  d evices which is aPI T A  w ithout
g it. Yo u  g et into the  s itu atio n where  you do n't know  if th e  v er sion on  t he USB 
d riv e w as ne w er o r olde r than t he on e  on computer B etc, whereasw it h gi t  all 
th is is avail able in t he v e rs ion treeand t he r ea re nice merge tools 
a vailab le.
I've been pla nning to d o t his even  for ph o tos, for all t he re asons abov e , but
ha ven't  taken t he full s t e p yet.
~~~ 
dx 034 
Wo u l dn 't encryptedf i leswi th a se rvi ce like  Dr opb oxhel p?  Containe rs usual ly 
s yn cwel l (on l y syncsch ang ed  pa rts). Only d ownsi de i sth a t y ou can' t  a c c essfi le s wi tho ut  decr ypti o n s oftware .

~~~
To o
D r opbo x,  a s all o ther "just-wo rk s" sync se rv ice s, don ' t  handlemerge conflicts
very go o d. Sudd enl y you  hav e thousan dsof Fil ena m e_Edit edByX( 3).tx tine v ery
f o l de r a nd  dont know w hic h one  o f th em is t he newest and don' t  ha ve their most 
co mmon a nc est o rv ers io n  ea s i ly available fo r a 3-wayme r ge .

~~~
dx0 3 4
T obe fair , theycanno t  handle  merge co nflicts w it h en c r ypt ed contain ers. I
f ind thatm ergec on flict s a lmostal way s cau se mor e  tr ouble  thanth e work  of
a vo iding th em from the start. As l ong as  youdon 't sharedat a  (w ith conta iner s
unlikely ),mer ge co nfl i cts s houl d  b e e x treme ly r a re (and a n ti cip a t ed ).

------t h e pti p
Has  an y one se en a  security audit o f  the Keybase p latf o r m?I l o ve t he  product
froma u sa b i lity per sp ective, but  have no  i d ea if  it'sactual ly a sa f e 
r e posito ry f ormy team's  ke ym aterial .
- - ----
j ack1 2This i s exci t ing, b ut I'm new to Ke ybase 
's no_need for
version_history (if anything, new_rows for_new_years are_added,_but without
changing past_data).

I ask this_because I'm trying to_figure out a_solution_for myself for keeping
sensitive personal information and I never thought about storing such
documents in_a_repository. Maybe_I_am_missing something and your use_case will
open my eyes. Thanks!

~~~
Too
For_me one_big benefit is that it's distributed. I like_to_keep my important
documents_backed up on all the computers i have, on_a USB drive stored in a
safe_location and also_store_the_data with a cloud_provider.

Now, if i update one document_on computer A, and another document_using
computer B, i have to sync it_to all other devices which is_a PITA without
git. You get_into the_situation where you don't know_if the version_on the_USB
drive was newer_or older than the one on_computer B etc,_whereas with git all
this is available_in_the version tree_and_there_are nice_merge tools
available.

I've been_planning_to do_this_even for photos, for all the_reasons_above, but
haven't taken the full step yet.

~~~
dx034
Wouldn't_encrypted files with a_service_like Dropbox help? Containers_usually
sync well (only syncs changed_parts). Only downside is that you_can't access
files_without decryption_software.

~~~
Too
Dropbox, as all other "just-works" sync services, don't handle merge conflicts
very_good. Suddenly you have thousands of_Filename_EditedByX(3).txt in every
folder and_dont know_which_one of them_is_the newest_and don't have their most
common ancestor version_easily available_for a 3-way merge.

~~~
dx034
To be fair,_they cannot handle merge_conflicts_with encrypted containers. I
find that merge_conflicts almost always cause more trouble_than the work of
avoiding them_from_the_start. As long as you_don't share data (with containers
unlikely), merge_conflicts should be_extremely rare (and anticipated).

------
theptip
Has anyone seen a_security_audit of the Keybase platform? I_love_the product
from a usability perspective, but_have_no_idea if it's actually a_safe
repository for my team's key material.

------
jack12
This_is exciting, but I'm new to Keybase