Hey #flohmis! I just installed the new #yunohost package #flohmarkt 0.12.1~ynh3.

The flohmarkt code stays the same. @grindhold@23.social researched the issue that after upgrades to flohmarkt the clients needed to force reload the frontend.

To circumvent the problem nginx now adds a header to control caching. **Thanks for the PR to the yunohost integration repo by @grindhold@23.social!

The testing environment of #yunhost found an issue with using add_header in nested nginx-configurations and delivered a reference: https://www.peterbe.com/plog/be-very-careful-with-your-add_header-in-nginx

Thanks to the great work of all the yunohost contributers for that great testing environment!

The newer package can be updated or installed from the yunohost app store.

From the download counter on the release page at codeberg I estimated that there are between 30 and 40 #flohmarkt instances out there running on #yunohost.

(Who uses ZIP ? Well, the yunohost integration does and the counter went up by the numbers shortly after publishing the latest update to the yunohost app integration.)

On the wiki we have a list of ~20 flohmarkts. The list is meant for users to choose an instance and for admins to look for other flohmarkts to federate with.

I'd like to invite everybody to drop us a line to add your flohmarkt to the wiki: either as a codeberg issue or as a fedimessage or fedipost or on #flohmarkt IRC.

And even if you'd not like to be on the wiki page: federate with others to make your small ads more visible.

#Federation enables that #SmallAd​s show up on the other instances an instance is federated with directly. This gives every small ad some more reach.

My impression is that federation is extremly important to make the flohmarkts more successful as an alternative to the well know centralized services.

I opened an issue to discuss how to make federating easier without forcing anyone to share more data with the world than they do with the actual version of flohmarkt.

Just updated the #yunohost package of #flohmarkt to the latest release 0.12.1. All the new features of 0.12.0 are included.

Thanks to the flohmarkt developers and supporters for their ongoing work and congratulations to the nlnet grant!

https://apps.yunohost.org/app/flohmarkt

Hey #flohmis - fellow #flohmarkt users!

Just updated the #yunohost app for flohmarkt to 0.10.1. Quoting @midzer@chaos.social and @grindhold@23.social :

• small fixes for 0.10.0
• accessibility refinements
• few bugfixes
• performance improvements for start page

On my local flohmarkt I added a lot of items, got a request for one of it and welcomed two new users.

• Selfhosting? yunohost
• Craiglist, kleinanzeigen, and the like? flohmarkt

Hey #yunohost admins ! Just upgraded my #flohmarkt on yunohost to version 0.10.0. Are you running a #fediverse small ads service, too?

If not try flohmarkt and if you're already running version 0.8.0 look out for the upgrade being soon available on the yunohost app store.

Well, I'll give it a try: https://forum.yunohost.org/t/nextcloud-aio-yunohost/36056.

#yunohost should provide the nginx (and let's encrypt certificate) and I'll look at nextcloud-aio (again) and see how I like it.

@jimbolaya@social.linux.pizza @hermankopinga@mastodon.social

Follow-up to this note:

I decided to test whether #GotoSocial would work on the #RockPro64 using the current instead of the legacy #Armbian kernel before risking problems upgrading my production #yunohost.

I have a similar testing setup: old mechanical drives instead of SSDs, a different PCIe SATA controller, an additional eMMC.

The additional eMMC I need to boot from, because for some reason the PCIe SATA ctrl didn't work, when u-boot initializes the controller before the kernel.

Installing the current kernel on my testing setup I found it not working: no console on hdmi, no network. Forgot to install the newer dtb (device tree binary) as well.

With currrent kernel and dtb from #Armbian installed the system booted half of the times I switched it on. Asking around on the rock64 chat I met Dragan Simic who greatly helped me to get further down the #RabbitHole…

On my #yunohost I tried to update #gotosocial from 0.17.4~ynh1 to 0.18.1~ynh1 and the update failed.

GotoSocial just showed some cryptical error messages when started.

@dumpsterqueer@superseriousbusiness.org traced the problem back to a changed lib version used in the new GotoSocial version and the developer of the lib answered my #linux kernel would be too old.

The old #armbian legacy kernel is running, because … I don't remember.

I need a kernel update for my #rockpro64.

Down the #RabbitHole…

Thanks a lot for all the work that went into the new #flohmarkt release 0.8.0!

The #yunohost app is upgraded as well and will soon appear in your update list.

