chiisana

joined 2 years ago
[–] [email protected] 1 points 1 month ago

Works very well on vanilla docker compose as well. Annotate containers with labels and it will wire itself up automagically. It’s wonderful.

[–] [email protected] 3 points 1 month ago (1 children)

There’s really compelling open source models like Zonos coming out; ElevenLabs will need to figure out how to thread the needle to keep everyone happy while other solutions eat into the pie.

[–] [email protected] 2 points 2 months ago (1 children)

If you can serve content locally without tunnel (ie no CGNAT or port block by ISP), you can configure your server to respond only to cloudflare IP range and your intranet IP range; slap on the Cloudflare origin cert for your domain, and trust it for local traffic; enable orange cloud; and tada. Access from anywhere without VPN; externally encrypted between user <> cloudflare and cloudflare <> your service; internally encrypted between user <> service; and only internally, or someone via cloudflare can access it. You can still put the zero trust SSO on your subdomain so Cloudflare authenticates all users before proxying the actual request.

[–] [email protected] 2 points 2 months ago

Yep! Give granite a try. I think that would be perfect for this use case both in terms of able to answer your queries and doing them quickly, without a GPU by just using modern CPU. I was getting above 30 tokens per second on my 10th gen i5, which kind of blew my mind.

Thinking models like r1 will be better at things like troubleshooting a faulty furnace, or user problems, so there’s benefits in pushing those envelopes. However, if all you need is to give basic instructions, have it infer your intent, and finally perform the desired tasks, then smaller mixture of experts models should be passable even without a GPU.

[–] [email protected] 2 points 2 months ago

Deepseek referred here seems to be v3, not r1. While the linked article didn’t seem to have info on parameter size, fact that they state it is sparse MoE architecture should suggest it is capable to run pretty quick (compared to other models of similar parameter space), so that’s cool.

[–] [email protected] 2 points 2 months ago (2 children)

Depending on what you want to do with it, and what your expectations are; the smaller distilled versions could work on CPU, but most likely will need extra help on top, just like other similar sized models.

This being a reasoning model, you might get a more well thought out results out of it, but at the end of the day, smaller parameter space (easiest to think as ‘less vocabulary’), smaller capabilities.

If you just want something to very quickly chat back and forth with on a CPU, try IBM’s granite3.1-moe:3b, which is very fast even on a modern CPU, but doesn’t really excel in complex problems without additional support (ie: RAG or tool use).

[–] [email protected] 5 points 2 months ago

Shipping address appears to be US only. Oh well.

[–] [email protected] 8 points 2 months ago* (last edited 2 months ago)

More than once I’ve heard the jokingly saying that ‘everything causes cancer in the state of California’ (regardless if they bore the warning label or not). I think while the intention may be good, the equivalent of notification fatigue is at play here and might not be delivering intended benefit/value.

[–] [email protected] 1 points 4 months ago (1 children)

I wonder if it’s more because they’re hitting capacity limits as result of physical limitations of memory on package design — physical distance resulting in potentially unbalanced performance due to some memory simply doesn’t have physical space that could deliver consistent performance, thus limiting capacity as an idea that crossed my mind.

So less so of a “it’ll be more performant” thing, but “this was great but we have to back paddle because we need more memory than the space could permit” kind of thing?

[–] [email protected] 6 points 4 months ago (1 children)

Yeah. We came from a time of incandescent light bulbs taking 60W per bulb with fixtures needing 2-3 bulbs. Turning those off regularly mattered. The obsession people have with turning their modern electronics off in the name of power savings is silly if not outright insane.

[–] [email protected] 4 points 4 months ago (3 children)

Electronics components do not like to have power states change frequently. Turning devices on and off frequently will decrease lifespan of device. Sure, you are saving money on your electricity bill, but at some point, the savings and environmental impacts are outweighed by the cost of the device/parts and the impact during manufacturing.

Also, don’t forget phantom draws from the power supplier is a real thing, which will most likely exceed your 5 zeros threshold. So that microwave oven, and laundry dryer? Don’t forget to unplug those after each use.

1
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

