Jump to content
Ketarin forum

floele

Administrators
  • Posts

    1,629
  • Joined

  • Last visited

Posts posted by floele

  1. Hm can you post your database maybe so that I can try to reproduce it? Any particular app is fails at or does it only happen randomly? Afaik you are the first Ketarin user so far experiencing this issue.

     

    And BTW: Quite interesting to know Ketarin is used by that project extensively. Nice find :)

  2. I just released Ketarin 1.7.0 (shouldn't be any different than the last beta).

     

    I will empty the online database now and make it so that deleted apps can no longer be re-uploaded. I'd appreciate if everyone could check if the database integration is working well and we need anything else to make it work properly.

     

    Oh and please re-upload all applications that should be included in the online database :)

  3. Another issue I see before we clear the current database is the naming convention. We need to settle on some way how apps should be named, otherwise it'll get messy soon.

     

    We could for example use

     

    Application Name 1.0.0 [beta|alpha] (English)
    for 32 bit apps and

     

    Application Name 1.0.0 [beta|alpha] 64-bit (English)
    for 64 bits. What do you think?
  4. Maybe I should rebuild my database to create a new unique GUID?

     

    Yes, you should.

     

     

     

    unintentional GUID collisions could also occur. 128-bits of entropy is nice, but 256 would be even better

     

    It's not unlikely. It's pretty much impossible. Now consider how many Ketarin users there are and how likely it would be that two of those generate the same GUID by accident.

     

     

     

    but I'm a security guy and I see the worst case scenario in everything I look at.

     

    We are talking about a rather non-critical consequences though, so I consider it overkill for now.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.