Hacker Newsnew | past | comments | ask | show | jobs | submit | asnyder's commentslogin

Unfortunately there are many companies that actually rely on SMS confirmation codes in real-time, which include reading it back to them.

A legitimate and generally well liked company, and its real helpful service representative used this method to verify my identify before they could finish their support effort.


I got this interesting pair of messages from Schwab recently - not sure if any other companies do this

On login:

Schwab Watch out for scams. DON'T share this security code with anyone, EVEN IF THEY CLAIM to be from Schwab. Your code for online login is XXXXXX

And then on a later phone call with an agent:

Schwab: XXXXXX is your Schwab security code to confirm your identity with the agent.

This is a nice touch, though I'm not sure how much it would help in a real scam situation for say, my grandma.


yeah someone that gets paid a lot needs to talk to someone whos pay depends on implementing that IT consultants directives.

relaying security codes by voice is how the bad guys do it, dont train your users to think its normal.

its probably not a bright idea to have your phones camera pointed at your screen while 2FA-ing or password resetting, or else someone will watch you login, and will see your codes, and use automation to authenticate with your digits faster than you can move a cursor and click.


Probably safe if you call them at a well-published number. If they call you, absolutely not.


How does this compare to the already established open source solutions such as Chatbox (https://github.com/chatboxai/chatbox), or Lobechat (https://github.com/lobehub/lobe-chat)?

Been using both, like Chatbox for how snappy it is, but is local only, vs Lobechat which allows you to setup centralized host to have shared host across clients but feels a bit clunkier.


One of the biggest differences I noticed off the bat is llms includes prompt caching which I'm not sure I've seen in any other self hosted UI options


I see Lobe and Chatbox both have prompt caching toggles, are you referring to something else?


I've mistakenly given Chatbox a new feature, sorry :). In LobeChat, after you select a particular model, it enables a mini-settings menu next to the model that lets you set caching, deep thinking, and thinking token consumption.


Ah that must be new since the last time I tried lobechat


Where do you see that? I can't seem to find it in the web or desktop apps for lobechat.

EDIT: I also don't see it in Chatbox


#freenode was generally the main IRC node I used with all the good dev rooms.

Seems to still be chugging along. You can even join directly via their web-client: https://freenode.net.

Personally I still use pidgin.im to connect to all the relevant #freenode goodness. Seems people forget it still works and is pretty great even all these years later :).


I forgot Freenode was still running, most projects left for https://libera.chat/

Due to https://en.wikipedia.org/wiki/Freenode#Ownership_change_and_...


Thanks so much for the update. Had no idea. Seems all the main channels moved over. Thanks!


Most went to libera, some went to OFTC[1], and a few moved to matrix as well.

[1] https://www.oftc.net/



Seems to be missing quite a bit of history. As many here mention, there was an entire ecosystem of tools to convert PSDs to HTML such as CSSHat, Engima64, etc., and its evolution into Avocode, Sketch, Zeplin, Invision Craft & Inspect, and other preview/prototyping/inspect/export tools.

Eventually all roads led to Figma somehow, which honestly I would've never expected. Still surprised Figma became Sketch before Sketch could become Figma.


Yes I left out a lot to keep it short and to the point. There has been many attempts at solving the handoff and none of them has been effective.

The solution is to get rid of the design handoff all together. Instead of designing user interfaces in vector drawing tools we need web design tools.


There's also open-source solutions such as rocket.chat, Mattermost, and likely a few more I haven't played with.

I wish Mattermost wasn't always trying to nudge you out of community version, but otherwise pretty solid, better than Slack IMO. Is unfortunate they require weird gitlab spoof bypass to use SSO in community version. Shameful it's not out of the box.

Many years ago Pidgin with multi-channel IRC was all I needed, but seems Slack killed that whole party, which brings us to the current situation :(.


I know Liveblocks.io has been making this very easy and accessible over the last few years. They recently introduced AI, and are promoting that of course, but as I understand it multiplayer collaboration (https://liveblocks.io/multiplayer-editing) is their meat and potatoes.

Not affiliated with Liveblocks, just aware of its existence.


I work at Liveblocks—yes! Our founders were inspired by Figma and wanted to make it possible for others to build apps like this more easily. We provide our own sync engine, Storage, which is aimed at this use case.


Opening up one's device does not void the warranty in the US. We have the Magnuson-Moss Warranty Act which forbids this, despite manufactures trying to groom us otherwise with those void if removed or broken stickers.

Most recently, FTC started to raise awareness and crack down on some abuse: https://www.ftc.gov/news-events/news/press-releases/2024/07/....

Will take a long time to de-program and by that time nothing will be replaceable to matter due to industries march towards preventing repair altogether.


There's also https://openobserve.ai, while not as stable as Grafana/Prometheus/Clickhouse, feels a bit easier to setup and manage. Though has a bit of ways to go, does the basics and more without issue.

Crazy crazy they spent so much on observability. Even with DataDog they could've optimized that spend. DataDog does lots of bad things with billing where by default, especially with on-demand instances you get charged significantly more than you should as they have (had?) pretty deficient counting towards instance hours and instances.

For example, rather than run the agent (which counts as an instance regardless of if it's on for a minute), you can send the logs, metrics, etc. directly to their ingestion endpoints and not have those instances counted towards their usage other than log and metric usage.

Maybe at that level they don't even get into actual by usage anymore, and they just negotiate arbitrary amounts for some absurd quota of use.


His legacy still exists and continues today. Even updated to modern sensibilities, cross-platform, and compatible with all your legacy Hypercard stacks!

As far as I remember, progression was Hypercard -> Metacard -> Runtime Revolution -> Livecode.

https://livecode.com

I was a kid when this progression first happened, my older brother Tuviah Snyder (now at Apple), was responsible for much of these updates and changes first at Metacard and then at its acquirer Runtime Revolution.

I even wrote some of my first programs as Hypercard compatible stacks. Was quite fun to see my apps on download.com, back in the day when that meant something :).

I always joked it required please and thank you due to its verbosity, but was super simple, accessible, and worked!

How nice, that even today one can take their legacy Hypercard Stacks and run them in the web, mobile, etc. Or create something new in what was more structured vibecoding before vibecoding :).


This seems like something completely different? Livecode looks like just another toolkit or SDK for developing standalone apps, which might be great for the handful of developers using it but certainly doesn't do anything to re-shape how users interact with their computers


Nope, is completely the same base. Scroll the homepage, and you'll see an example of Livecode (updated HyperTalk).

You can open your HyperCard stacks, or MetaCard stacks, or Runtime/Livecode Stacks in their IDE, code, edit, etc, similar to what you would have back in Hypercard days, but with modern features, updates, and additions.

It's backwards compatible with HyperTalk, its current language is an updated HyperTalk (i.e. an updated MetaTalk), that incorporates all that was, but adds new features for today.

Your Livecode apps can be deployed and run as cross-platform desktop applications (Mac, Win, *nix) , mobile applications, and as far as I remember, web applications with HTML5 deployment (so they say).

Not affiliated with them in any way, just sharing my understanding and memories.


And how exactly does this re-shape the user's (not developer's) relationship with their computer?


it says "GUI coding built in"


Can you elaborate on how that answers my question?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: