home.social

#gitg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gitg, aggregated by home.social.

  1. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  2. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  3. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  4. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  5. A performance testing surprise I did not have on my bingo card this month: #gitg being 3 times slower to reload a git repository compared to the initial load. It… it can't be! :blobsweats:

    gitlab.gnome.org/GNOME/gitg/-/

    #Sysprof #profiling #git #GNOME

  6. @delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform

    cloud.google.com/blog/topics/t

    #SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach

  7. @delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform

    cloud.google.com/blog/topics/t

    #SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach

  8. @delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform

    cloud.google.com/blog/topics/t

    #SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach

  9. @delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform

    cloud.google.com/blog/topics/t

    #SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach

  10. @delighted Well, yes.. that's the ShinyHunters/ScatteredSpider collaboration, but now they have the Salesloft Drift approach, which Google Threat Intelligence Group had tracked as UNC 6395. It looks like GITG just updated the scope of the attack today to any and all authentication tokens stored in or connected to the Drift platform

    cloud.google.com/blog/topics/t

    #SalesloftDrift #Salesforce #GITG #vulnerability #OAuth #Tokens #databreach

  11. @partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: gitlab.gnome.org/GNOME/gitg/-/
    @tbernard

  12. @partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: gitlab.gnome.org/GNOME/gitg/-/
    @tbernard

  13. @partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: gitlab.gnome.org/GNOME/gitg/-/
    @tbernard

  14. @partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: gitlab.gnome.org/GNOME/gitg/-/
    @tbernard

  15. @partizan We need contributors—patch writers and code reviewers—to help with #gitg. Still waiting for someone to step forward to begin a GTK4 port: gitlab.gnome.org/GNOME/gitg/-/
    @tbernard

  16. Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?

    I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: gitlab.gnome.org/GNOME/gitg/-/

  17. Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?

    I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: gitlab.gnome.org/GNOME/gitg/-/

  18. Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?

    I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: gitlab.gnome.org/GNOME/gitg/-/

  19. Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?

    I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: gitlab.gnome.org/GNOME/gitg/-/

  20. Can I get a @vala_lang FLOSS hacker interested in this fine newcomers-difficulty-level UX issue to solve in #gitg?

    I tried starting to fix it myself a year ago and couldn't figure out how to get past my initial attempt to check the horizontal vs vertical orientation of the layout. I could try again (if I'm desperate enough), but would need a pair programming session with a #Vala enthusiast… or such an enthusiast could probably solve it by themselves in half an hour: gitlab.gnome.org/GNOME/gitg/-/

  21. A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:

    gitlab.gnome.org/GNOME/gitg/-/

    Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!

    #git #GNOME #performance #opensource

  22. A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:

    gitlab.gnome.org/GNOME/gitg/-/

    Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!

    #git #GNOME #performance #opensource

  23. A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:

    gitlab.gnome.org/GNOME/gitg/-/

    Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!

    #git #GNOME #performance #opensource

  24. A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:

    gitlab.gnome.org/GNOME/gitg/-/

    Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!

    #git #GNOME #performance #opensource

  25. A free 2x performance speedup has now landed in #gitg nightly for every time you click a branch (or any type of ref) in the sidebar :blobaww:

    gitlab.gnome.org/GNOME/gitg/-/

    Thanks to @GeopJr for creating the fix, and to @albfan for reviewing & merging it!

    #git #GNOME #performance #opensource

  26. Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: gitlab.gnome.org/GNOME/gitg/-/

    #git #GNOME

  27. Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: gitlab.gnome.org/GNOME/gitg/-/

    #git #GNOME

  28. Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: gitlab.gnome.org/GNOME/gitg/-/

    #git #GNOME

  29. Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: gitlab.gnome.org/GNOME/gitg/-/

    #git #GNOME

  30. Huh! Turns out #gitg has no problem fetching other people's anonymous HTTPS repositories, but it chokes on SSH git repositories backed by some SSH keys. Bug report, up for grabs: gitlab.gnome.org/GNOME/gitg/-/

    #git #GNOME