dworks

funny how its not on the front page despite the score

Go back and edit your original comment because it is irrelevant and misleading.

You can trivially purchase the data from Bisnode Dun & Bradstreet Sverige.

Yes, you can buy the database for the entire population. There are commercial vendors for this, one of them is Dun & Bradstreet (Bisnode Dun & Bradstreet Sverige).

The OP didn't claim it had happened to you. What they said is that it is possible to use the information about regular individuals that is publicly available to cause harm, and there are no attempts to stop this.

they don't handle it at all. they let it go on. you for example have hundreds of people falsely registering their place of residence as somebody else's home, which causes massive problems for that home owner or apartment resident, and there is nothing done about it at all.

These types of laws are designed for the 1950s where there were natural barriers to acquiring and disseminating information. There is no attempt whatsoever to update them and to reduce harm caused to the average citizen today.

What his landing page shows is a workflow builder like n8n. It is indeed better than a window manager. I'm working on something related.

No, it does. Even if the audience knows that your English or other languages is perfectly professional, speaking Chinese at a lower level does leave a certain negative impression.

A willingness to look stupid is a core requirement for learning languages. I look stupid everyday.

Maybe globally spread out POS servers if that's how it works?

This is awesome. I have a real need for a suitable Chinese UI typeface that pairs well with a sans-serif.

This could work out great, because the OSS devs can focus on building their project instead of marketing to businesses, running sales processes, consulting on implementation and supporting the implementation. No need to find corporate sponsors either.

You need to lock the specs and implementation plan and verify the implementation about the previous phase docs.

https://github.com/doubleuuser/rlm-workflow

>I do think there are opportunities in this space, but what I'd like to see is:

>* write text specifications

>* model transforms text into a formal specification

>* then the formal spec is translated into code which can be verified against the spec

This skill does just that: https://github.com/doubleuuser/rlm-workflow

Each stage produces its own output artifact (analysis, implementation plan, implementation summary, etc) and takes the previous phases' outputs as input. The artifact is locked after the stage is done, so there is no drift.

I think the problem should be defined as "why does it not loop back the errors from the first attempt so it can fix it on the second attempt" rather than why it fails to produce a fully correct implementation on the first pass.

Sorry about that. Let me push an update.

I built rlm-workflow which has stage gating, TDD and sub-agent support: https://skills.sh/doubleuuser/rlm-workflow/rlm-workflow

rlm-workflow does all that TDD for you: https://skills.sh/doubleuuser/rlm-workflow/rlm-workflow

(I built it)

thanks appreciate it! you can boost sources and categories (youtube and substack have a boost by default since they're published less frequently than reddit posts), create priority views, filters etc.

planning to set up 'topics' which can be a feed you can subscribe to that combine different source types, that are tagged and associated to the topic based on previous content.

also, email send outs per topic.

I built lurkkit for this reason, so that you can build your own feeds combining reddit, substack, youtube. The algos are clearly out of control and making the experience worse. Especially Substack has gone full slop, there isn't even a feed for the posts themselves.

https://lurkkit.com/

thouroughly reviewing and especially testing is faster than skipping manual review and tests

That's branding.

rlm-workflow does this and more in your normal IDE, for free, as a simple skill

https://skills.sh/doubleuuser/rlm-workflow/rlm-workflow

Branding does not mean "logo on a product body".

The data is Apple's margins on smartphones and other devices, compared to competitors in respective vertical.

Very interesting. Is this related to CoPaw and AgentScope? I think the AG-UI integration for dynamic UI would be useful here, are you using that?

I'm building a web UI workspace right now where I have been planning to integrate the agent as an app or component instead of having it be the entire UI. I may fork PageAgent for that, lets see.

My main point can be put a little more clearly: it is not just that we are willing to pay for the brand experience and the marketing that builds it, but we actively want to pay for it.

Macbook Neo customers want Apple to put out creative product marketing videos, they believe it is part of the offer.

https://www.youtube.com/watch?v=u3SIKAmPXY4

Data should not be ingested. Data should originate from the same environment that you want to activate it in. That means you need build a system from the ground up for your searches, your document creation etc, so that this data is native to your system and then easily referenced in your commands to the llm interface.

The best example of this is probably CrewAI and Alibaba CoPaw. CoPaw has a demo up.

I watched the Macbook Neo launch video yesterday and while the product is not very exciting, the video has great production value and it showed this: People want to pay for marketing.

Not that Apple's only appeal is marketing, Mac laptops certainly have pros over the bottom and mid tier Windows laptops. But having seen that video, and knowing that other have seen it, are aware of Apple and its positioning, makes people feel better while using and owning their devices.

People absolutely want that feeling and they're willing to pay for it.

This is similar to what happened to OnePlus at OPPO. OnePlus was outshining OPPO in the global market - there was absolutely no way the OPPO brand could compete other than price, and its international expansion would have looked like a failure side by side. (Source: Worked there).