stefan / is on Nostr

"2835e440cbecab707db6d8ffdf0a7b6f1ef7493313df17d4b1d99389fbb674fb7ce7a6bfa70b2b8a84f04f1ddc0d970483b1009fa4ec44c1fc7e7888525a12f6"

Last Notes

2023-03-12 20:34:01

- reply

with traefik you can use some kind of config discovery backend like consul etc..

2023-03-12 20:32:09

- reply

ah ok but you‘d still have to know the name, got it. yeah caddy is cool..

2023-03-12 10:00:36

- reply

can it discover the docker instances like traefik does?

2023-03-10 11:49:00

- reply

nifty

2023-02-24 13:23:19

in case anyone is in vienna next month.. https://www.eventbrite.at/e/ai-meetup-dotbite-meets-talentgarden-tickets-557588330707 #chatgpt #vienna #devs #ai #meetup

2023-02-20 06:52:34

- reply

bring them on. fip is the best. a product of oldschool cultural politics / top-down planning and still punk - i don't know how they do it

2023-02-19 15:39:05

- reply

cool, give it a try. freebsd supports c++20 afaik

2023-02-19 10:13:03

- reply

interesting. and edge case of binary compatibility between linux and freebsd?

2023-02-17 18:39:01

- reply

also, federated training is a possibility but makes everything a bit more complicated. i guess the most important question is: what features turn out to be predictive. maybe the protocol itself can be leveraged more (network/metadata).

2023-02-17 18:30:49

- reply

#[3] ’s approach seems reasonably lightweight and could be added to any relay. classifying using larger models and frequently retraining them would be heavier but surely possible on larger nodes.

2023-02-17 17:40:29

- reply

what’s your take on content filtering for relays? possible approaches: a) mitigation through POW b) based on network features c) based on content features .. n) any combination of the above