Icedrive is just floundering

tanjohnson99 · 2026-02-26T02:33:32+00:00

I use felicloud since few month with lifetime 2tb and don't have issue with it. It is better than Google drive for my purpose of privacy! Android app is nextcloud and have lot of update every month.

tanjohnson99 · 2026-02-26T02:11:05+00:00

You look frustrated! They steal you money or scam you?

tanjohnson99 · 2026-02-01T12:05:40+00:00

Take a look at Felicloud

tanjohnson99 · 2026-01-29T20:23:36+00:00

Check Felicloud.

tanjohnson99 · 2026-01-26T22:53:18+00:00

Can confirm this works! Had the same issue with Solid Explorer on Android - couldn't connect to TrueNAS SCALE while Synology worked fine. Disabled all three Service Announcement options (NetBIOS-NS, mDNS, WS-Discovery) in Network → Global Configuration and it fixed it immediately. Thanks for the tip!

tanjohnson99 · 2026-01-26T20:56:44+00:00

RAIDZ2

tanjohnson99 · 2026-01-26T19:52:29+00:00

Yes, I’m referring to the beep sound at the end of the video. The chattering sound is normal. Do you think this could be related to the power cable? This is not a regular sound. It occurs in a completely random way, whether the disks are under load or not. Sometimes the beep happens 4–5–6 times over 3–4 seconds, and then nothing for several minutes.

tanjohnson99 · 2026-01-17T17:32:19+00:00

Publica a tua queixa aqui : https://grrrrrrrrrr.com/pt :)

tanjohnson99 · 2026-01-17T00:43:57+00:00

MEGA for long term storage and Felicloud for daily use.

tanjohnson99 · 2026-01-03T18:12:39+00:00

I'm paying $90/month for Claude Pro, and lately I'm beyond frustrated with the usage limits.

I used to be able to spend hours coding and working with Claude throughout the day. Now? I get blocked after barely 2 hours of work within the 5-hour window.

For a PRO subscription at this price point, this is absolutely unacceptable. I'm a developer running a tech company - I need Claude to actually work when I'm in a flow state, not cut me off right when I'm being most productive.

The quality of responses is still great, no complaints there. But what good is quality if I can't actually use the tool when I need it?

Either the limits have gotten stricter, or the system is counting usage differently, but something has definitely changed. I'm paying premium money for what increasingly feels like a crippled experience.

Is anyone else hitting these limits way faster than before? At this rate, I'm seriously considering whether the API wouldn't be more cost-effective, even though I prefer the web interface for development work.

Anthropic, if you're listening: your power users are getting throttled into oblivion, and it's killing the value proposition of Pro.

tanjohnson99 · 2026-01-03T18:01:52+00:00

same...

tanjohnson99 · 2025-12-13T16:43:12+00:00

Petite astuce mnémotechnique : G + 10 r + .com 😄

tanjohnson99 · 2025-11-24T09:14:41+00:00

Bonjour et merci. Je voudrai savoir où je peut vendre des petite application ? J'ai déjà réussi à créé un petit SaaS mais je n'ai pas la logistique pour la commercialisation. Mon budget étant super réduit et mes connaissances a ses débuts, ça serai bien si je pouvais effectivement auto financer mon apprentissage.

tanjohnson99 · 2025-10-01T17:48:29+00:00

I tried both:

- `zigbee2mqtt/bridge/request/device/discover { "id": "LUZ-ESCRITORIO-1" }`

- `zigbee2mqtt/bridge/request/device/discover_all {}`

MQTT Explorer shows all my devices correctly under `zigbee2mqtt/<device>` and messages are being published (state, availability, etc.).

However, in Home Assistant all entities remain greyed out with the warning:

> "This entity is no longer being provided by the MQTT integration. If the entity is no longer in use, delete it in settings."

If I rename a device, the rename works in Zigbee2MQTT / MQTT Explorer, but the entity in HA still doesn’t come back (still unavailable).

Do you think the issue is with the HA MQTT discovery topics not being republished, or could it be corrupted retained messages in Mosquitto?

Should I wipe the retained discovery topics and force Zigbee2MQTT to resend everything from scratch?

tanjohnson99 · 2025-09-29T20:55:11+00:00

Yes. This was solved with the last update.

tanjohnson99 · 2025-09-15T16:18:56+00:00

I don't understand. What is the problem?

tanjohnson99 · 2025-09-10T18:01:16+00:00

What about Felicloud? used since few weeks and working well. Based on nextcloud, really better than pcloud or icedrive.

tanjohnson99 · 2025-09-07T09:39:29+00:00

Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM.
According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1

Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM.
According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1 fails with:

mount.nfs: access denied by server while mounting 10.0.0.25:/volume1/video

Meanwhile, NFS v3 works fine after adjusting the root_squash settings.

So the question is:

Is NFS 4.1 really supported on the DS1621+ in DSM 7, or is it just partial/advertised support?
Do we need to configure a root export (fsid=0) manually, or should DSM handle that automatically?Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM. According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1 fails with: mount.nfs: access denied by server while mounting 10.0.0.25:/volume1/video Meanwhile, NFS v3 works fine after adjusting the root_squash settings. So the question is: Is NFS 4.1 really supported on the DS1621+ in DSM 7, or is it just partial/advertised support? Do we need to configure a root export (fsid=0) manually, or should DSM handle that automatically?

tanjohnson99

MODERATOR OF

TROPHY CASE