Local AI models are getting a lot better. If you have the capability to run them, you could automate this yourself using your own browser automation, actually. It is rather fiddly, as mentioned in the post, but is absolutely doable, and probably the only option, at least for now, where you wouldn't need to provide your credentials to a third party.
Plaid does do screen scraping for smaller banks, but they have agreements for OAuth-based access with most of the largest institutions.
I've been trying to work on a new LLM code editor that does just that. When you instruct it to do something, it will evaluate your request, try to analyze the action part of it, the object, subject, etc, and map them to existing symbols in your codebase or, to expected to be created symbols. If all maps, it proceeds. If the map is incomplete, it errors out stating that your statement contained unresolvable ambiguity
I think there is a real benefit here, and it might be the actual next beneficial grounded AI sustainable use in programming. Since I the current "Claude code and friends" are but a state of drunkenness we fell into after the advent of this new technology, but it will prove, with time, that this is not a sustainable approach
I'm a little surprised nobody has mentioned Campfire [1].
It's open source, trivial to self-host, and can support an arbitrary number of rooms and users.
Sure, it doesn't have all of Discord's bells and whistles (for better or worse), but then neither do some of the alternatives mentioned in the article.
> A thoughtful-man named Maxwell Mouser had just produced a work of actinic philosophy. It took him seven minutes to write it. To write works of philosophy one used the flexible outlines and the idea indexes; one set the activator for such a wordage in each subsection; an adept would use the paradox, feed-in, and the striking-analogy blender; one calibrated the particular-slant and the personality-signature. It had to come out a good work, for excellence had become the automatic minimum for such productions. “I will scatter a few nuts on the frosting,” said Maxwell, and he pushed the lever for that. This sifted handfuls of words like chthonic and heuristic and prozymeides through the thing so that nobody could doubt it was a work of philosophy.
Sounds exactly like someone twiddling the knobs of an LLM.
The hostage naively walked past all the police and into the data centre, and you’re shooing them in the leg. They’ll probably survive, but they knowingly or incompetently made their choice. Sucks to be them.
When I get my way reviewing a codebase, I make sure that as much state as possible is saved in a URL, sometimes (though rarely) down to the scroll position.
I genuinely don't understand why people don't get more upset over hitting refresh on a webpage and ending up in a significantly different place. It's mind-boggling and actually insulting as a user. Or grabbing a URL and sending to another person, only to find out it doesn't make sense.
Developing like this on small teams also tends, in my experience, to lead to better UX, because it makes you much more aware of how much state you're cramming into a view. I'll admit it makes development slower, but I'll take the hit most days.
I've seen some people in this thread comment on how having state in a URL is risky because it then becomes a sort of public API that limits you. While I agree this might be a problem in some scenarios, I think there are many others where that is not the case, as copied URLs tend to be short-lived (bookmarks and "browser history" are an exception), mostly used for refreshing a page (which will later be closed) or for sharing . In the remaining cases, you can always plug in some code to migrate from the old URL to the new URL when loading, which will actually solve the issue if you got there via browser history (won't fix for bookmarks though).
You mean like it has become a mistake when the story about it broken up and went viral?
But if Hack Club did not complain about it, you would have happily took and kept taking their money?
That kind of a "mistake"?
In all seriousness, why should anyone believe what you are saying?
It seems to me that your story about a "mistake" is just as plausible as this kind of behavior simply being Slack's business strategy. Be ambiguous. Change the terms of the sale after the sale. Try poking. See which tactics works. If someone bites, take advantage of it. If they complain, call it a mistake and do damage control. Collect profits. Rinse and repeat.
Thank you for addressing this issue. Could you also provide feedback on the accusations that data export is only available for high-tier pricing plans and requires Slack's explicit approval?
> This was one of the most successful product launches of all time. They signed up 100 million new user accounts in a week! They had a single hour where they signed up a million new accounts, as this thing kept on going viral again and again and again.
Awkwardly, I never heard of it until now. I was aware that at some point they added ability to generate images to the app, but I never realized it was a major thing (plus I already had an offline stable diffusion app on my phone, so it felt less of an upgrade to me personally). With so much AI news each week, feels like unless you're really invested in the space, it's almost impossible to not accidentally miss or dismiss some big release.
Yeah, we got these red-bellied wodpeckers here, knocking on the metal top of the poles of the electricity lines. Since the main inlet is connect to a wall in our bed room, they wake us up early in the morning by their drumming, resonationg through the electricity lines from near and far.
It have spent hours, half aslep, pondering what that sound could be, it took quite a while before I found the origin!
> although I was worried that folks are too locked in to SaaS stuff
For some people the cloud is straight magic, but for many of us, it just represents work we don't have to do. Let "the cloud" manage the hardware and you can deliver a SaaS product with all the nines you could ask for...
> teaching a course on how to do all this ... there might be interest in that after all?
Idk about a course, but I'd be interested in a blog post or something that addresses the pain points that I conveniently outsource to AWS. We have to maintain SOC 2 compliance, and there's a good chunk of stuff in those compliance requirements around physical security and datacenter hygiene that I get to just point at AWS for.
I've run physical servers for production resources in the past, but they weren't exactly locked up in Fort Knox.
I would find some in-depth details on these aspects interesting, but from a less-clinical viewpoint than the ones presented in the cloud vendors' SOC reports.
I think the biggest issue in video games is the disconnect between how people perceive developers and what they do.
Many people complain about QA teams and how they "aren't doing their job". The real issue is that making video games requires so much testing that they can't keep up with meeting deadlines and goals. Considering that someone has to hand test nearly all situations that the only way you can really test a game is to release a beta quality game and let your users tell you whats wrong. Warframe is the best at trying to manage peoples expectations. The creative director went on periscope during a big release which made people understand what is happening. The head liveops (community manager) allows them to walk on water (https://twitter.com/rebbford) due to her ability to manage the community. Warframe is the sole example of a game that treats its uses like adults.
This reminds me of a time I was at a company using a BI tool for dashboarding. The numbers weren't making much sense to me, so I looked at the query building tool. I couldn't tell for the life of me if a part of the query was doing an inner join or left join. The business analyst who built the dashboard had no idea either.
It turned out that it was doing a left join when the intent was an inner join, and the data being shown was an order of magnitude higher than it should have been. This is when I lost all faith in these kinds of abstraction layers on top of SQL targeting people who don't actually know SQL.
> Warning: fopen(https://docs.google.com/spreadsheets/d/1s2eNqf5xpVX8j6LfnL6r...): Failed to open stream: Connection refused in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php on line 1493 Fatal error: Uncaught TypeError: fgetcsv(): Argument #1 ($stream) must be of type resource, bool given in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php:1496 Stack trace: #0 /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php(1496): fgetcsv(false) #1 {main} thrown in /mnt/web308/b1/30/54257730/htdocs/enforcementtracker/index.php on line 1496
Some people will argue we are open-core because almost everything is open-source (AGPL) but our sso and enterprise plugins are under a source-available proprietary license.
The reason that we didn't split them out of the codebase is that it's harder to maintain and would require to load the plugins. We didn't want to waste time on that when we had so much to build.
The point about the newer Bialettis being cheaper is absolutely true. My mother has an old (>10 years) Moka that feels heavy and sturdy. A couple of years ago, after accidentally leaving it on the stove for too long, the bottom chamber and the filter basket got a permanent burnt coffee taste, and we bought a new one to replace it. That one was lighter and came with a significant thinner filter basket, which I also attributed to either being counterfeit or just they shipping cheaper versions of the product to Brazil.
Then, a couple of months ago, I was on vacation in Italy and decided to get a brand new one as a gift, directly from an official Bialetti store. To my surprise, the Mokas in the store felt exactly like the lower-quality one we had bought in Brazil. I didn't even buy the gift.
It certainly solves the ethical debate, but sadly the data storage extortion is nothing more than a means to make you pay for your content multiple times.
I would support a political party that intends to change this, but I don't think any party I vote for actually cares about it.
Plaid does do screen scraping for smaller banks, but they have agreements for OAuth-based access with most of the largest institutions.