Skip to content
View asctime's full-sized avatar
Block or Report

Block or report asctime

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. Ev2W Ev2W Public

    Gnome Evolution email client for Windows (MinGW64 x64)

    C 5

  2. Ev2W_Depends Ev2W_Depends Public

    Evolution for Windows dependency libraries (MinGW64 x64)

    C

  3. Trivial ChatGPT GUI, with context, i... Trivial ChatGPT GUI, with context, intent analysis and keyword enginies enabled; save & load chat; written in python3-gobject
    1
    #! python3
    2
    import sys, gi
    3
    gi.require_version('Gtk', '3.0')
    4
    from gi.repository import Gtk, Gdk, Pango
    5
    import re, openai, nltk, webbrowser
  4. Stevey's Google Platforms Rant Stevey's Google Platforms Rant
    1
    Stevey's Google Platforms Rant
    2
    ==============================
    3
    
                  
    4
    I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
    5
    
                  
  5. Notes on SASL and OAUTH2 for IMAP Notes on SASL and OAUTH2 for IMAP
    1
    SASL - _Simple Authentication and Security Layer_ is NOT a security protocol. It is an interface or an abstraction providing pluggable authentication _mechanisms_ to connection-oriented protocols. For example, the SASL interface in a system supporting the LDAP _protocol_ may support Kerberos-based authentication though traditionally LDAP does not support Kerberos-based authentication or security. Another example is that SASL built into an IMAP server may allow Oauth2-based authentication or any new authentication mechanism to be plugged in, though traditionally an IMAP server may only be supporting password-based authentication.
    2
    
                  
    3
    From now on, _mechanisms_ refer to authentication mechanisms like Kerberos-based authentication, OAuth2-based authentication or even plain text authentication and _protocols_ refer to connection-oriented protocols like LDAP, IMAP, SMTP, etc. 
    4
    
                  
    5
    The _mechanisms_ are grouped and named. For example, Kerberos-based authentication falls under a _mechanism_ name called _GSSAPI_.