GPUI and Makepad are the two Rust UI frameworks that seem the most interesting for what I'm looking for in a UI framework (hybrid immediate/retained mode, self-drawn widgets, open source).
Not so much limitations. Rather behaviors I'm used to, around scrolling content, input fields, splitters for resizing panes etc. Can't recall specifics right now. Just small things that I usually get out of the box had to be implemented here.
I think the original SubSync was the useless linear tool I tried last time. Though the Sefzz15 fork added some kind of "piecewise" feature which might work.
No, it finds over a hundred of sync points it can match with the translated subtitle (either via reference subtitle or audio track). How the interpolation between the sync points is done I haven't checked, but it fixes gradual drifts, offsets, gaps, etc. It syncs basically everything.
Agent that has its own computer, plugins to connect it to various services and probably it's own memory. A virtual personal assistant. You could have different specialized Dots each with its own plugins, memory and instructions.
That's how I understand it.
Cloud compute means its work VM is isolated from your devices, so it can't destroy your local data as easily (unless it has access to your devices) and it's on 24/7. A big negative is that you are giving access to even more of your services and data to a third party and the lock-in into a walled garden happens once you start depending on it.
Publish new features first to clients that provide feedback, so rollout can be stopped, if there's an issue with new version. Telemetry off effectively prioritizes stability over speed of recieving new versions.
Yeah me too. Maybe that place will occupy the Astra Minor model that appeared in Microsoft's Azure model config. As Sol and Sonnet are now similarly priced (unless Sonnet 5.5 will reduce its price).
The policy is both, good, but also flawed. For example, you cannot persist settings, because one policy says that website settings should be ephemeral unless user agrees to persist them.
That's not true and is a very common misinformation people repeat online. You can save user preferences in cookies without any consent banner, if the cookie isn't used for tracking.
See here[0], page 6:
> As stated in Article 5(3) ePD: ‘This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service.’
0: https://www.edpb.europa.eu/system/files/documents/2024-10/ed...
As long as you do not share that info with 3rd party, and the user requested it, you can store via cookies pretty much whatever you want without the need for a consent screen
The guidelines you linked state: "These Guidelines do not address the circumstances under which a processing operation may fall within the exemptions from the consent requirement provided for by the ePD".
Let's check what "Opinion 04/2012 on Cookie Consent Exemption" [0] says under section 3.6:
"""
3.6 UI customization cookies
User interface customization cookies are used to store a user’s preference regarding a service across web pages and not linked to other persistent identifiers such as a username. They are only set if the user has explicitly requested the service to remember a certain piece of information, for example, by clicking on a button or ticking a box.
...
These customization functionalities are thus explicitly enabled by the user of an information society service (e.g. by clicking on button or ticking a box) although in the absence of additional information the intention of the user could not be interpreted as a preference to remember that choice for longer than a browser session (or no more than a few additional hours). As such only session (or short term) cookies storing such information are exempted under CRITERION B. The addition of additional information in a prominent location (e.g. “uses cookies” written next to the flag) would constitute sufficient information for valid consent to remember the user’s preference for a longer duration, negating the requirement to apply an exemption in this case.
"""
See that you need to provide provide "information in a prominent location (e.g. “uses cookies” written next to the flag)" to be able to store user preferences in persistent cookies. You don't need consent banner for that (which I didn't say you need), but you need to clearly inform the user. The act of setting a preference together with clear information about persistence counts as a valid consent.
GPUI and Makepad are the two Rust UI frameworks that seem the most interesting for what I'm looking for in a UI framework (hybrid immediate/retained mode, self-drawn widgets, open source).
reply