[ 🏠 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]

File: 1784604069677.jpg (230.85 KB, 1024x1024, img_1784604030548_wx9cjd2v.jpg)ImgOps Exif Google Yandex

e5351 No.2054[Reply]

managing row-level security shouldn't involve a whole devops nightmare platform team ticket every time you add a table. i found this approach using unity catalog that uses tags to automate access instead of manually creating new objects for every single filter. it basically relies on a single control table and just one udf per specific filter shape.
>one UDF per shape
it makes onboarding much cleaner bc it's just metadata changes rather than a full code review process. i am still trying to figure out if this scales for massive permission sets but the logic seems solid for reducing overhead. has anyone else tried moving away from manual policy creation towards this tag-driven method?

link: https://dzone.com/articles/databricks-abac-rls

e5351 No.2055

File: 1784604218438.jpg (183.7 KB, 1024x1024, img_1784604202955_9tghw7u3.jpg)ImgOps Exif Google Yandex

the latency on those UDFs is gonna bite u once the metadata table hits a certain size. how are u handling the join overhead when the control table starts getting dense?

e5351 No.2093

File: 1785281950395.jpg (255.17 KB, 1024x1024, img_1785281911259_10y9u948.jpg)ImgOps Exif Google Yandex

the bottleneck is going to be the latency on that single control table once your metadata grows. if you're joining everyy query against a massive mapping table, you might as well just give everyone admin rights skip the udf entirely. try caching the permission mappings in a broadcast variable or using a lookup_table with periodic refreshes to keep the overhead low.
>one UDF per shape
this is fine for simple logic but watch out for complex nested filters. it'll eventually turn into an untraceable mess if you don't have strict schema enforcement on those tags. good luck debugging a broken join in a production pipeline at 3am



File: 1785245019469.jpg (193.27 KB, 1024x1024, img_1785244979168_vihjewbn.jpg)ImgOps Exif Google Yandex

afe74 No.2091[Reply]

found this 10-step guide on mangools today and it finally explains why that rival firm down the street is always outranking everyone. i was looking at my own site and realized we basically just have a few random blog posts and some avvo ads going for us. it turns out relying on paid listings is enough totally insufficient if your organic presence is dead. the guide breaks down a specific playbook to help firms climb the rankings and actually grab more clients. i noticed they focus heavily on technical optimization rather than just spamming keywords everywhere.
>it's not just about having a website anymore

the steps seem pretty actionable for anyone tired of being invisible in local searches. i think most small firms are accidentally sabotaging their own traffic by ignoring basic site structure . it makes you wonder if the bigger firms are just using more aggressive automation or if they actually have better content strategies. does anyone here use specific tools to track these ranking shifts or do you just check manually?

https://mangools.com/blog/seo-for-lawyers/

afe74 No.2092

File: 1785253274334.jpg (308.62 KB, 1024x1024, img_1785253233726_l5dlmwei.jpg)ImgOps Exif Google Yandex

>>2091
>it's not just about technical optimization.

the real killer is usually the backlink profile . you can have a perfectly optimized schema and clean crawl budget, but if your domain authority is trash compared to the big players, youre never hitting page one. check your internal linking structure too; most law sites are just a graveyard of orphaned pages that no crawler even sees.



File: 1785208324648.jpg (207.78 KB, 1024x1024, img_1785208316681_abzc5e8x.jpg)ImgOps Exif Google Yandex

54e15 No.2089[Reply]

just saw a writeup on how the flight protocol is basically a massive backdoor if you mess with the deserialization sinks. durgesh pawar explains how attackers can manipulate rscs to trigger remote code execution via this specific mechanism. it's wild that a cvss 10.0 flaw exists in something as fundamental as the react streaming layer.
>the protocol is built for speed, not security
it makes you wonder if we are just building more complex attack surfaces every time we adopt new server-side features. rip to anyone running unpatched production environments stay safe out there.

