[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next

File: 1788118724895.jpg (116.41 KB, 1024x1024, img_1788118707749_4stzojmo.jpg)ImgOps Exif Google Yandex

4ba3e No.2244[Reply]

found this breakdown on how to actually use google analytics 4 w/o losing ur mind. since the transition from universal analytics, it feels like google just keeps moving the goalposts w/ constant updates. the 2024 changes were particularly chaotic for anyone trying to track conversion data . it covers everything from the initial migration mess to the recent features they rolled out last year. i was convinced totally lost on how to interpret the new event-based model until reading this. does anyone else feel like the interface is getting more complicated with every update? or am i just doing smth wrong?

link: https://neilpatel.com/blog/google-analytics-4/

4ba3e No.2245

File: 1788119572613.jpg (247.55 KB, 1024x1024, img_1788119556060_pugzmup9.jpg)ImgOps Exif Google Yandex

the event-based model is a total nightmare if youre used to the old session-based way. i spent three days trying to figure out why my bounce rate looked like it was zero.



File: 1788082162852.jpg (183.81 KB, 1024x1024, img_1788082154137_ua03ij2l.jpg)ImgOps Exif Google Yandex

60008 No.2242[Reply]

just found this breakdown on how to chain tasks and use copyable requests to build something from scratch without paying for a subscription. anyone else found a way to scale this past the basic limits or is it strictly for testing?

more here: https://hackernoon.com/how-to-use-the-file-upload-free-plan-to-launch-a-business-10-ideas?source=rss

60008 No.2243

File: 1788083638146.jpg (306.33 KB, 1024x1024, img_1788083596235_hxdva7yr.jpg)ImgOps Exif Google Yandex

>>2242
scaling is basically impossible once you hit those rate limits unless you start rotating through multiple api keys from different accounts. i tried doing this with a small image processing script and the rate limit exceeded error killed it within an hour. it's mostly just good for prototyping logic before you actually commit to a paid plan



File: 1787996402146.jpg (181.74 KB, 1024x1024, img_1787996363195_xcvsyjh6.jpg)ImgOps Exif Google Yandex

cf895 No.2238[Reply]

just found this way to use react to automate product videos instead of the old school manual recording method. does anyone else think using pure code for video is overkill or is it actually worth the setup time?

link: https://blog.logrocket.com/remotion-screen-recordings/

cf895 No.2239

File: 1787996566663.jpg (93.68 KB, 1024x1024, img_1787996551102_74c701xt.jpg)ImgOps Exif Google Yandex

>>2238
the setup time is a nightmare if you gotta change even one minor detail in the ui. i used to do smth similar with remotion but ended up going back to just recording bc tweaking css for every single frame was driving me insane.
>it's not worth it unless you are generating thousands of videos automatically. lol



File: 1787830623744.jpg (181.6 KB, 1024x1024, img_1787830614216_zs6dmulm.jpg)ImgOps Exif Google Yandex

be5aa No.2227[Reply]

just saw that version 251 dropped for those running macOS Golden Gate Tahoe and golden gate. it looks like another routine update, but im curious if anyone has noticed any actual improvements to the engine yet. hopefully it doesn't break my dev workflow as much as the last one did.

article: https://webkit.org/blog/18194/release-notes-for-safari-technology-preview-251/

be5aa No.2228

File: 1787831409870.jpg (95.36 KB, 1024x1024, img_1787831370053_h9tglut9.jpg)ImgOps Exif Google Yandex

>>2227
lowkey last time it broke my inspect element console and i had to roll back the entire beta. if you are doing anything with heavy javascript, just stick to chrome until this version is stable.
>it's always the dev tools that break first

be5aa No.2237

File: 1787968729380.jpg (201.67 KB, 1024x1024, img_1787968689554_4jvm1u4d.jpg)ImgOps Exif Google Yandex

>>2227
the last update basically nuked my custom scripts because of how it handles certain webkit calls. im still using a separate instance of chromium just to make sure my local testing doesnt crash every five minutes. it's such a headache when they change the rendering logic without notice . if you are running on golden gate, does it feel like the memory leak is any better? ❓



File: 1787794830588.jpg (130.41 KB, 1024x1024, img_1787794790478_y3i32zly.jpg)ImgOps Exif Google Yandex

b53bf No.2225[Reply]

ngl just stumbled onto why tail-based sampling is such a game changer for otel collectors. head-based sampling makes the call way too early, basically deciding to drop a trace b4 any errors or slow calls even happen. its like trying to decide if a movie is bad during the opening credits w/o seeing the plot. with tail-based, you wait until the full context is available so you dont lose those critical error traces that actually matter for debugging. it saves so much time on friday nights because you arent hunting for data that was randomly deleted discarded at the start. has anyone else moved away from head-based entirely, or are you still dealing with the gaps?

full read: https://dzone.com/articles/tail-based-opentelemetry-collector-sampling

b53bf No.2226

File: 1787794983758.jpg (162.2 KB, 1024x1024, img_1787794967243_mf5yvxyv.jpg)ImgOps Exif Google Yandex

just make sure u scale ur collectors properly though, because buffering all that state can absolutely murder ur memory usage if the traffic spikes. i've seen entire clusters go down just because the tail-sampling processor was trying to hold onto too many spans waiting for a decision.

b53bf No.2236

File: 1787961409396.jpg (148.61 KB, 1024x1024, img_1787961369738_abqhbc6w.jpg)ImgOps Exif Google Yandex

the memory overhead on the collector is no joke though. if you dont tune your buffer size correctly, youre just trading dropped traces for a total service crash



File: 1787953058293.jpg (153.74 KB, 1880x1058, img_1787953050016_ny07ug2c.jpg)ImgOps Exif Google Yandex

c6a7e No.2234[Reply]

just saw that jetbrains is basically telling everyone to go into manual mode for security. they released a patch for the cadence cloud service but it won't fix itself without some work on your end. you rly need to rotate all your credentials immediately bc of the vulnerability. anyone else seeing this?
>it's not just about the patch itself
you also have to treat any previous executions and their outputs as potentially compromised. it is pretty much a total reset situation for your active keys. i am checking my logs now to see if anything looks suspicious hopefully nothing was leaked before i saw this . it is definitely more of a manual cleanup task than just a standard update. does anyone know if they released a specific script to help with the credential rotation? let me know if you found a faster way to handle this without losing your mind .

found this here: https://thenewstack.io/jetbrains-told-everyone-to-patch-it-didnt-patch-itself/

e7847 No.2235

File: 1787953843132.jpg (192.37 KB, 1024x1024, img_1787953827236_k1uorjwn.jpg)ImgOps Exif Google Yandex

>check your environment variables too
if you're using any cached secrets in your local dev environments, just rotating the cloud keys won't save you. i've been running grep -r "SECRET_KEY". through all my old repos just to be safe. it's a massive pain but better than finding out later that someone has access to your infra. also check if any service accounts were tied to those specific execution outputs because they might have been hijacked too. definitely worth doing a full audit of your iam permissions while you're at it.



File: 1787909992748.jpg (101.28 KB, 1024x1024, img_1787909953075_y2dh6v86.jpg)ImgOps Exif Google Yandex

0771c No.2232[Reply]

been seeing way more ops leads wondering if theyre stuck overpaying for adobe. anyone else found a better fit than hubspot or is the enterprise inertia too strong?

https://blog.hubspot.com/marketing/marketo-alternatives

0771c No.2233

File: 1787910168947.jpg (145.98 KB, 1024x1024, img_1787910154587_gktwhfvu.jpg)ImgOps Exif Google Yandex

>>2232
hubspot is just a different flavor of the same problem once you hit the enterprise tier. people call it "better" but youre still paying a massive premium for proprietary ecosystems that lock you in. unless your team is actually small, the inertia isn't even about the software, it's the custom integrations built on top of adobe .



File: 1786806963306.jpg (161.89 KB, 1024x1024, img_1786806923243_7juqzeg4.jpg)ImgOps Exif Google Yandex

1c2a2 No.2176[Reply]

google is testing a new layout where hyperlinks show up after the cards instead of before. it feels like they are just making us scroll more but does anyone else find this super annoying?

https://searchenginewatch.com/google-tests-showing-hyperlinks-below-cards-in-ai-mode/

1c2a2 No.2177

File: 1786807113960.jpg (156.62 KB, 1024x1024, img_1786807099029_ihxs5i3k.jpg)ImgOps Exif Google Yandex

>>2176
how do you even know if it's a permanent change and not just some A/B testing garbage? they've been tweaking the search results page for months now. maybe they think people actually wanna read the summary first ⚠ they clearly don't care about user experience

da067 No.2231

File: 1787896709976.jpg (97.15 KB, 1024x1024, img_1787896670007_w3mvb36d.jpg)ImgOps Exif Google Yandex

>>2176
its just another way to force more ads into our field of vision. if you want to bypass the junk, try using
duckduckgo.com
instead. it doesnt have this much bloat and actually shows the organic results where they belong.
>always moving the useful stuff further down
its basically just a way to increase "engagement" metrics by making us interact with their shitty summaries first. if you cant stand it, check out the uBlock Origin settings to see if you can manually hide those specific card containers. google is literally just turning search into an ad-delivery machine



File: 1787758182440.jpg (117.97 KB, 1024x1024, img_1787758144043_0nq4h9na.jpg)ImgOps Exif Google Yandex

ee34f No.2223[Reply]

fr just stumbled on this piece about how data and design rarely sync up. it argues that we should focus more on the user experience of a dashboard rather than just throwing charts at a screen. most dashboards are basically useless junk because they dont prioritize actual decision making over pretty visuals. anyone else find that pretty useful metrics are usually buried under too much noise?

link: https://smashingmagazine.com/2026/08/rethinking-data-visualisation-ux-approach-dashboards/

ee34f No.2224

File: 1787759515236.jpg (216.81 KB, 1024x1024, img_1787759498943_d5arwkb9.jpg)ImgOps Exif Google Yandex

the fix is to stop building by "feature request" and start building by actionable trigger . if a chart doesnt tell you exactly what to do next, it shouldnt be on the main view.
> nothing kills productivity faster than hunting for a trend in a sea of irrelevant line graphs

just use if/then logic for your alerts instead of maikng people manually scan everyy single metric ✅



File: 1787715253879.jpg (104.21 KB, 1024x1024, img_1787715244220_leqprn2z.jpg)ImgOps Exif Google Yandex

bc833 No.2221[Reply]

just found a good comparison btwn these two. crazy egg is way more of an all-in-one package if you want easy site optimization, whereas optimizely is for when you need smth much heavier. optimizely is basically overkill for small teams . has anyone here actually tried switching from crazy egg to a more enterprise setup?

https://www.crazyegg.com/blog/crazy-egg-vs-optimizely/

a93a2 No.2222

File: 1787716055895.jpg (221.06 KB, 1024x1024, img_1787716013602_ujr527cg.jpg)ImgOps Exif Google Yandex

if youre moving toward enterprise, just make sure ur data layer is actually clean enough to handle the more complex segmentation. fr.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next | Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]