@rixx Some instances hide their version.txt using htaccess/nginx.conf,others have only a outdates version.txt because of Cloudflare Cache but have a updated instance.Therefore the list can only be correct if I check every instance manually.And I don't know why I should remove your instance from the list.I have no problem with it and I also have no problem with older instances in general.I don't know what you dislike that much about my post.

@rixx I have no expectations but as it would be quite difficult to write a automatic version checker I check every instance for updates manually a few days after publishing a new version and so I notice when instances don't receive updates for months.I like it when instances are up to date because else people often complain about bugs which have been fixed for months but I list every public instance that exists.The list is sorted by versions so it shouldn't be a big problem.

@jr @rixx Thanks for notifying me that the instance has finally received an update.It's now updated on the instance list but please update your nginx.conf so that new pages work.They throw error 404 for me.

We've just released 2.3.4 with the following changes:
- Add support for Mastodons new BlurHash
- Add example config for the lighttpd webserver
- Add debug option to config.ini.sample
- Load link previews without additional API requests
- Bugfix: YouPlay can't load any video anymore
- Bugfix: Fix XSS in the textarea autocomplete
- Bugfix: Some bugs with media thumbnails in the profile
You can download it from notabug.org/halcyon-suite/halc

Important: There was a bug in 2.3.3 which sent answers to other posts as completely new posts without context.We've released a and recreated version 2.3.3.Please reinstall Halcyon 2.3.3 as soon as possible!You can get it as always from notabug.org/halcyon-suite/halc

We've just released 2.3.3 with the following changes:
- You can now copy&paste media into the compose field
- You can now drag&drop media into the compose field
- Video and audio (if supported by serverside) uploads supported
- Uploaded media files can be sorted
- Captions can now be added to media files
- Bugfix:Uploading a second picture overwrites the first
- Bugfix:Automatic dark mode detection doesn't work
You can download it from notabug.org/halcyon-suite/halc

@snder That would be great.The login page code is in /login and is completely separate from the logged in area,that should make it easier for you.It would be cool if you could make it look like web.archive.org/web/2018011500 but in Halcyons blue.The content should come from the public timeline of a instance which the Halcyon instance admin can set in the config.ini

@inditoot @snder A PWA won't come that soon.It would need a rewrite of the whole code base without any big improvements.

@snder The project homepage halcyon.social already is responsive.A new login page which will of course look exactly like a old version of the birdsite is planned,too.Another person said that he'll create it but then he went away and his instance isn't reachable anymore so I think I'll have to do it myself in some weeks.

@snder A responsive version has been on the todo list for a very long time but it's much work as pretty much every part of Halcyon has to be optimized.That will take much time so I had to postpone it often.But I have much time over the next weeks so maybe it will come sooner than initially planned.I'm not sure.

We've just released 2.3.2 with the following changes:
- Add management for blocked and muted accounts in settings
- Add management for follow requests in settings
-> Update your nginx.conf or Caddyfile
- Add Catalan translation
-> Enable the ca_ES locale
- Add profile sidebar to notifications page
You can download it from notabug.org/halcyon-suite/halc
-> Still miss your language?Help translating at translate.nikisoft.one/project

@marcus Oh sorry,I just noticed that I've completely forgotten this message.The problem seems to come from your Pleroma instance.Please edit your nginx.conf and remove the Access-Control headers from it.They've been set by Pleroma itself for a few months and if these headers are duplicated (one time from Pleroma and one time from nginx),that will cause bugs with clients on third-party domains (other subdomains are enough for the bug to appear).

@marcus Mastodon sets a session cookie (which counts as third party because Halcyon is on another subdomain) but I'm not sure if Pleroma has this session cookie,too.If that gets blocked,that doesn't matter anyway because Halcyon gets a OAuth Token at login which is used to authenticate you at Pleroma so that the session cookie is ignored here.

@marcus I think that shouldn't be a bug of your Halcyon instance.I tried logging in with my private account and everything worked fine.If there's a connection problem between Halcyon and Pleroma,it won't let you login at all.I think your adblocker plugins could block the connections to your Pleroma instance.Login works through Halcyon but all requests after that are directly from the browser to Pleroma which could be detected wrong as thirdparty tracker.

@jeroenpraat Great!That means that it's really a bug in PHP itself.I think I should add this to the troubleshooting documentation page.

@snder That's just an issue with your cache.Hit CTRL+F5 and everything will be alright.

@jeroenpraat That's a really weird issue but if it has worked before,it can't be caused by the translation file in the repository.This doesn't happen for the first time but it always only happen on one instance and I think not always.Normally I recommend downloading the messages.mo file for the buggy language again and replace it on the server with the new one (even if it should be exactly the same) but I can't remember if that helped in the past.Maybe it's a bug in PHP 😕

@tsia Yes,new strings are only added to the translation files every 2.X.0 release because the work would be quite big else.

Show more
W3C CSS Working Group Mastodon

Mastodon server for anyone interested in CSS or general web development