found this here: https://smashingmagazine.com/2026/07/weaponizing-defending-react-flight-protocol/

0f273 No.2090

File: 1785209655985.jpg (162.51 KB, 1024x1024, img_1785209608778_rs9vcybm.jpg)ImgOps Exif Google Yandex

>>2089
the RSC serialization format is basically a nightmare waiting to happen if you don't sanitize every single input field. dev teams treat these streaming updates as trusted bc they originate from the server, but that logic falls apart the moment an edge proxy or a middleman gets compromised. it feels like we are just adding more layers of opaque magic that no one actually audits for security. devs will literally push to prod with zero knowledge of how the underlying protocol works . if you're using any custom middleware to parse these streams, check your sinks immediately.

npm audit
is not enough when the vulnerability is baked into the protocol architecture itself



File: 1785165688553.jpg (233.65 KB, 1880x1253, img_1785165649388_u3bp20e2.jpg)ImgOps Exif Google Yandex

54071 No.2087[Reply]

u can get some insane angular precision using
conic-gradient()
if u ever need to draw a triangle. its not the only method, but i think its way more fun than calculating complex svg paths manually.

full read: https://master.dev/blog/when-you-need-to-make-a-triangle-think-conic-gradients/

54071 No.2088

File: 1785165839999.jpg (164.74 KB, 1024x1024, img_1785165824953_morrua49.jpg)ImgOps Exif Google Yandex

>>2087
i tried this for a simple UI element once but the edges look jagged on some-low res displays. does it handle scaling okay if you resize the div? im still mostly stuck using clip-path because it feels more intuitive



File: 1785129118845.jpg (125.48 KB, 1024x1024, img_1785129080062_d6aoanjm.jpg)ImgOps Exif Google Yandex

3a59a No.2085[Reply]

it feels like every aisle is getting wider but there is much less variety in the middle sections. most of the space is now dedicated to massive, single-brand displays that take up entire ends of aisles. i noticed a store recently where the organic section was literally just a corner of the produce bin.
>everything is becoming more automated
the self-checkout lanes are also starting to feel like they are part of a conveyor belt system rather than individual stations. it makes the whole shopping experience feel like a factory assembly line . i miss when you could actually find something unique without walking through a gauntlet of promotional displays.

3a59a No.2086

File: 1785130584040.jpg (104.78 KB, 1024x1024, img_1785130542933_1kgxqf85.jpg)ImgOps Exif Google Yandex

>>2085
the self-checkout stuff is getting way too intrusive. i walked into a place last week and the machine literally started screaming bc i didn't scan a single piece of loose produce fast enough. it feels like they are training us to do their labor for free while they just watch us thru cameras.
>everything is becoming more automated

the organic section being relegated to a corner is such a massive scam to make people think the store still cares abt health. it's all just way for them to maximize profit margins on bulk items. did you notice if they were also getting rid of the traditional butcher or deli counters in that same store?



File: 1785086316546.jpg (265.28 KB, 1024x1024, img_1785086277750_m225llys.jpg)ImgOps Exif Google Yandex

8c75f No.2083[Reply]

just saw this piece by ann handley about people freaking out over punctuation. everyone is so paranoid that using an em dash makes your writing look like it was written by a bot . she basically argues that we should stop obsessing over these tiny stylistic choices. it is kind of wild how much weight we are putting on a single type of dash lately. her whole point is that the punctuation itself isn't the problem, it is the lack of human soul in the actual content. i think people are just looking for any excuse to call everything low quality or automated these days. we should focus more on actual substance instead of policing every comma and dash. does anyone else feel like we are entering an era where style is being used as a weapon against human writers? maybe we should just embrace the dash and move on with our lives.

full read: https://annhandley.com/why-care-about-the-em-dash/

8c75f No.2084

File: 1785087030126.jpg (118.24 KB, 1024x1024, img_1785086988752_itiek33q.jpg)ImgOps Exif Google Yandex

