God I hope this is a bit

Are these from a video game or Terry Pratchett’s Night Watch books?

I’m aware they’re not using a generic model, but that’s not much better. Current custom-made models still fuck up significantly more than humans, and in less predictable ways.

Even if their custom model is slightly incorrect 1% of the time, that’s still a major problem in critical systems like those.

Legacy COBOL code is largely used in critical systems like those of banks and airlines. What could go wrong with having that code rewritten by stochastic parrots who get programming answers wrong half of the time?

Me when I start seeing sickoposting in my default Lemmy comms

Interesting demo! Does this use the user agent string for identifying clients?

Oh I mean, sure, but I don’t think IP logging is the main privacy concern with spy pixels.

I’m assuming this trick uses the user agent string and other request metadata to identify clients. Even if it didn’t recognize Jerboa as a client, it did guess that I was on mobile. That’s not possible just by tracking IPs, unless they’re cross-referencing it with other datasets. Also, I was on VPN anyway, so the IP would have been useless.

It should be possible for clients to obfuscate/fake the metadata of image requests to make tracking with spy pixels less effective.

Can countermeasures be implemented in the clients to mitigate privacy risks, while not having to proxy images?

Interessante, grazie della spiegazione. Sembra che in questo caso la semplice compatibilità di Akkoma con Pleroma abbia fatto sì che si sia involontariamente portata dietro parte della comunità già esistente su Pleroma. Coltivare una comunità di un certo tipo è una vera impresa…

Detto questo, se lo strumento in se non è neutro, mi chiedo quali siano le caratteristiche o feature che attirano certa gente piuttosto che altra.

Akkoma è una fork di Pleroma, non so esattamente quale siano le differenze ma suppongo siano simili. Secondo te cosa rende Pleroma/Akkoma attraente per quelle comunità?

Capito, grazie della risposta. Non ho trovato i contenuti di questa istanza direttamente sulla nostra feed, l’ho solo vista segnalata in giro. Tra l’altro essendo un’istanza Akkoma e non Lemmy l’unico rischio che c’è è che i suoi utenti postino su comunità esistenti e (si spera) moderate.

L’indirizzo dell’istanza è sotto lo spoiler (ATTENZIONE: …), dovrebbe essere mostrato quando ci clicchi sopra. Non funziona?

Got it, thank you!

I’m seeing the same bug, and I don’t see a github issue for it. Wanna create one?

Buono a sapersi, vediamo come va…

Se avete tempo di postare aggiornamenti sulla performance e il consumo di risorse dell’istanza, ogni tanto, a me interesserebbero. Mi piacerebbe ad un certo punto mettermi su un’istanza personale, per cui farebbe comodo avere termini di paragone.

Ottima notizia, grazie per il lavoro che ci mettete.

Avete notato miglioramenti particolari di performance del server? Ho sentito parlare di riduzioni drastiche della grandezza del database, avete visto qualcosa di simile o no?

Dal lato utente intanto sembra che l’ordinamento “Hot” sia stato finalmente aggiustato, non vedo più post vecchi di mesi.

Oh cool, didn’t know about the plugins.

Agreed, standards are what make the Fediverse possible. Rendering posts from other platforms is already messy: we’ve all seen the posts coming from Mastodon where the title is the whole body of the post, cut at the character limit. If Lemmy starts doing its own Markdown flavor it would further degrade the integration with other Fediverse platforms.

Which other web services support Markdown formatting and also single line breaks? Reddit, for example, didn’t…

Since AFAIK the main reason for this choice in standard Markdown was to make the raw .md files more readable, I can see how this isn’t necessary in Lemmy. I still see two reasons not to change this though:

• Effort: forking and maintaining a markdown rendering library just for lemmy would take a ton of effort for a pretty small usability improvement. The dev team is already small and overloaded with work, this doesn’t seem like a good use of their time.
• Consistency: each website having its own flavor of Markdown syntax would be pretty chaotic for users. Right now you can learn basic Markdown once and use it on Reddit, Lemmy, Github, etc. If every website did it their own way you’d have to remember all the little differences, it would get messy.

This is not a missing feature in Jerboa, it’s a design choice in the Markdown syntax. It’s done so that one can break up long lines in the .md file without affecting the rendered page. Markdown is a standard, and Jerboa uses an existing tool to format posts. In order to make this work for Jerboa the devs would have to break compatibility with Markdown and create their own rendering tool. They’re most likely not going to do it, and I don’t think they should.

That’s not a problem, though, because you can already create single line breaks in Jerboa, using standard Markdown. All you have to do is add two spaces at the end of your first line, where you want your line break to be. So, if I write down:

This is a line<space><space>
This is another line

this gets rendered to:

This is a line
This is another line

There are other ways to create line breaks in Markdown:

• Using an HTML <br/> tag
• Using a backslash \

but they’re not supported by all renderers. For example: the <br/> tag works in Jerboa, but not in the web UI. Double space works for me in both.

Or just https://pluralistic.net/2023/07/24/rent-to-pwn/

He has a mirror of his blog on his own website without paywall. Not sure why he still publishes on Medium too, visibility I guess…