@MeltedMindz Around now and the next 6 months might just be about the best time to invest since like 2020 though. Hopefully the midterms can reign him in and we can start converging fundamentals and price again.
@MeltedMindz I almost fomo'd after the 20% pump but then thought about the 100 times this has happened and decided to hold back and bet on Trump being a retard as Trump does. We are so divorced from fundimentals because of his grifting, endless wars, and general economic turmoil.
@NortonMpls@RobertKennedyJr L&B guac is so much better than whole foods guac and they're a local company with a unionized workforce. It is a bit more expensive but worth it imo
@mysticryuujin W for Streamingfast's Firehose/Substreams in this category. From what I can tell that's the direction app developers with users are headed anyway. I do appreciate your efforts on this thankless job as someone that has run into tracing discrepancies between clients though π
@JesseStojan@bennjordan And yea QUERY is new but my point was they could've still used POST in a way that isn't intended (GET style) and that now industry standard non-intended use case is the reason QUERY was proposed.
@JesseStojan@bennjordan Yea same here I'm not trying to argue for arguments sake I just want everyone to be on the same page so flock can't point to a small misunderstanding and paint all research on them as bad.
@BoredBaritenor@constans@Giomasterreal And how much could it have decreased if nuclear plants were still on? That decrease is a reflection of how much has been invested in renewables (great work btw!), but it could've been a whole lot more if you weren't forced to turn back on the coal power plants
@Mightymadmaxx@bennjordan You can quickly get links delisted from search engines once you find out they're crawling something you don't want them to. Flock likely had the results taken down within a few hours of being notified of the issue. Doesn't make the issue any better though
@bennjordan leak. But the full extent of the leak lies with the two data points that search engines crawled, namely identifiers like license plates and the reason for the search. It is yet another data point showing Flock's carelessness with these systems, just not as bad as CSRF would be.
@bennjordan FYI you won't be able to tell whether Flock is vulnerable to CSRF without logging in and checking request bodies and cookies. Those protections don't usually live in the URL. But the fact that they used GET requests instead of POST and forgot robots.txt did result in a real data
@JesseStojan@bennjordan only evidence we have of data leakage / insecurity. To tell whether Flock if vulnerable to CSRF you'd have to be able to login and check session cookies and request bodies which is where CSRF protections usually live.
@JesseStojan@bennjordan POST requests have been used in place of GET requests for many different use cases. That's why the QUERY request was introduced in RFC 10008. And in this case it would've in fact stopped the leak of identifiers (like license plates) and reasons via search engines. But that is the
@yumtapwater@JungAristotle Lab grown meat to the rescue. I'm eating it exclusively once I can't tell the difference. Hopefully not more than 10 years away
@hellashus@NortonMpls I've been a few times when running some errands around the area. Very nice! But I probably wouldn't go that far for it if that's all I was doing. I prefer to bike around the city if I'm just going out for a bite. First world problems, I know π