luketic.de

4. December 2024

Why is Google punishing me?

Google de-monetized this blog when it was still under blog.icod.de, because the top level domain icod.de didn’t have ads, because it’s my company’s website, and also barely any, what Google calls, content. But the blog has been up for years and well linked and has seen its impressions and I helped many people with my blog posts.
But now there are barely any impressions or search result clicks.
The number of indexed pages also dropped by about 90%.
Since about a month ago it’s almost flatlined.

So why is Google punishing me?

Nothing changed except the domain, and I’ve added the Google Sitekit plugin.

Am I not right wing enough?
Am I criticizing Google Meta Microsoft too much?

What is it Google, that you’re punishing me for?

#Google #exclusion #punishment #pagerank #seo #search

3. December 2024

Remix JS: Does Remix use process.env or import.meta.env?

Does Remix use vite’s import.meta.env or process.env?

The answer is, both. However it’s better to rely on vite’s import.meta.env because of 2 things:
1. Only VITE_ prefixed environment variables are imported
2. It’s also available in the non-SSR context, while process.env is a NODE thing only and not propagated to the browser.

So what does that mean?

You can have a
.env.development
and a
.env.production
file in the project root and add things like

VITE_HTTP_ENDPOINT=http://localhost:8080/api/v1
VITE_OIDC_AUTHORITY=https://my.id.domain.tld

1 2	VITE_HTTP_ENDPOINT=http://localhost:8080/api/v1 VITE_OIDC_AUTHORITY=https://my.id.domain.tld

and you can access those variables with e.g.

const httpEndpoint = import.meta.env.VITE_HTTP_ENDPOINT
const oidcAuthority = import.meta.env.VITE_OIDC_AUTHORITY

1 2	const httpEndpoint = import.meta.env.VITE_HTTP_ENDPOINT const oidcAuthority = import.meta.env.VITE_OIDC_AUTHORITY

but this also gives you access to other variables, which are present by default

{
  BASE_URL: '/',
  DEV: true,
  MODE: 'development',
  PROD: false,
  SSR: true,
}

{

BASE_URL: '/',

DEV: true,

MODE: 'development',

PROD: false,

SSR: true,

}

#vite #remix #env

15. November 2024

Gestern WhatsApp installiert heute Werbeanrufe

Gestern habe ich WhatsApp installiert und meine Telefonnummer angegeben und nach wenigen Minuten wieder gelöscht, heute schon der 2. Werbeanruf.

#Spam #WhatsApp #Werbung

25. October 2024

Kleinanzeigen Kreis Göppingen

Die letzten Tage habe ich an einer Kleinanzeigenplatform für den Kreis Göppingen gearbeitet.

Sie wurde mit ent, gqlgen, mysql im Backend und react mit vite und relay, flowbite UI und tailwindcss im Frontend geschrieben. Als Authentifizierung nutzt sie Zitadel als OIDC IDP.

Man kann sie finden unter:
Kleinanzeigen Kreis Göppingen

24. October 202424. October 2024

Uncaught RangeError: date value is not finite in DateTimeFormat.format()

Playing with Flowbite React and their Datepicker component, I had data coming from the backend in this or similar form:

{
	"data": {
		"posts": {
			"edges": [
				{
					"node": {
						"id": "c57e4ea8-072e-4057-974f-bfb369504a57",
						"createdAt": "2024-10-24T12:21:20Z",
						"updatedAt": "2024-10-24T14:03:16Z",
						"title": "Jobangebot mit jemand ohne Namen",
						"body": "Dies ist ein Jobangebot von jemandem ohne Namen",
						"expires": true,
						"expireTime": "2024-10-31T23:00:00Z",
						"category": {
							"id": "df84950d-742b-4d07-9f11-04b8964bcb36",
							"title": "Jobangebote"
						},
						"profile": {
							"id": "0ce6ee59-4ebf-42cf-9c3a-69cf5e826b0b",
							"sub": "288686157058342913",
							"name": ""
						}
					}
				}
			]
		}
	}
}

{

"data": {

"posts": {

"edges": [

{

"node": {

"id": "c57e4ea8-072e-4057-974f-bfb369504a57",

"createdAt": "2024-10-24T12:21:20Z",

"updatedAt": "2024-10-24T14:03:16Z",

"title": "Jobangebot mit jemand ohne Namen",

"body": "Dies ist ein Jobangebot von jemandem ohne Namen",

"expires": true,

"expireTime": "2024-10-31T23:00:00Z",

"category": {

"id": "df84950d-742b-4d07-9f11-04b8964bcb36",

"title": "Jobangebote"

"profile": {

"id": "0ce6ee59-4ebf-42cf-9c3a-69cf5e826b0b",

"sub": "288686157058342913",

"name": ""

}

]

}

aka

"expireTime": "2024-10-31T23:00:00Z",

1	"expireTime": "2024-10-31T23:00:00Z",

React is a bit of a cringy special child. Angular, no problemo. Vue, no problemo.
Anyhow.

I have to set defaultValues in a React-hook-form form, because React is special with controlled and uncontrolled components.
aka

type AdminPostEditFormValues = {
    title: string,
    body: string,
    expires: boolean,
    expireTime: Date,
}
    const {control, handleSubmit, watch, formState: {errors}} = useForm<AdminPostEditFormValues>({
        defaultValues: {
            title: data?.posts?.edges[0]?.node?.title,
            body: data?.posts?.edges[0]?.node?.body,
            expires: data?.posts?.edges[0]?.node?.expires,
            expireTime: dayjs(data?.posts?.edges[0]?.node?.expireTime).toDate() || dayjs().toDate(),
        }
    })

type AdminPostEditFormValues = {

title: string,

body: string,

expires: boolean,

expireTime: Date,

}

const {control, handleSubmit, watch, formState: {errors}} = useForm<AdminPostEditFormValues>({

defaultValues: {

title: data?.posts?.edges[0]?.node?.title,

body: data?.posts?.edges[0]?.node?.body,

expires: data?.posts?.edges[0]?.node?.expires,

expireTime: dayjs(data?.posts?.edges[0]?.node?.expireTime).toDate() || dayjs().toDate(),

}

})

So, I’m using dayjs for my date/time stuff, and this line essentially means, parse the Date before assigning it to a form value (or create a new Date(), because React and controlled/uncontrolled forms is not a happy story).

            expireTime: dayjs(data?.posts?.edges[0]?.node?.expireTime).toDate() || dayjs().toDate(),

1	expireTime: dayjs(data?.posts?.edges[0]?.node?.expireTime).toDate() \|\| dayjs().toDate(),

TL;DR: Parse the date value coming from the backend into a Date object. e.g.

Date.parse("2024-10-31T23:00:00Z")

1	Date.parse("2024-10-31T23:00:00Z")