veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

233
active users

#json

6 posts6 participants0 posts today

Does anyone have a good way to create a reasonable visual layout for a mastodon archive of posts? Say like a styled rss feed with post text and thumbnails, and maybe paginated. I'd like a section on my website with at least some of the posts from my other masto acct, searchable via Grav search.

🎉 Behold, a 12-minute joyride through the riveting world of "Packed Data in Haskell" — because when you're not busy serenading code with your 🥁 musical genius, you're crafting verbose essays on data serialization. Spoiler alert: It's just yet another attempt to sound fancy while discussing #JSON and #XML. 🚀
arthi-chaud.github.io/posts/pa #PackedData #Haskell #DataSerialization #CodeJoyride #HackerNews #ngated

Arthi-chaud · Packed Data support in HaskellPacked Data x Haskell = Portable(Type-safety + performance)

#Blogger so: Hübscht eure #Blogs auf und optimiert sie für #AI mit #JSON.

Andere Blogger so: Hört mit dem Bullshit und den ausgedachten JSON-Formaten auf.

Blogger früher so: Liebes Tagebuch, heute war ein Scheißtag.

Wo sind wir Blogger denn falsch abgebogen? Wir wollten auf SEO verzichten und machen nun AI-O? Wozu? Um dem Ami Google noch mehr Daten zum Fraß vorzuwerfen? Wer sagt denn, dass mir das mit meinem Blog irgendwas bringt?

PostgreSQL Antipatterns: создаем JSON из строки

Я уже не раз поднимал в статьях тему [не]эффективной работы с json[b] в PostgreSQL - и как его лучше превращать в выборку , и как можно "транспонировать" . Сегодня же рассмотрим некоторые возможности по его генерации на стороне базы .

habr.com/ru/companies/tensor/a

ХабрPostgreSQL Antipatterns: создаем JSON из строкиЯ уже не раз поднимал в статьях тему [не]эффективной работы с json[b] в PostgreSQL — и как его лучше превращать в выборку , и как можно «транспонировать» . Сегодня же рассмотрим...

Using Jenkins deeply has reminded me that one of the pros of the original REST API intent was "You don't have to write your HTML handling logic twice." As in: if you use honest-to-God forms, and those forms access your app via your own REST API, you aren't writing one handler for form inputs and one for API calls (which had been the style at the time when REST hit the scene).

Nowadays, it's pretty much all JSON under the hood (i.e. barely anyone uses raw forms anymore; if you have a form on a page, it's bundling its fields into JSON and making an XmlHttpRequest), so this benefit is overlooked.