g6d3np81

Is this gonna be equivalent of ESLint + Prettier but in one performant package?

I also have a similar side project planned for a revamp. Successfully made a v1 with grease monkey (vanilla JS) + stylish back in maybe 2016. Super dangerous to keep firefox 56 running only for this front-end. Just need to do the v2 then migrate to latest librewolf.

I want to redo the whole thing in Vue, client side routing with build step. The problem is that

• site is not open source
• no API doc (but I already made my own)
• required log-in (no sensitive info)
• some route request must be made from that domain due to CORS

My goal is not to change the UI but wipe the whole page and start over with custom API call instead. V1 do this by visiting a 404 route to stop unnecessary load and use my own URL param for the API call. For bonus cringe I used local storage for database.

Ended up having to use userscript, and now I'm kinda stuck with how to mash Vite build and tamper/violent monkey together :(
Do you have any suggestion or resource I can learn more on this?

If you use QMK you're in luck.

https://github.com/daniel5151/qmk_firmware/blob/discipline/keyboards/coseyfannitutti/discipline/keymaps/prilik/keymap.c#L145
https://github.com/ridingqwerty/qmk_firmware/blob/cfd632e021f2460c50dd9e283426cc6e28c9a475/users/ridingqwerty/process_records.c#L297

Thank you. After thinking about it overnight, I realized I asked a wrong question. Your answer still helps greatly and get me more than half way to satiate my curiosity.
Tolerance grade and example objects that require different grade/minimum pi accuracy is what I was looking for.

TIL there is a closer approximation than 22/7

Thank you, I already skimmed through that article before posting. Maybe I failed to put my question into words properly.

I want examples similar to pool/fence circumference in the article. Along the line of "We're building x, and this is the worst rounding we can go, one fewer digit and it will be off by y"

I would not place my hope on kadokawa doing anything like that. I don't think they even care about anime industry aside from make money part of it.

Misinformation may reduce repeat visit, that part, I have no idea if google take into account when they rank the result. Domain/page age also plays a role. But what about other "problems"? If I try to de-optimize every items on that guide, will it speed up the de-rank as well?

Regarding SEO, What's stopping maintainers from vandalizing their own fandom page?

It would not be difficult to make a bot to update fandom page with a convincing but slightly wrong info, after a few hundred iterations, it's all useless. Go look at what google recommend and do complete opposite. I'm convinced this will bomb ranking and put whatever wiki they migrated to at the top.

Can you explain a bit more about "zooming, different levels of detail" you mention? Maybe break them down to separate issue you are having with the library, what does it do, what do you want that it's not doing. If there is a way to tweak it then you don't have to build the component from scratch.

But if you already abandoned the idea of tweaking timeline-js then you can have full control in vue, have to build it yourself though. Start by breaking the functionality of the timeline into separate interaction. From a quick look, timeline-js just make style attribute reactive. Have a box? good. Now put really long div in it with placeholder texture. Can you drag/scroll it? no? grab a suitable function from vueuse and make it scrollable. Follow with markers, zoom, dummy event items, data fetching (the actual width, marker spacing, events placement can be calculated from timestamp in json after this step), lazy loading, styling, animation, so on.

I don't know how much experience do you have with each things required (html, css, js, vue) so it is a bit difficult to give useful answer.

Events?? TimelineJS3/blob/master/API.md
Not sure what else is available if you want to build the component yourself though.

but note that because TimelineJS's primary use case is the embedded iframe, some of these methods have not been thoroughly tested.

I think you can replicate most of its function with vue alone, skip all the tedious work with vueuse. Lazy-load with Intersection Observer. Basic events and refs for zoom level.

I would start with putting all entries into a usable format. A CMS will help a lot. Maybe a JSON from your django server containing batch of entries, its timestamp, length, importance, tags, etc. Anything that is required to place entry on the timeline properly in vue.

EDIT:
Have you tried the official tutorial?

Flac is a low bar for any music player though. I don't know whether itunes support it yet, don't care.

I'm sure Rhythmbox works well for you and that is great. But I also need some niche features which might not be in it.

Mostly conversion and forensic thing.
ape tak tta format, bit compare, audio checksum, mass-tag/batch-tag, replaygain, custom playlist columns, statistic driven field. Don't know what else until I try and find it's missing.

I'm also sure I can get all those and more in different cli tool if I want but getting them in one software is very convenient.

After a quick look, DeaDBeeF might have most of what I want.

• Sort and group the tracks in any order you wish, using advanced Title Formatting scripting, compatible with Foobar2000

Got the date wrong, last time I tried it was 2018. Lot of new features added since then.