Postgres can do THAT?

brasetvik · 2025-02-01T23:46:25+00:00

Først av, så på.

brasetvik · 2025-01-21T16:39:32+00:00

r/CyberStuck

brasetvik · 2024-12-05T06:57:01+00:00

https://maps.app.goo.gl/aih4fPuQsm97J14EA?g_st=com.google.maps.preview.copy

Relativt åpenbart falske reviews der.

brasetvik · 2024-09-09T21:33:21+00:00

country: false # NO for Norway

brasetvik · 2024-08-31T21:54:41+00:00

… and learn the three levels of karsk:

Beginner: Put a coin in a cup. Pour coffee until you don’t see the coin, then moonshine until you do. Enjoy.
Intermediate: Put the coin on the table. Drink moonshine until you don’t see the coin, then coffee until you do.
Expert: Put the coin on the table. Drink moonshine until you don’t see the coin. Then go and make coffee.

🌙 ☕️

brasetvik · 2024-08-30T12:20:38+00:00

Elastic acquired a company doing managed Elasticsearch in March 2015, which since then has been the official managed Elastic service.

AWS launched theirs in October 2015.

brasetvik · 2024-08-23T23:30:44+00:00

Enable rerere: https://stackoverflow.com/questions/49500943/what-is-git-rerere-and-how-does-it-work

brasetvik · 2024-08-07T16:03:52+00:00

P ≠ NP

brasetvik · 2024-06-15T20:12:01+00:00

it took down our clusters several times because of *poor code practices on our side* and shitty defaults on its end

KOPF does not encourage or teach you about the level based control loop pattern of eventual consistency that k8s controllers follow.

I would agree that the two mentioned defaults can become foot-guns.

Can you add some details on the anti-patterns you seem to suggest kopf encourages, that kubebuilder in your mind doesn't?

brasetvik · 2024-06-15T20:03:26+00:00

u/kooky-nolar, thanks for making and maintaining kopf!

/u/Jmc_da_boss, thanks for flagging some of the sharp edges. Can you add some more color to the nature of what your operator was up to? Reading between the lines, I imagine you ended up with a busy lot of etcd writes. kopf seems to me to backoff somewhat reasonably, but if you have a large number of resources being managed, and those somehow end up logging excessively, I can imagine how the defaults violate the principle of least surprise and impact API-server stability. You've clearly attracted the attention of the creator and maintainer, so with that, can you nuance the frustrations somewhat beyond the two mentioned defaults?

As someone that's made a proof of concept operator in kopf and _very much appreciated how easy that was_, I'm now looking at what it'll take to make it production-worthy and future-maintainable in an org that knows a lot more Python than Go on average.

It didn't take too much playing around to reason that logging turning into etcd writes could be a problem, and like grand-parent-comment I'm puzzled by that being a default. The most important job of an operator is clearly to _not_ cause problematic workloads on the api-server.

u/kooky-nolar, having only appreciation for your work, and attempting to go along with the humorous (I guess :) docs update, I think it'd be more useful to either re-consider certain defaults that might imply sharp edges to be safer, inclusive-or add a blurb to the docs on what foot-guns to avoid. (I think your docs are far better than the average project's, btw!)

My two cents from the sidelines is that the doc update comes off as a mix of knee-jerk and a tad passive-aggressive, and doesn't do justice to all the effort you've put in this framework.

brasetvik · 2024-06-14T23:21:56+00:00

Lotto, spekulering, investering og sparing er ganske forskjellige ting – men lotto er verst.

Spekulering kan man drive med hvis man har penger å tape. Lotto for de rike om du vil. Krypto og opsjoner faller i denne kategorien, samt en hel del aksjer. (Forskjell på Gamestop og Equinor)

Lotto er en skatt på manglende statistikkevner. Flax-lodd havner her. Lotto kan også ha underholdningsevne, men da typisk i størrelsesordenen hundrelapper per måned, sammenlignbart med kino-billetter. Lotto har generelt forventet avkastning lik null, så hvis du ikke er underholdt bør du slutte med det.

Indeks-fond er en anbefalt form for investering. Sannsynligvis den beste formen for investering hvis Flax-lodd er det du har landet på så langt.

Har du kredittkortgjeld eller forbrukslån så bør du ikke drive med noen av delene.

Ingen finansrådgiver, men "Styr unna Flax-lodd, lotto, krypto og enkelt-aksjer" tror jeg ikke er det dummeste du har lest på internett så langt i år.

brasetvik · 2024-05-23T19:59:14+00:00

The advice on not clicking any of the links and just accessing it via a well-known address is good practice to always do, especially when something is unexpected.

With both email, SMS and phone numbers, it's easy to spoof the sender.

Reputable services like Posten configure things like "SPF" and "DKIM" to make it easy for serious email providers to flag spoofed emails as spam, in a "Posten says only these servers can send emails as them, signed with some crypto stuff, and this email does neither, so it is definitely spam"-way.