If you can't wait: yunohost app upgrade --force flohmarkt.

@grindhold@23.social @midzer@chaos.social @stdevel@chaos.social

Sending and receiving large or confidential files via #email is difficult: the size often is not accepted by the recipient and confidential content might be transported unencrypted and via any number of relaying smtp servers.

I used psitransfer for #filesharing for a while, but it doesn't offer an upload protection for multiple users and it doesn't support handing out upload tickets to people that I'd like to invite to send me a file.

I'm now testing lufi on a #yunohost. #lufi offers the integration into an existing user database (like in the case of yunohost openldap) and it allows users to invite third parties to send them files using a time limited upload ticket.

It's time to #upgrade my #yunohost to version 12. I started drafting and testing a plan on how to get through it without any unwelcome surprises.

If you're interested in upgrading your own yunohost: you're welcome to look at my draft (yes, I didn't write it with sharing in mind ).

Any feed back is welcome! When I'll done I'll publish the final version as a reply to this post.

Upgraded my testing #yunohost vm successfully to #bookworm.

My production #yunohost is in some places modified and actively being used for #email, #matrix and some other things by friends+family.

To get an estimated of the time needed to upgrade it and find any issues beforehand I setup a testing board and copied the installation over to test the upgrade.

Just released #flohmarkt 0.6.1~ynh1 for #yunohost. There are many new features - thanks for the impressing developments of the last two month to @grindhold@23.social and @midzer@chaos.social and all the other contributors!

• instance name is shown as page title of browsers
• visually reworked item page
• most tabs now feature icons
• visually reworked item tags
• sticky menu
• search Users in Admin View
• most used tags are now shown as clickable buttons on the front page.
• user settings dialog is now split into tabs "Profile" and "Account". "Profile" is for the public-facing unproblematic stuff and "Account" contains the more dangerous actions like "delete account" and "change email" e.t.c
• item authors may now change the order of the uploaded images
• new couchdb database view in this release: yunohost upgrade will run initialize_couchdb.py automatically for you

After the release party yesterday for #flohmarkts beta 0.2.0 - first version tagged ever - we cleared out a last issue to make the beta release available for #yunohost. You'll find the yunohost soon in the app catalog - hopefully with the antifeature for alpha stage gone.

Actually the yunohost version is one step ahead of the official beta .

@read@blog.nigini.me I still microblog.pub even though I have two problems:

• memory is getting low on my host running all the services I'm using (4GB RAM)
• time needed to maintain microblog.pub beside #GoToSocial.

But it's still worth it I guess - otherwise I wouldn't have made the #yunohost package version 2 to keep #microblogpub available for yunohosts next version.

BTW: for yunohost a database integration would be great - there's always running mariadb.

Hey #flohmis! For #yunohost I configured #urlwatch for #flohmarkt to monitor the user database and not much later got an email informing me about a change .

My configuration templates can be found here as the three files named urlwatch*.

I looked at this again and found that the two notes requested very often from my #microblogpub are those that I 'pinned' that can be found at /featured.

The rest are paths pointing to information about this side. Maybe it has been some kind of #fedibot?

Here's a #fail2ban config that helped me blocking the IPs:

# cat /etc/fail2ban/filter.d/manual.conf 
[Definition]

# cat /etc/fail2ban/jail.d/manual.conf 
[manual]
enabled = true
bantime = 14d

This seems to lead to a jail which isn't connected to a logfile and for which manually added IPs stay blocked for 14 days.

To block IPs I used fail2ban-client -vvv set manual banip $IP which leads to

# fail2ban-client status manual basic
Status for the jail: manual
|- Filter
|  |- Currently failed:	0
|  |- Total failed:	0
|  `- File list:	
`- Actions
   |- Currently banned:	4
   |- Total banned:	4
   `- Banned IP list:	34.229.130.24 44.206.236.255 54.164.161.50 3.238.157.198

fail2ban is integrated into my #yunohost and even though it doesn't come with the greatest documentation I'm starting to love it.

Just installed the ynh8 #yunohost app integration on my flohmarkt.

I added an hourly check of the user database of #flohmarkt to send out an email notification for changes.

To enable admins through the web gui to change the address I added a configuration panel and while at it I put the setup URL for the initial setup of a new flohmarkt installation on the configuration panel, too.

Now it should be easy to install and initialize a flohmarkt instance by only using yunohosts web gui.