@cha05e90

I checked the order issue of images and I could find why it happens. I will try to contact the developer through xoops forum to help me.

@all
Please report a this thread any issues you find.

Thanks for your help. Can you please recheck if there is now a button shown?

Dear all,
The amigans.net is back online, updated to the latest stable versions. Please, if you see any problems, feel free to inform me using this topic.

Thank you all for your patience. We count on your help to make amigans.net even better.

It seems that there are no topics to discuss, and that's sad. Anyway, I will be there...

I changed today the amount of characters the website show in each article. So, from now on only the first 600 characters of each post is visible.

Also I removed the "Read More" link and rename the "Original Post" to "Read More", which of course leads to the original blog post.

Hope these changes please you all guys.

I did a change today. I placed the "Source link" link above the main text and renamed it to "Original Post". Also I make it visible at the first page with the teaser list. That way, the user has the choice to go instantly to the blog post or continue reading it at the AmigaBlogs.net using the read more link.

What do you think on that?

@kas1e
I am open to proposals. This can be done, if people would like it. I could also show only the titles, and view a website with only titles. But this would be ugly and not helpful.

I believe that if you provide RSS content, you do that because you want someone to read the whole article from anywhere, and not only from your blog site (RSS readers for example).

Also, it is better for SEO to have as much content as possible, that will help search engines to lead readers to discover those articles.

Also, if someone prefers his blog not being aggregated by AmigaBlogs.net, then this can be done by asking from the contact form of the site. I can remove his content.

@broadblues, @ddni
The AmigaBlogs.net uses only the RSS from each blog to collect the articles. If a blog provides the full article, then that's what it stores.

Thank you all for your kind words.

I would like to inform you all about a new website we developed that we hope to help all of us.

More and more Amiga users/enthusiasts create their personal blog where they write interesting articles describing their beloved Amiga computer and guides on how to do things, based on their personal experience. Unfortunately, many of these articles are doomed to be invisible to readers, because it is lost among many other articles in the web. As a result the blogger loses his interest on writing new stuff.

We had the idea to create AmigaBlogs.net, were the visitor can read interesting articles and discover a blog that he never knew it's existence. We collect all the latest posts talking about Amiga computers and AmigaOS from various blogs. We do not want to steal anyone's work but to help the bloggers to promote their content to a global website with a broader and more targeted audience.

None of the included articles was authored by our team, as these are property of their respective authors and owners. That's why we provide in every single article the blog name with a link to it. We also provide the blog post original link at the end of the texts. We never edit the texts or the images of the articles, and this means that we are not responsible for their content and we do not totally agree with all of them.

The website works really nice on tablets and smart mobiles, so that you can read it anywhere you are. If you like our website and idea, use the contact form to inform us about your blog or propose what you would like to add or change.

I would also like to thank all the people behind AmigaOS 4.x development. They do a great work and they deserve our appreciation. I believe that they work hard to give us the best AmigaOS experience. And for that I am really grateful.

And we all have to support them and show our appreciation. Think about what we had 10 years ago and we are now. It doesn't matter if we don't have Libreoffice or the latest version of Firefox on our machines. It matters that the spirit is still alive and moving forward.

Most of you are right that maybe there were wrong decisions made. But those people are there and have to make decisions. Judging them is the worst thing we can do.

So support them, help them when they ask for it, make them know that we appreciate their work. And they will give us what they promised.

An other way, that I didn't still try, might be by using DropDav (https://www.dropdav.com/) services and WebDav Handler (http://aminet.net/package/comm/www/webdav-handler). It could work that way. Unfortunately, there is a limit of 150MB upload by the DropBox API.

Great stuff. Keep up the good work...

I am working on the updates, which are necessary for the best working status of the website. Also I want to prevent having any serious problems with the content. So the updates should be double checked before applied to the main website.

Sorry for the delay guys. I am doing my best to have everything sorted out as soon as possible.

Great news. Thank you for all your effort...

@saimo
It looks really good... I would love to play it. When do you believe this will be available?

I will do my best to be there and have a few pints with you mate. Keep up the good work...

Did anyone try these memory modules? Do they work fine with microA1?

I have the same problem, but as I mentioned on an other thread, these problems resolved when I installed timberwolf on an ffs2 partiton. Try that...

@tfrieden

I just tried the Timberwolf RC2 on a FFS partition on my X1000, without replacing any so lib. It seems that it doesn't have the timing/freezing prblem that I had with it on a SFS partition. It works faster now. Although it does this freeze but it lasts a few seconds.

- The bookmarks work fine on FFS partition too.
- Over links the cursor becomes a hand, something that doesn't happen if the timberwolf runs on SFS partition.
- The CPU isn't always at 100%, even if you do nothing with Timberwolf.

So, I think that the filesystem change the behavior of Timberwolf drastically.

Right now I'm using it with the following compination:

libpixman (RC2)
licairo (RC2)
libsqlite (RC1)

It works nice on website appearance, the flickering of the pointer over a text is removed, the menu appears right, the bookmarks doesn't work (SFS0)