fire

If you are still in contact with the guy, could you ask him what the marketing learning actually were? Everyone has their own take on marketing and it's honestly really difficult to get the concept with most posts about it being so fluffy.

I'd honestly love some cliff notes or a bulleted list from someone who has actually succeeded, especially if they ( like me ) had no marketing experience beforehand.

heh, I guess I don't remember enough of my dreams to get anything out of it

> Based on the information provided, it is impossible to accurately interpret this dream without more information. Dreams often reflect our fears, desires, and subconscious thoughts, but the specific meaning of any given dream is highly personal and can depend on the individual's experiences, emotions, and beliefs. Without more context, it is impossible to say what this particular dream may mean.

I would love to do this for my TV honestly.

Bit of a tangent rant here - The LG77CX has a native res of 3840x2160, but the damned display's edid lists 4096x2160 as the "maximum", even though it causes skewing of the image on the display.

If you want to use DSR on nvidia cards, it bases it to the highest res, NOT the native res, which... causes skewing. If you then manually override the EDID data for the display via EITHER the windows registry or an unsigned monitor profile ( which requires you to disable driver signing overall! ), the nvidia control panel disables basically all configurable functionality; presumably so that you can't force DSR with a faked display resolution, because it used to work in older driver versions ( which are now too old to support 3k or 4k series cards )

I wonder what the time to kill on /this/ magic prompt will be

Nice! I just hadn't seen it referenced anywhere before - the last big ID wave I can remember was the swath of content about moving to snowflake style IDs

TIL about ULID[0]; It looks interesting, but the spec was last touched in 2019 and I haven't really heard of it before... is it actively used?

Also curious because I don't actually know: If a format spec is GPL, does that encumber implementations of said spec?

0: https://github.com/ulid/spec

holy hell; do they really need it to be that concentrated?

I adore t3ssel8r's work, it looks so good

I'm betting we're going to see subscription-only Activities[0] here shortly

0: https://support.discord.com/hc/en-us/articles/4422142836759-...

huh, I didn't know home and commercial rinse aids were any different?

This is a very cool concept, however,

(from the site:)

> Can I see the source code?

> Sure! Bulwark Passkey is built on top of an open source core called Virtual FIDO, which contains the USB emulation and FIDO protocol code, as well as the credential encryption and formatting. You can view the safety critical parts of the code, as well as easily decrypt and transfer your credentials out of the system.

So... it... isn't? It sounds like it isn't.

Like, maybe I'm just paranoid at this point, but regardless of how exciting this is in concept, I'm not too keen on using an (unaudited) virtual replacement for a hardware security token when I can neither audit the app I'm actually running, nor (preferably) build it from source; More generally, how would I even tell that the library in use by the app as-built is the same as the source on github?

Yeah! They tend to specialize against particular species!

I don't have research documents on hand atm, but I do have a terrifying video about them from zefrank: https://youtu.be/9TZQDA2yabg

my cliff notes for teflon non-stick:

· Don't use high heat, ever; you will destroy the coating and release toxic gas

· Don't leave the pan to get too hot over medium/low heat either; if a teflon pan ever smokes, you have officially fucked up.

· Don't use hard/sharp utensils against the pan; you will scrape off the coating

· Don't clean the pan with abrasive scrubbers; you will scrape off the coating

· Do use soft plastic, silicone, or wood utensils; these shouldn't damage the coating

· Do wipe the pan after use, while the remnants of cooking are still hot ( honestly this is just a general tip; I always wipe out my carbon steel pan after use as well )

· Do use a soft cloth or sponge and warm / hot water to clean the pan when hand washing; just like seasoned pans, you shouldn't need to clean them with actual soap all that often, but a light once over every so often will not hurt at all and helps mitigate dust/general grime.

· Do soak the pan if you have somehow managed to carbonize food onto the pan; attempting to pry off stuck burned food can pull off parts of the coating.

Personally though I'd recommend a stainless or carbon steel ( cast iron if you don't mind the weight ) and seasoning it, or basically anything with a ceramic coating ( all cliff notes apply to ceramic as well, but due to general coating damage concerns rather than ptfe's production of toxic gas and generation of microplastic granules )

Yeah, Adam Ragusea has a decent video[0] covering PFAS coating safety and production concerns; I hadn't realized how bad the factory side of things were prior to this - I only knew that overheating a teflon coated pan will destroy the coating, release toxic gas, and... kill any pet birds in your apartment :(

0: https://youtu.be/vZ1KmVmpC8o

if memory serves in many cases ( because there are a lot of parasite birds ) it's an evolutionary thing to prevent the parasite layer from destroying their own eggs - many of the parasite species will check on the nest after the fact and destroy it / the eggs if their eggs have been removed

I certainly haven't heard anything about it as a gsuite subscriber

yep, that's why I want it

My biggest complaint is probably that it doesn't support overlay or popup windows, which makes it impossible to use plugins like WhichKey[0] and such, which I like on normal neovim because I'm a scrub and don't know vim hotkeys by heart

0: https://github.com/folke/which-key.nvim

yeah, I've had this happen a number of times because the service was treating the `+` as a space in either the signup or the update, and I've had some success forcing it by replacing `+` with `%2B`

god I clicked in and suddenly an hour went by, this is brilliant

Sad to see, but happy they're open sourcing things.

I went ahead and filed an issue on kiteco-public[0] about their derived data because the readme states:

> By the way, we are happy to share any of our open-source-derived data. Our Github crawl is about 20 TB, but for the most part the intermediate and final pipeline outputs are pretty reasonably-sized. Although please let me know soon if you want anything because we will likely end up archiving all of this.

However, I have no idea if this is the right way to contact them

0: https://github.com/kiteco/kiteco-public/issues/5

yeah, it would be pretty simple to skip validation of the username if it didn't change

The key point here that was hard to find is that they and others had a username containing Clyde set already, and now can't update anything else about their profile because their username has come to be considered invalid.

That's pretty poor judgement to not even communicate this to affected users

is the app open source? I'm on android, so :c

I'm looking forward to it!

yeah, I find that it helps to have a password complexity gauge that shows the user their password is weak, but I still wouldn't stop them from using it ( except for minimum length )

is there a reason we couldn't or shouldn't use existing mail infra and maybe auto-negotiate a protocol upgrade for mastodon servers?

cool; just to expand - since hashed passwords are all the same length in a db, there's no benefit for max length requirements, and providing character limitations gives attackers a blueprint for brute force attacks since they now know what characters they don't need to try. When your requirements are too strict, this can make hashes orders of magnitude faster to reverse.

my personal stance is: if they can type it, it can be in a password

I would strongly suggest not having password complexity or length requirements except for perhaps a minimum length of 16+.

Anything else is additional user frustration and serves no real purpose given that you're presumably not storing passwords in plaintext in the year 2022.

this is a really cool idea! How do you plan to keep it up to date?