Notices by jae (jae@fsebugoutzone.org), page 2
-
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 08:40:39 JST jae
@tinfoil-hat @dcc have you not met dcc? he's like a battletank -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 08:13:03 JST jae
@dcc @tinfoil-hat
> I still need a month or two before its setup.
reals?
take my money. i have a box that needs a home -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 08:10:40 JST jae
@lain i respect a man who respects nicole. klaus is out, nicole is in. new world order -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 06:27:13 JST jae
@mischievoustomato @bajax
image.png -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 06:18:51 JST jae
@mischievoustomato @bajax -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 01:47:36 JST jae
@TeaTootler @RedTechEngineer @phnt @p @m0xEE
> almost my entire network is e waste
excellent. i draw the line at router/switch. those are all newer components. -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 00:46:33 JST jae
i will refrain from saying vulgars during standup.
easiest_change.gif -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Saturday, 12-Apr-2025 00:43:12 JST jae
@waff @RedTechEngineer @TeaTootler @m0xEE @p @phnt
> people who pay top dollar are suckers
i know this too well
> e waste facilities
i've got a three node kubernetes cluster running on e-waste. it's nice e-waste, but e-waste nonetheless. i also gifted some to another kubernetes operator for the cost of shipping -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 22:42:34 JST jae
@p @TeaTootler @m0xEE @phnt
> And completely changes the service from "Store these blobs" to "execute arbitrary code".
the system doesn't exec arbitrary code. it handles git operations, drops builds, runs linters, sast/sca, full test-harness with regression suite, then deployments where applicable. it's all very intentional.
ace theoretically could occur in the ci system (not related to forgejo), however if the operator is running a ci system that allows elevated privilege to the host operating system that the runners kick on, that is problematic and poor choice to make. i do not have that problem.
and the scraper issue people were hemming/hawing about is a non issue when you have a waf at the edge, which we do. (servo has ascended) -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 21:53:16 JST jae
@phnt @TeaTootler @m0xEE @p
> Imagine not knowing how to use git.
does not compute.
> It's a collection of small bug fixes they didn't backport from upstream that drove me crazy.
do you have a list besides what you listed here? i maintain my own fork and can bring them forward.
> LDAP auth was broken for more than a month with a fix already in Gitea (maybe still isn't fixed). At work we depended on this, so I had to build custom images after every update.
interesting that people use this for work. i think forgejo is a bit behind since they are volunteers and not paid coders
> Mirrors with LFS objects would seemingly randomly balloon in size. This one annoyed me for months until it got fixed in some release.
i saw this too, but i only mirror one repo so it wasn't a big problem.
> And lastly, after the addition of Forgejo actions, mirrors would start to have failing pipelines that got enabled automatically even though zero runners were configured.
it sounds like default behavior is to pull in repo attrs like actions_enabled: true is that what you mean? i disabled actions on my system since it's not very mature. i used woodpecker which is fine atm.
> One day, I got fed up with Forgejo thanks Chinese scrapers downloading bundles and tarballs which created 30GB of orphaned archives, compared the Forgejo v7 and Gitea 1.21 (base for Forgejo v7) schemas and manually reverted the migrations. Did the same few days later at work and that solved all our problems I had with Forgejo. Plus the whole relicensing thing with Forgejo rubbed me the wrong way. They tried LibreOffice EEE and failed. Companies still prefer Gitea or even GitLab (we use both for reasons).
i can understand how this might be an issue for work/business. my business is just get shit done and hack everything. i have the luxury of laughing at licensing. -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 20:32:31 JST jae
@p @RedTechEngineer @TeaTootler @m0xEE @phnt @waff
image.png -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 20:32:11 JST jae
@p @RedTechEngineer @TeaTootler @m0xEE @phnt @waff
> Old machines are fun; people have to turn anything into a Cause nowadays. Minimalist computing is fun, too, getting some use out of really old shit.
it's fun if you have the gear, but there's some who will pay top dollar just to claim retro/minimal/whatever-cause.
the only cause i endorse is crunching machine code (and global hysteria for laughs)
> Hold my beer.
visions of tony robbins in an elevator
image.png -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 20:23:22 JST jae
@p @waff @RedTechEngineer @TeaTootler @m0xEE @phnt
> because I wouldn't buy an ancient machine just to run $current_year Linux slop on it.
there's a trend to going back to these ancient devices. something-something permacomputing. which i don't get.
when the flood comes, it won't matter. we'll be floating on our laptops before being swallowed by basilisk
i think i would not go back > 8yrs (and i havent' with the t480s) -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 20:02:57 JST jae
@p @TeaTootler @laurel @m0xEE i couldn't remember when it was introduced. it was really handwavy thingy in python. then again ive only written .rb since ~2011 so maybe i glazed over it for years.
yes it doesn't seem good in go. -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 19:57:04 JST jae
@laurel @m0xEE @TeaTootler @p python set the course for yield. we use it in ruby too.
Husky_1744368955603_UEY4Z4OXJ9.jpg -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 19:54:38 JST jae
@phnt @TeaTootler @m0xEE @p they're also shoving mcp into the system now for all the .ai worshippers. gitea has really went commercial. forgejo isn't much better but im not sure what you mean its nearly unusable. ive got forgejo running fine for about a year. ci/cd is nearly always building and deploying for our our group.
we tend to work on latest go so version bump and new patterns aren't big problems. -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 14:03:43 JST jae
@dcc @TeaTootler @m0xEE @p
informational infographic
image.png -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 13:51:19 JST jae
@p i don't get out of bed for less than 16 threads these days. maybe in 1995 my expectations were less -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 13:51:13 JST jae
@TeaTootler @m0xEE @p
> no math coprocessor
yes. dx models have on-pcb math-coproc. sx can't do float -
Embed this notice
jae (jae@fsebugoutzone.org)'s status on Friday, 11-Apr-2025 03:25:34 JST jae
warning, read side-effects on box before consuming.
image.png