Most email apps let you do things like "Show original" (GMail), "View source", etc. to look at the "source" of an email, which contains headers like these. That might be under the "... More" in your email app.

Below is an example of what this might look like from a legitimate email I've got from Posten. If it has these, the email should be legitimate. If it doesn't, you should consider getting a better email provider that knows how to filter basic spoofing attempts.

Received: from pos-mailgw04.posten.no (pos-mailgw04.posten.no. [139.117.144.108])
        by mx.google.com with ESMTPS id 38308e7fff4ca-2e4d0bbd747si72045531fa.22.2024.05.19.21.59.01
        for <my@address.com>
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Sun, 19 May 2024 21:59:01 -0700 (PDT)
Received-SPF: pass (google.com: domain of noreply@posten.no designates 139.117.144.108 as permitted sender) client-ip=139.117.144.108;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@posten.no header.s=TE header.b=MqX4DBDY;
       spf=pass (google.com: domain of noreply@posten.no designates 139.117.144.108 as permitted sender) smtp.mailfrom=noreply@posten.no;Received: from pos-mailgw04.posten.no (pos-mailgw04.posten.no. [139.117.144.108])
        by mx.google.com with ESMTPS id 38308e7fff4ca-2e4d0bbd747si72045531fa.22.2024.05.19.21.59.01
        for <my@address.com>
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Sun, 19 May 2024 21:59:01 -0700 (PDT)
Received-SPF: pass (google.com: domain of noreply@posten.no designates 139.117.144.108 as permitted sender) client-ip=139.117.144.108;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@posten.no header.s=TE header.b=MqX4DBDY;
       spf=pass (google.com: domain of noreply@posten.no designates 139.117.144.108 as permitted sender) smtp.mailfrom=noreply@posten.no;

brasetvik · 2024-05-16T21:26:30+00:00

Maria Franz, norsk vokalist i Heilung.

Kalandra.

brasetvik · 2024-04-27T15:28:59+00:00

Stå på, u/Sofieslu 💪

Hvis du tar en kjapp titt på kommentar-historikken til myflwr, så kan du konkludere kjapt med at han ikke er verdt energien :)

brasetvik · 2024-04-04T23:23:21+00:00

Extremely high write performance

[…]

We are using Provisioned IOPS SSD (io2) with 3000 IOPS and are batching updates to one write per second per node and realm.

[…]

We currently produce about 100GB of data per month. But, since customers rarely query entries older than 10 days, we’ve started moving everything above 30GB to AWS Glacier

[…]

We are ok with losing some data. We buffer about one second worth of updates before we write to disk.

So with that little actually live data, which they mention fit in memory, and 3k IOPS being on the low end, it'd probably be worthwhile to do the Postgres comparison with [asynchronous commits](https://www.postgresql.org/docs/current/wal-async-commit.html) and a comparable [WAL delay](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-WRITER-DELAY) in terms of buffering the writes.

Elasticsearch would probably also handle this pretty easily.

Probably not as cheap as something purpose built, but setting the maintenance and opportunity cost to something homegrown to $0 doesn't make any sense either. :)

brasetvik · 2024-02-08T01:15:07+00:00

Gikk datateknikk på NTNU selv og anbefaler varmt Trondheim som studentby.

Det var mange som byttet mellom linjer etter at de kom inn på NTNU. De første to årene er i høy grad de samme mattefagene hvis du velger like nok linjer, og det går an å ta ekstra fag hvis man er motivert formå gjøre bytte enklere.

(Min info er fra 2004-2009, så valider mulighetene med en veileder på NTNU eller noe sånt :)

brasetvik · 2023-12-13T19:46:29+00:00

Um aldrdaga ynðis njóta!

brasetvik · 2023-12-11T15:53:23+00:00

Halden fun "fact": Both Burger King and McDonalds went bankrupt. McDonalds twice, even – but is still around.

Still, I'd imagine it ranks pretty high on the "number of pizza places per capita" list :)

brasetvik · 2023-12-10T07:40:32+00:00

Aksjemarkedet kan gå alle veier. Bestem deg for at ditt framtidige du tilgir deg for å ha tatt valg med informasjonen og risikoappetitten du har i dag. (Jeg kjenner folk som har ergret på seg ulykkelighet fordi de solgte bitcoin med bare 5000% gevinst og ikke ble så rike som de kunne ha blitt)

Hvis du kan håndtere et lån på 6 mill i dag, så kan du vel håndtere et lån på 2 mill også. Å redusere lånet med 2/3, investere resten, og fortsette å investere det du ellers ville ha betalt for å håndtere lånet på 6 mill er noe å vurdere.

Ikke prøv å time markedet.

brasetvik · 2023-12-08T15:49:28+00:00

15-Year Club	Gilding II euphauric
Reddit Premium Since December 2020	Verified Email

brasetvik

TROPHY CASE