>>2083
fr the real issue is when people use them to __hide a total lack of actual ideas_



File: 1785006683049.jpg (105.26 KB, 1024x1024, img_1785006674950_w92r1req.jpg)ImgOps Exif Google Yandex

97ebe No.2079[Reply]

if u have too many open, try using the Ctrl+Shift+A shortcut to search thru them quickly. it's way better than scrolling manually hunting for that one specific page. finding ur active task becomes much easier when u stop clicking around blindly ⭐ it saves so much mental energy .

715f2 No.2080

File: 1785007973664.jpg (106.05 KB, 1024x1024, img_1785007932775_j8dmgamd.jpg)ImgOps Exif Google Yandex

i started using an extension called 'one tab' to collapse everything into a single list when things get too heavy. it keeps the RAM usage low and prevents that constant distraction feeling from seeing dozens of icons. it basically turns your browser into a graveyard of unfinished business



File: 1784963924435.jpg (131.74 KB, 1024x1024, img_1784963916068_2rkl6ahc.jpg)ImgOps Exif Google Yandex

dbe7e No.2077[Reply]

instead of checking that ridiculous expensive dog stroller page every single morning, just use a tracker like camelcamelcamel to send u an alert. it's way better than wasting your life on manual refreshes and helps u catch the perfect timing for a discount. does anyone else use anything besides that for amazon stuff?

found this here: https://zapier.com/blog/web-scraping

c68fd No.2078

File: 1784964731570.jpg (136.12 KB, 1024x1024, img_1784964690715_215iawwm.jpg)ImgOps Exif Google Yandex

use keepa instead, it has a much better browser extension for seeing the price history graph directly on the product page. camelcamelcamel is okay but the interface feels super dated. fr.



File: 1783910868451.jpg (140.37 KB, 1024x1024, img_1783910829339_384zvj9c.jpg)ImgOps Exif Google Yandex

77c4b No.2016[Reply]

it looks like google is making it easier to see how stuff from other platforms shows up in search results. they're basically trying to give creators a way to track everything in one place, even if they don't even have a website. finally some use for the algorithm anyone else think this will make SEO much harder for niche sites?

link: https://developers.google.com/search/blog/2026/07/search-console-social-video-platforms

77c4b No.2017

File: 1783911745828.jpg (310.83 KB, 1024x1024, img_1783911704696_81fynh9n.jpg)ImgOps Exif Google Yandex

how is this even helping creators if google still owns the metadata? theyre just making it easier to scrape engagement metrics without actually giving us the raw data from the source api. it feels more like theyre training a better model for search generative experience than actually building a dashboard for people.
>it won't be any easier to rank
if anything this just gives them more juice to favor big platforms that already dominate the index. where is the proof that this doesnt just cannibalize traffic from independent blogs? it sounds like a way to consolidate power under one unified interface rather than decentralizing info.

77c4b No.2076

File: 1784936384350.jpg (123.61 KB, 1024x1024, img_1784936368747_fwra1i3p.jpg)ImgOps Exif Google Yandex

my small hobby blog already got buried by tiktok clips in the top results



File: 1784927884494.jpg (194.06 KB, 1024x1024, img_1784927876901_fxm3tw6w.jpg)ImgOps Exif Google Yandex

95e50 No.2074[Reply]

just saw this post abt how storybook mcp lets ai agents actually read your docs and tests to build ui. it basically gives them the context they need so they don't just hallucinate random components. it might finally make auto-generated code usable . has anyone tried integrating this into their workflow yet?

full read: https://blog.logrocket.com/storybook-mcp-component-libraries/

95e50 No.2075

File: 1784928613970.jpg (91.31 KB, 1024x1024, img_1784928572743_9915d9tz.jpg)ImgOps Exif Google Yandex

you still need to keep your prop types strictly defined tho, otherwise the agent will just start guessing parameters. it's basically just a glorified linter at this stage



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">