TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Feature Request: Manual Refresh of external calendar feeds

70 点作者 baptou12将近 9 年前

19 条评论

kazinator将近 9 年前
Google doesn&#x27;t care that the Picassa system&#x27;s servers are used for bouncing spam. The spam arrives with a from-envelope address of &quot;&lt;random-id&gt;@photos-server.bounces.google.com&quot;. This has been going on for years and reported to Google repeatedly. They don&#x27;t give a damn.<p>I bet you my e-mail server has caught this recently. Let&#x27;s see:<p><pre><code> # zgrep photos &#x2F;var&#x2F;log&#x2F;exim4&#x2F;rejectlog* &#x2F;var&#x2F;log&#x2F;exim4&#x2F;rejectlog.17.gz:2016-07-24 04:34:41 H=mail-qk0-f201.google.com [209.85.220.201] F=&lt;3y6eUVwYUADANRSTQeNRSTQe.kkPQeeM.ebMOQ@photos-server.bounces.google.com&gt; rejected RCPT &lt;ada-mp1-request@kylheku.com&gt;: Too many components in domain name [... snip, a number of hits going back to May ... ] </code></pre> There we go: the most recent spam attempt was on July 24, 2016. Someone tried to use Picassa to spam my ADA MP-1 mailing list.<p>So <i>that&#x27;s</i> how I&#x27;m catching this stuff now: my rule against too many components in the sender domain is taking care of it, currently, before anything more specific.<p>Here is one 2012-dated discussion about this:<p><a href="https:&#x2F;&#x2F;productforums.google.com&#x2F;forum&#x2F;#!topic&#x2F;gmail&#x2F;bQd_kZlscFE" rel="nofollow">https:&#x2F;&#x2F;productforums.google.com&#x2F;forum&#x2F;#!topic&#x2F;gmail&#x2F;bQd_kZl...</a><p>It goes back before that, though, to at least 2010.
AdmiralAsshat将近 9 年前
So, much fun as it is to bash Google, this <i>is</i> a feature request. They&#x27;re not obligated to implement a free enhancement on any sort of timetable.<p>This isn&#x27;t like when Google actually broke the telephony in the Nexus 4 and then finally closed the issue with a middle finger: <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;android&#x2F;issues&#x2F;detail?id=82949" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;android&#x2F;issues&#x2F;detail?id=82949</a>
jjnoakes将近 9 年前
You get what you pay for.<p>My calendar on my phone routinely forgets to remind me, even though clearly the entry says &quot;remind me 1 hour before&quot; and other events with the same reminders work fine.<p>Are there any good calendar hosting companies where I could pay a few $$ a month for decent features, bug fixes, and service?
评论 #12255469 未加载
评论 #12255701 未加载
评论 #12255672 未加载
评论 #12255501 未加载
评论 #12255505 未加载
评论 #12255565 未加载
评论 #12255607 未加载
评论 #12255517 未加载
评论 #12255675 未加载
评论 #12255507 未加载
评论 #12255508 未加载
scholia将近 9 年前
How can this not get fixed after 10 years? You&#x27;d have to assume that googlers use their own Calendar, so why aren&#x27;t they out with pitchforks to incentivize the programmers? Do the in-house Calendar feeds get refreshed every hour or so?
评论 #12255523 未加载
评论 #12255485 未加载
评论 #12255581 未加载
simonsarris将近 9 年前
Reminds me of what&#x27;s going on right now in Chrome:<p><a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=608016#c53" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=608016...</a>
评论 #12255513 未加载
评论 #12255560 未加载
评论 #12255556 未加载
评论 #12255588 未加载
评论 #12255572 未加载
评论 #12255570 未加载
评论 #12255604 未加载
评论 #12255819 未加载
评论 #12255528 未加载
评论 #12255592 未加载
评论 #12255524 未加载
apatters将近 9 年前
My mind was blown when I discovered this little gem recently:<p><a href="http:&#x2F;&#x2F;www.computerhope.com&#x2F;unix&#x2F;ucalande.htm" rel="nofollow">http:&#x2F;&#x2F;www.computerhope.com&#x2F;unix&#x2F;ucalande.htm</a><p>Place a text file at ~&#x2F;.calendar&#x2F;calendar with one event per row, containing the date and the title separated by a tab. Type calendar and you&#x27;ll get a list of what&#x27;s coming up in the next few days. You&#x27;re done.<p>Being a venerable UNIX utility there are of course a variety of options (switch to view X days in the future, support for including external calendars, support for recurrence, etc.). Weirdly, it lacks any concept of start and end time, but this is easy enough to simply include in your appointment&#x27;s title. And no free&#x2F;busy or special sharing mechanism (though you could certainly compose your calendar of several files and expose them on a web server easily enough).<p>It&#x27;s not about to replace a full-blown calendar app for power users, but if you&#x27;re the type of person who has a fairly light meeting schedule and spends a lot of time in a terminal... I was immediately done with all other calendar software and consequently all the problems of said software when I stumbled across this thing.
评论 #12256106 未加载
rietta将近 9 年前
It&#x27;s the cult of the API.<p>I have personal experience with this. Because of the lack of reliable iCal sync, a project I worked on had to spend over a week and a half of developer hours implementing, troubleshooting, and maintaining Google Calendar API integration for our users. It&#x27;s the source of no shortage of pain for this app as it is a sideline feature, but has just enough demand that Google integration cannot be dropped.<p>Google doesn&#x27;t want to support iCal because they want to have everyone use their API.
评论 #12255699 未加载
thinkpad20将近 9 年前
Github has a similar thing, a issue which has been open for over three years and has received innumerable upvotes[0] with essentially no official response as far as I can tell.<p>[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;isaacs&#x2F;github&#x2F;issues&#x2F;18" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;isaacs&#x2F;github&#x2F;issues&#x2F;18</a>
tranv94将近 9 年前
&quot;I hope this can be resolved soon...&quot;- dawnjc79 4&#x2F;17&#x2F;12<p>poor guy
baptou12将近 9 年前
I was just wondering why a feature as simple as this one with lots of demands is still not implemented (or rejected). (6 years !!)
评论 #12255386 未加载
mark-r将近 9 年前
Google is all about scale, and caring doesn&#x27;t scale. This is part of their DNA.<p>This might seem like a flippant comment, but it explains a lot of the observations I&#x27;ve made of Google over the years.
raverbashing将近 9 年前
Another funny Google problem. Backup via adb has been broken since 1.0.32. Nobody cares <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;android&#x2F;issues&#x2F;detail?id=208337" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;android&#x2F;issues&#x2F;detail?id=208337</a>
smhg将近 9 年前
As someone who builds a scheduling product which offers an iCalendar feed for Google Calendar (among others), I have to face this issue on a weekly basis.<p>The most plausible explanation I came up with (and what I tell my users) is that Calendar is maintained by a small team in Switzerland for which this isn&#x27;t a priority. I don&#x27;t blame anyone, if true. It might not be easy to fix with little resources.<p>The fact that some feeds sync faster than others (Facebook events) and syncs speed up as time passes, makes for a weird case.<p>Outlook.com or iCloud&#x2F;iCal sync properly. One of those offer a way out for my users if critical.
jeffrand将近 9 年前
I think Google cares, but they&#x27;re not communicating it very well. I would hesitate before building a feature that might kick off a relatively complicated process with a lot of external factors whenever a user wants. It seems very complicated and without much positive benefit for the average user.
leephillips将近 9 年前
Is this just a problem when subscribing to calendars published through Google? In other words, if I host an iCal calendar on my own server, will subscribers see changes immediately when they refresh their Google Calendar client?
TheLarch将近 9 年前
They&#x27;d have a lot more clout if they were customers.
therealmarv将近 9 年前
hey, other google users which are volunteers are answering all your questions. You are not supposed to talk directly to Google! ;)
usmannk将近 9 年前
Was this hidden from the front page?
sctb将近 9 年前
The previous title, “Google just don&#x27;t care” violates the guidelines by being editorialized. Please use the original title unless it&#x27;s misleading or clickbait.<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html</a>
评论 #12255972 未加载