Tweetovi

	Sam Saccone @samccone	3. velj
	Odgovor korisniku/ci @elektronik2k5 Do you know of anyone who has documented the needs and gaps? I see a lot of saber rattling on the internet but am missing all of the nuance.
	Prikaz razgovora ·

	Sam Saccone @samccone	3. velj
	Odgovor korisniku/ci @poordadjcu link? :)
	Prikaz razgovora ·

	Sam Saccone @samccone	3. velj
	Odgovor korisniku/ci @benschwarz fun side-note: I spoke about the high level approach back in 2014: pic.twitter.com/4iRQOaxkVL
	Prikaz razgovora ·

	Sam Saccone @samccone	3. velj
	Odgovor korisniku/ci @benschwarz For me, I am evaluating how to formalize some more things. We have a pattern that is close to what redux does but it is hand-rolled and is less "strict" than redux. Formality and strict compile time checking is still the gap that I am looking to solve for.
	Prikaz razgovora ·

	Sam Saccone @samccone	3. velj
	Has anyone written up a postmortem/retrospective report on redux 📄? I want to read more about the kind of learnings that only arise over a longer timeframe + codebase size + engineer count.
	Prikaži podatke ·

	Sam Saccone @samccone	1. velj
	Odgovor korisniku/ci @andybons Good doc is good
	Prikaz razgovora ·

	Sam Saccone @samccone	29. sij
	Odgovor korisniku/ci @parkerreed @AndroidDev ci.android.com 👏
	Prikaz razgovora ·

	Sam Saccone @samccone	29. sij
	Odgovor korisniku/ci @sebmck @ladyleet i 2 ostali "I can drive a car far" .2/10 on the humble brag scale.
	Prikaz razgovora ·

	Sam Saccone @samccone	29. sij
	Odgovor korisniku/ci @RonAmadeo @TheRealScialex #implementation-details-are-leaking 😅
	Prikaz razgovora ·

	Sam Saccone @samccone	29. sij
	Odgovor korisniku/ci @OrangeCMS @Android We are downloading the actual image to flash your phone with :)
	Prikaz razgovora ·

	Sam Saccone @samccone	29. sij
	Odgovor korisniku/ci @TheRealScialex @RonAmadeo Confirmed, it is a branch that has the same manifest as aosp-master-with-phones but only builds on a fixed interval not on every commit.
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @lnplum @PandelisZ @Paul_Kinlan @Paul_Kinlan
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @PandelisZ @slightlylate @slightlylate
	Prikaz razgovora ·

	Sam Saccone proslijedio/la je tweet
	‏Pα̹̖̺̃̊ͩ̑̽ͥν͍̯̳̳τ̗̘̺̥̦͊̉̃ͥͫͅε̝͗̎͗ͮλ̒̓̿͆is🇪🇺 @PandelisZ	28. sij
	Odgovor korisniku/ci @samccone This is a very small and mostly unrelated part to your amazing webusb hackery but it's nice to see a team at Google playing nice with Edge pic.twitter.com/RHld2WJBun
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @devsnek @domenic Thanks for the report! We have fixed it and will deploy soon.
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @floreengrad @9to5Google @SkylledDev 🦕 will file this! Thank you
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @SkylledDev @9to5Google Thank you Kyle.
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @9to5Google @SkylledDev @evowizz @evowizz
	Prikaz razgovora ·

	Sam Saccone proslijedio/la je tweet
	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @9to5Google @SkylledDev In your article you mention that flash.android is not for recovery, that is correct! instead you can use: pixelrepair.withgoogle.com/carrier_select… which enables the exact workflow you outlined. Same (web USB) technology powers both applications!
	Prikaz razgovora ·

	Sam Saccone @samccone	28. sij
	Odgovor korisniku/ci @9to5Google @SkylledDev In your article you mention that flash.android is not for recovery, that is correct! instead you can use: pixelrepair.withgoogle.com/carrier_select… which enables the exact workflow you outlined. Same (web USB) technology powers both applications!
	Prikaz razgovora ·