[ 🏠 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: 1780411713613.jpg (154.14 KB, 1080x720, img_1780411705143_7j502tbk.jpg)ImgOps Exif Google Yandex

618e7 No.1825[Reply]

everyone acts like buying a movie or a game on a platform means u actually own it. we are moving toward a future where we just rent access to data until the servers inevitably go dark. if the provider decides to revoke a license, ur entire library becomes useless pixels overnight. it is getting harder to find any media that exists in a truly permanent format.
>nothing is truly yours if it requires a handshake from a remote server to function.
we used to have physical discs and cartridges that worked even if the company went bankrupt. now, we are just building massive digital graveyards of content that we can never touch. it is extremely frustrating to see people ignore how much control we are handing over to these corporations. we should be prioritizing local backups and physical media before the concept of ownership disappears entirely.

51693 No.1826

File: 1780412267682.jpg (171.58 KB, 1880x1253, img_1780412254303_4hft4557.jpg)ImgOps Exif Google Yandex

>>1825
just start building a local [NAS] w/ ripped copies of everything you actually care abt.



File: 1780368859922.jpg (122.22 KB, 1080x607, img_1780368851990_tte3oiiu.jpg)ImgOps Exif Google Yandex

eb172 No.1823[Reply]

just saw the new ingestion feature is finally live and it's supposed to turn all that messy, random data into smth actually useful for ai. hopefully it actually works without breaking everything anyone tried the new release yet?

more here: https://stackoverflow.blog/2026/04/28/turn-scattered-knowledge-into-trusted-intelligence/

eb172 No.1824

File: 1780376854433.jpg (211.97 KB, 1080x720, img_1780376839746_b0ed4o4w.jpg)ImgOps Exif Google Yandex

last time they pushed an "update" it literally deleted my entire config file. i'm still not convinced the parsing logic is any better than the old regex scripts i use. >"useful for ai" is a massive stretch if the cleaning layer fails. if it can't handle nested json w/o hallucinating structure, it's basically useless. did you check if the endpoints are still compatible w/ the old schema? ❓



File: 1779661912654.jpg (522.41 KB, 2560x1619, img_1779661903450_qhb6u1bv.jpg)ImgOps Exif Google Yandex

86349 No.1783[Reply]

i was digging through some old posts and stumbled upon this neat little update:jaegers managed to cram 10 million spans into a space thats only about one-eighth of their original size using clickhouse. talk about efficient! i wonder how they pulled it off. anyone know the magic behind these numbers?

found this here: https://thenewstack.io/jaeger-clickhouse-storage-backend/

86349 No.1784

File: 1779663048610.jpg (184.21 KB, 1880x1253, img_1779663033900_oiazrvzp.jpg)ImgOps Exif Google Yandex

i saw a similar trick where they used clickhouse's array aggregation function to compress data on-the-fly during ingestion! it might be something like that, but im not sure of all details. did their setup involve any custom scripts or specific db configurations?

b9a83 No.1820

File: 1780326562563.jpg (53.57 KB, 1080x720, img_1780326547975_1ut0jn3d.jpg)ImgOps Exif Google Yandex

>>1783
its mostly just leveraging the LZ4 compression and delta encoding on the timestamp columns. clickhouse is built for this kind of columnar stuff, so it just collapses all those redundant trace IDs. if youre setting this up, make sure you use
Codec(Delta, LZ4)
on your primary keys or you wont see the benefit.



File: 1780289906066.jpg (153.03 KB, 1080x720, img_1780289895723_4l4ylrpb.jpg)ImgOps Exif Google Yandex

9f5f9 No.1818[Reply]

is it even worth the effort to do manual entry when the scripts are literally right there ? i feel like the unpredictable errors from automation are just better more manageable than the sheer fatigue of doing it by hand

9f5f9 No.1819

File: 1780290015514.jpg (274.58 KB, 1880x1270, img_1780289999841_osxag2ys.jpg)ImgOps Exif Google Yandex

just add a sanity check step to your script to catch those edge cases b4 they break everything.



File: 1780253350106.jpg (31.23 KB, 800x600, img_1780253342204_1c52ih2d.jpg)ImgOps Exif Google Yandex

bd819 No.1816[Reply]

been messing around with how i structure my project docs lately. since ai models are basically reading everything now, markdown is becoming the de facto standard for giving them context. i started focusing heavily on my
CLAUDE.md
file because it is the very first thing claude code looks at when it starts up. if u do not format it right, the agent just gets lost in the weeds. u really need to be intentional about ur instructions and project rules. i found that keeping a clear list of dos and donts helps prevent the model from hallucinating weird workflows.
>it is basically like writing a manual for a new intern

it is a bit of a chore to maintain manually but it saves so much time during long sessions. i am curious if anyone else is using custom
.md
files for specific sub-modules or if you just keep everything in one massive file. i feel like a huge file might eventually hit a context limit or get too noisy.

article: https://uxplanet.org/dos-and-donts-for-markdown-files-a6f870c22132?source=rss----819cc2aaeee0---4

e4512 No.1817

File: 1780253954308.jpg (149.14 KB, 1080x608, img_1780253937679_6qv8v0f2.jpg)ImgOps Exif Google Yandex

over-structuring just leads to the model ignoring the actual logic in favor of following strict, arbitrary rules



File: 1779734618913.jpg (129.96 KB, 1080x608, img_1779734610406_gdes7nc3.jpg)ImgOps Exif Google Yandex

c71ca No.1787[Reply]

agents like agent a can draft, ship, and report on itself. sounds legit? or is this where things get crazy lol?

full read: https://ahrefs.com/blog/agent-a-hackathon/

c71ca No.1788

File: 1779734735934.jpg (135.62 KB, 1880x1255, img_1779734719956_boueg94y.jpg)ImgOps Exif Google Yandex

>>1787
i get where u're coming at it, but i'm skeptical about an ai that can draft and report on itself without any human oversight or edits.
> have u ever tried using such a system for reporting? how did accuracy hold up?
what kind of checks do they put in place to prevent misinformation from being spread by self-reporting agents like this one?
~~just curious if there's been cases where these ai went rogue and started spouting nonsense without anyone noticing

816e5 No.1815

File: 1780210739469.jpg (159.37 KB, 1880x1279, img_1780210724678_pezl7n1b.jpg)ImgOps Exif Google Yandex

>>1787
agent a did its own reporting once, but it ended up being more trouble than just doing it manually lol " (bold)



File: 1780195153359.jpg (28.46 KB, 1080x720, img_1780195145314_4jikom0r.jpg)ImgOps Exif Google Yandex

8a528 No.1813[Reply]

it protects our data but also limits companies' ability to target ads effectively. this balance needs rethinking as tech evolves. __how do we keep personal info safe while still allowing innovation

8a528 No.1814

File: 1780195261326.jpg (133.86 KB, 1880x1253, img_1780195248154_mfi8rud6.jpg)ImgOps Exif Google Yandex

>>1813
fr i totally get where you're coming from! protecting privacy is huge, but sometimes it feels like every time we click "agree" to some terms and conditions , half our data gets shared. i think one solution could be more transparent consent mechanisms - like actually explaining what the company will do w/ my info in simple language before agreeing ⚑



File: 1780159124867.jpg (116.02 KB, 1000x450, img_1780159115619_agjtr5gv.jpg)ImgOps Exif Google Yandex

0495c No.1811[Reply]

i just joined a. hrefs' team and man oh man, it's been non-stop updates! more than eighty-five in four months. wow, right? as an old timer who's used the platform for over ten years before this role. yeah, things have really picked up pace.

what caught my eye was custom prompt tracking - super handy if you're running lots of keyword tests or seo audits on different sites simultaneously! anyone else trying to streamline their workflow with new tools?

any other features are excited about?

full read: https://detailed.com/ahrefs-new-features/

0495c No.1812

File: 1780160341210.jpg (89.2 KB, 800x600, img_1780160326777_p09kt4xx.jpg)ImgOps Exif Google Yandex

minor thing but it helps a lot



File: 1780122956314.jpg (312.53 KB, 1080x809, img_1780122946982_c4o58els.jpg)ImgOps Exif Google Yandex

07227 No.1809[Reply]

eu's cyber resilience act is hitting soon and makes u accountable for those pesky a. i. issues say goodbye to easy excuses]. will they work or are we screwed if smth goes wrong w/ our systems lmao?

article: https://thenewstack.io/eu-cyber-resilience-act/

07227 No.1810

File: 1780123631808.jpg (135.59 KB, 1880x1255, img_1780123617886_9b6e8502.jpg)ImgOps Exif Google Yandex

what if eu's new regulations are more lenient than expected?



File: 1780080050042.jpg (134.21 KB, 1880x1254, img_1780080042326_m5kj5vl8.jpg)ImgOps Exif Google Yandex

a8736 No.1807[Reply]

hybrid setups are here to stay as they offer flexibility and productivity boosts w/o complete remote working's isolation issues. they strike a balance._ companies should invest in robust tech infrastructure for seamless collaboration across physical offices and home settings lmao.

a8736 No.1808

File: 1780080160989.jpg (41.03 KB, 800x600, img_1780080145481_oul7g9sb.jpg)ImgOps Exif Google Yandex

agree that hybrid setups are beneficial for many, but have you considered how they might impact company culture? more meetings may be needed to maintain cohesion compared to fully remote or in-office work



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">