This morning, when I launched Voyager, my settings were reset. I suspect the app may have upgraded and something caused the preferences to be lost. This wasn’t the first time it happened, and who knows if the underlying conditions triggering this reset would happen again.

It would be nice if we can export our preferences into a json file (or whatever format serializes easiest), and re-import them next time the preferences gets lost, so we don’t need to manually make all the changes.

 

SkyTrain’s King George Station is temporarily closed from Saturday, Apr. 27 until mid-June while we complete multiple infrastructure maintenance works, including the replacement of an original component from when the station opened in 1992.

**Who’s affected: **Customers who ride the SkyTrain to and from King George Station.

**What do I need to do: **During this time, the terminus station for the Expo Line in Surrey is at Surrey Central Station instead of King George Station. Customers should plan for an additional 15 minutes of travel time if they use King George.

  • Customers who normally arrive by bus at King George Station to connect to the SkyTrain should stay on the bus to continue to Surrey Central Station.

    • The 345 King George Station/White Rock Centre, 394 White Rock/King George Station Express, and 395 Langley Centre/King George Station buses will all stop at King George Station, then continue to Surrey Central Station.
    • When connecting from SkyTrain to bus, customers should board their bus at Surrey Central Station.
  • Trains are arriving and departing for Waterfront Station at Surrey Central Station using both platforms, so check the screens for the next train.

  • Between 6 a.m. and 9 a.m. on weekdays, a SkyTrain replacement bus is operating every 15 minutes between Bay 2 at King George Station and a temporary stop on City Parkway at Surrey Central Station.

  • Know before you go — plan your trip at translink.ca/tripplanner and sign up for Transit Alerts at translink.ca/alerts.

Additional details:

  • During the closure, Expo Line service will operate Waterfront to Braid, Waterfront to Production Way–University, Waterfront to Surrey Central Station.
  • Customers who currently use the passenger pickup/drop-off zone at King George Station can access parking lots at Surrey Central Station to access SkyTrain service.
  • The Bike Parkade at King George Station will remain accessible.
  • Currently, there is a HandyDART passenger pickup/drop-off zone at King George Station; this will be closed. For the duration of the station closure, HandyDART service will continue as normal at Surrey Central and other stations.

**What’s happening: **We’re closing the station temporarily to replace a portion of the tracks called the turnout that allows trains to change tracks and direction at King George Station. It has reached the end of its service life. We’re also taking advantage of the closure to complete other work:

  • Replacing a section of power rail between King George and Surrey Central station. These rails are what provide power to the SkyTrain cars, allowing trains to move.
  • Realigning our guideway intrusion monitoring systems and preparing station platform to receive the longer Mark V trains that will enter service by the end of the year.
  • Elevator inspections, fibre optic cable replacement, station deep cleaning, and various asset repair and replacements that can be completed quickly and efficiently while the station is closed.

**Zoom out: **TransLink’s Maintenance and Upgrade Program is making investments in aging infrastructure across the system to keep customers safe, comfortable, and moving across a reliable transit network every day. For more information and to learn more, please visit translink.ca/keepmoving.

 

Due to the decentralized nature, and multiple communities on same subject exist across multiple instances, it is not uncommon for people to be subscribed to multiple communities of the same subject. It is also not uncommon for people to submit the same thing to multiple communities of the same subject, thereby resulting in multiple posts of the same content appearing in the feed. Cross post or not, the duplicated content clutter the feed, making it more difficult to consume content quickly.

I think it would be helpful to declutter by hiding/collapsing these posts. A possible implementation could be to keep an index of post titles, author, and submission time; then hide/collapse (cross)posts with same title, submitted by the same author, within some time interval (say for example +/- 1hr). That way the feed wouldn’t be as cluttered.

I understand cross referencing each post against other known posts is an exponentially large task, and could be very resources consuming, so even with the time range filter, it would be prudent to make this an option and likely disable by default to prevent performance issues.

It may be nice to inform the user on the post itself that there are other similar discussions, if they’re interested for other comments/interactions, but that’d be a nice to have in the future kind of thing.

view more: next ›