Sailfish Community News, 4th April 2024 - Blogs

Managed to fix the paging on my blog

5 Likes

@piggz, thank you very much, though a minor issue remains: The sorting order on page 2 is slightly broken, the entry on 2024-04-12 “Sailfish and Ofono - Day 12 - Feedback” is displayed last. There seems to be something special about this specific entry: AFAICS it is only this single entry which is “out of (sorting) order” and IMHO its date is also wrong; apparently it should be 2024-03-20 (instead of 2024-04-12).

1 Like

thanks, fixed. the date in the .md file somehow got commented out

2 Likes

Thank you!
Yes, this is working fine now.

Edit: Now I discovered that your first blog entry links to the RSS feed of your blog. The content of the very first entry on 04 Aug 2018 is available only there as part of the RSS feed! You may want to create a separate entry for this first blog entry of your (new) blog.

BTW, the first entry of @piggz’ blog reads as follows:


Welcome back to my blog after being offline for 2 years, since the drupal instance I was running was hacked with a crypto miner!

I finally got around to setting up a pico_cms instance on Nextcloud, so lets see how this works out!

So, what have I been doing lately? After I was successfully crowd-funded a new Amazfit GTS watch, i've polished up the support for it a bit more in Amazfish, my watch app for Sailfish, and while I was at it, I added basic support for a few other models which use basically the same protocol. These are untested, but should have basic functionality. A lot of the protocol implementation is taken from GadgetBridge, the android app, so, if GB supports it, I should be able to make it work.

https://openrepos.net/content/piggz/amazfish

Also recently we got some great support from the Lima GPU mesa developers in getting the driver to work on Sailfish. This was likely due to a compiler bug in the GCC version used on sfos, which meant the following code returnd 0 on sailfish, where it should be 4.

union u { int i; float f; }; int main(void) { union u test, test2, res; test.i = 4; test2.f = 1.0f; res.f = test.f * test2.f; printf("%f %.8x\n", res.f, res.i); return 0; }

The new improved driver brought a revived effort back to the sailfish port for the Pinephone, and the team have made great improvements over the last few weeks.

https://twitter.com/adampigg/status/1220440291397730307

BTW, I would be really interested to read a blog entry about your blog: Its software setup, why you decided to use Pico CMS and which other ways of publishing a blog you evaluated before making this decision, configuration details, what it took to make the “More Posts” link working as intended etc.

Background

I have been considering to start blogging years ago, but that idea always had low priority, because of the hassle I expect when setting up and configuring a software stack which allows me to blog. (BTW, “No”, I do not want to use a pre-configured “platform” somebody else runs, I want to control the software stack myself, though I may decide to run it at GitHub etc. in a self-controlled manner.) Additionally I always asked myself, “Who would be really interested in the stuff I think about and deal with”, but realising how eagerly I consume your and @flypig’s blog activities, I concluded that there may be sufficient interest. I already went through software evaluation a few times and the Hugo static site generator scored best for my criteria (others suggested Beautiful Jekyll and many more). Hence I am interested what advantages Pico CMS may have in comparison and how much effort it took you to employ a working software stack for blogging.

2 Likes

Im not sure it needs a full blot entry on the subject.
I too have heard about hugo, and if i was to set things up again, there would be a good chance I would use that. The reason I used pico cms, is that my site just runs on a nextcloud instance, and there was a pico_cms app available to make setting up the blog relatively simple. After several upgrades of NC, the pico_cms app is now unsupported, so I definitely wouldnt recommend this setup now, though, a standalone pico_cms may be better supported. I had to hack at the nextcloud app code to get it to work somewhat properly. Hopefully in the future there will be an upgrade to fix the compatibility, but until then, I wouldnt recommend a nextcloud/pico based blog.

1 Like

I’m not who you asked, but…

I chose Pico because I really, really wanted a flat file CMS, preferably without an admin frontend, and no client-side scripting.

Pico offers that, has humble dependencies and is very versatile with twig templating.
Pico CMS themes are much more than just appearance tweaks, the twig templates therein run most of what the site does.

I wasn’t ware of how important that would be, but in the end it wasn’t hard to learn.

Very humbly I could point you to my own theme and a few plugins I wrote (in PHP, not twig).

2 Likes

This topic was automatically closed after 30 days. New replies are no longer allowed.