Holiday inn express redwood city ca

Greenwood, IN

2011.08.01 01:29 GreenwoodIN Greenwood, IN

/GreenwoodIN is an subreddit for the city of Greenwood, IN and events relating to the city and surrounding areas.
[link]


2011.11.05 01:49 neobchod Owensboro, KY's premiere reddit presence!

Consider this a loose info dump for anything happening in or around Owensboro.
[link]


2012.11.30 00:44 boynedmaster Hoarders

A private subreddit for persons struggling with hoarding disorder and the associated shame, so that they can work on their recovery and support each other in a safe online environment. This sub does NOT exist as an echo chamber for hoarders who aren't interested in recovery. Please let's avoid any judgment or shaming of other Redditors who struggle with hoarding. Offensive, oppressive and shitty behavior will not be tolerated.
[link]


2023.06.09 16:51 EchoJobs Bear Robotics is hiring Senior Robotics Software Engineer, Robot Behavior USD 120k-215k Redwood City, CA [C++ Python]

Bear Robotics is hiring Senior Robotics Software Engineer, Robot Behavior USD 120k-215k Redwood City, CA [C++ Python] submitted by EchoJobs to rustjob [link] [comments]


2023.06.09 16:46 Atreus528_ Una joven se tiró desde el séptimo piso del hotel Holiday Inn Express que está sobre Reforma 222 la noche de ayer en la CDMX. Según testigos, estuvo más de 15 minutos trepada en un barandal pero nadie hizo nada para detenerla.

submitted by Atreus528_ to mexico [link] [comments]


2023.06.09 15:47 TheIcebergRealtor Mayor says St. John's in early talks with Uber to improve downtown safety

https://www.cbc.ca/news/canada/newfoundland-labradostjohns-downtown-safety-coalition-1.6869526
submitted by TheIcebergRealtor to newfoundland [link] [comments]


2023.06.09 15:01 EchoJobs Bear Robotics is hiring Senior Software Engineer, Machine Learning - Perception USD 120k-215k Redwood City, CA [Deep Learning Python TensorFlow OpenCV Spark Kafka Hadoop Machine Learning Keras PyTorch NumPy Pandas Streaming]

Bear Robotics is hiring Senior Software Engineer, Machine Learning - Perception USD 120k-215k Redwood City, CA [Deep Learning Python TensorFlow OpenCV Spark Kafka Hadoop Machine Learning Keras PyTorch NumPy Pandas Streaming] submitted by EchoJobs to ReactJSJobs [link] [comments]


2023.06.09 14:31 EchoJobs Bear Robotics is hiring Senior Software Engineer, Machine Learning - Perception USD 120k-215k Redwood City, CA [Deep Learning Python TensorFlow OpenCV Spark Kafka Hadoop Machine Learning Keras PyTorch NumPy Pandas Streaming]

Bear Robotics is hiring Senior Software Engineer, Machine Learning - Perception USD 120k-215k Redwood City, CA [Deep Learning Python TensorFlow OpenCV Spark Kafka Hadoop Machine Learning Keras PyTorch NumPy Pandas Streaming] submitted by EchoJobs to golangjob [link] [comments]


2023.06.09 13:32 wardXn 35 day solo itinerary check across western Honshu, Shikoku, Osaka/Kyoto, Kanazawa and Tokyo

Hello, I would like to seek fellow redditors opinions, input and recommendation on how I could better finetune my itinerary better. There's only so much I can think of, and plan as an individual, but with everyone's input and comments I can further refine and enhance the travel experience before I set foot into Japan. Do forgive me in advance for the theorycrafting wall of text.
I know it may be difficult to review the itinerary, so to make the review easier I have broken the itinerary down into specific sub-groups e.g. Shikoku, Kinki etc. Specific questions that I have are bolded.
Thank you in advance for taking your time to provide your opinions!
-------------
Baseline information

Specific goals/objective:
  1. Experience Shikoku in autumn (specifically the views at Iya Valley) and in other prefectures (thus making nature sightseeing more of a priority this time round)
  2. Experience Kanazawa for anime stuff
  3. Experience the Shimanami Kaido in full (including any sightseeing spots in between the 6 island chains)
  4. Bonus - try as many sightseeing trains as possible.
  5. Bonus - if weather, time and schedule permits, try skiing as an option in Nagano.
  6. Bonus - stay in as many onsen ryokans as possible, without breaking the bank.

Locked-in prefectures [i.e. I will definitely go to those prefectures no matter what]:
  1. Shikoku (as per above objective)
  2. Hiroshima (because its on the opposite end of the Shimanami Kaido)
  3. Kanazawa (for anime related reason)
  4. Tokyo (that is my starting and end point so it has to be included by default)
All other prefectures are basically float i.e. I am open to consider dropping said itinerary for something else based on your suggestion that aligns with my preferences/interest. Most of the other locations I added are prefectures that are often next to each other, or well-connected (apart from the initial Tokyo Kagawa jump via Sunrise Seto/Shinkansen).

Wait-list prefectures (prefectures that I want to go, but I don’t think I can realistically fit in without dropping other locations):
  1. Snow skiing at Nagano (depending on how cooperative the weather is in early-ish December (would 2 days be sufficient?))
  2. Ehime, Kochi expansion [spend 1-3 more days]
  3. Izu Peninsula (~2 days, via Saphir Odoriko)
  4. Nagoya + lower Nagano (Kiso Valley) (~3 days)
  5. Ishikawa expansion [1 extra day at Kaga]
I am open to dropping a few days in Tokyo/Osaka etc to make that trade off [currently kept 3 days free for further development]. Alternatively, if the planning can be better optimized based on your inputs I might be able to do one of those without compromising on the base set. I would like to hear your opinion on what locations you would drop in the itinerary to make time for one of the above.

General planning philosophy:
  1. My itineary adopts a breadth approach (cover as much area as I can humanely possible without rushing/touch-and-go) as opposed to depth (i.e. spending much more time within Shikoku than what I allocated); though I would be open to considering more days at selected locations if you have strong recommendations. My thought is to experience how different autumn is at various parts of the country (if possible), and maybe winter too (to a certain degree).
  2. Due to the nature of my travel, I note that luggage logistics is a critical consideration when moving between prefectures; my thought is to park that luggage at the next hotel as quickly as possible so that I can free myself for sightseeing within the vicinity, or leave the luggage at the hotel after I check out until I am ready to travel to the next location. I will need to send (quite a fair bit of) emails to the hotels to confirm on this prior to booking.
  3. I will attempt to minimize transit time between prefectures to no more than 2~3 hours a day to avoid having excessively long transport days (except the initial Tokyo Kagawa jump).
  4. Because of the long trip, I will also need to factor a bit of downtime at night for administrative stuff (e.g. catching up a little bit on work, laundry etc).
---------
Shikoku (~7 days)
Specific thoughts while planning:
  1. I will need to exploit Limited Express trains as much as possible to minimize downtime between the 4 prefectures. Fortunately, for the most part these train frequencies are almost hourly, thus missing one train isnt too deadly consequence-wise.
  2. The transfer between Kochi and Ehime [Matsuyama] is oddly quicker via express bus as opposed to trains (!)
  3. For Kochi, my opinion is that it is best explored on car instead of public transport [it’s a really wide prefecture]; I feel that 1 day may not do it justice, but it is probably adequate for exploring the city centre as a whole.
  4. There's a fair bit of uncertainties while planning this leg so I would deeply appreciate any advice you may have.
  5. This current iteration is unable to weave in the Shikoku Mannaka Sennen Monogatari sightseeing train [四国まんなか千年ものがたり] ; if you people think its something not to be missed do let me know and I will reshuffle my timetable as such.
Day 0: Tokyo Kagawa (Sunrise Seto) [Saturday, 11 Nov]
Day 1: Kagawa (Takamatsu) [Sunday, 12 Nov]
Day 2: Kagawa (Kotohira) Tokushima (Iya Valley) [Monday, 13 Nov]

Day 3: Tokushima (Iya Valley) [Tuesday, 14 Nov]
[Post-research note: I realized that there is NO public transport to Mount Tsurugi on a weekday. I will have to rent a taxi direct to Mount Tsurugi, make the 'climb', then thereafter take the taxi down to the other attractions. I am inclined to just go full hog on the private taxi and rent it (almost the whole day, probably 7~8 hours for 4300yen/hour) to save the trouble.
Otherwise, I will need to hike downhill which can be rather rough since its just a single lane road (looking at nearly 10++ km) so I think it wise not to penny pinch in the interest of both time and safety.]
Spend the day at Iya Valley.

Day 4: Tokushima (Iya Valley) Kochi (Kochi) [Wednesday, 15 Nov]

Day 5: Kochi (Kochi) Ehime (Imabari) [Thursday, 16 Nov]

Day 6: Ehime (Matsuyama / Imabari) [Friday, 17 Nov]
Day 7: Ehime (Imabari) Hiroshima (Shinamani Kaido) [Saturday, 18 Nov]
I am of the opinion that 1 day in Shimanami Kaido is adequate if I attempt just the main route which is about 80km [as a test run, I did 70km and finished it within 6-7 hours with lunch breaks included]. For now I will plan for two full days, however should I truncate it down to one day later, I will add an extra day to either explore Matsuyama or Okayama.

--------
Hiroshima + Yamaguchi (~4 days)
Specific thoughts while planning:
  1. Onomichi is a pretty good base to jump to Okayama to explore Okayama, Kurashiki or Tomonoura with the Shinkansen accessibility, but it is impossible to cover them all within a single day. If I finish the Shimanami Kaido within a single day or finish it early on the second day, I will have that extra time to visit those.
  2. There's another sightseeing train etSETOra from Onomichi to Hiroshima but it only operates on Monday/Friday/Saturday/Sunday. For now the schedule could fit the train timetable pretty nicely.
  3. Would anyone suggest visiting Miyajima in the morning or in the evening? This would help me determine the order for the Kintaikyo Bridge/Miyajima day trip. Watching the sunset at either destination is pretty good in my books.

Day 8: Hiroshima (Shinamani Kaido Onomichi) [Sunday, 19 Nov]
Ideally reach Onomichi just around lunch or earlier. Chill for the rest of the day, and if I'm still up for it, explore Onomichi, including but not limited to:
Retire at a guesthouse/hotel near JR Onomichi that I have forwarded the luggage to.

Day 9: Hiroshima (Onomichi, Takehara+Kure OR Tomonoura OR Okayama) Downtown Hiroshima) [Monday, 20 Nov]

Day 10: Hiroshima (Downtown Hiroshima) [Tuesday, 21 Nov]
Spend the day surveying Hiroshima proper.

Day 11: Hiroshima (with a day trip to Yamaguchi) [Wednesday, 22 Nov]
--------
Shimane + Tottori (4 days)
Specific thoughts while planning:
  1. Matsue becomes the main jump point for Shimane just because of the subsidized highway bus from Hiroshima, and ease of access towards Tottori later. There's no direct train between Hiroshima and Izumo/Matsue (!).
  2. Tottori is really wide size-wise, to the point that it feels more efficient to have two separate hotels in two nights (Kurayoshi/Misasa Onsen + downtown Tottori) rather than one hotel for two nights (i.e. downtown Tottori). Could be just me making excuses to get into an onsen ryokan however.
  3. Is there anything interesting at Yonago (Tottori) that I should take note of? Based on my initial survey nothing in particular pops up (other than the Tottori Prefectural Flower Park).
  4. Skipping Tottori Castle since it doesn’t seem to be interesting at first glance. Any other interesting things to at Tottori downtown (or nearby)?

Day 12: Hiroshima Shimane (Matsue) [Thursday, 23 Nov]

Day 13: Shimane (Izumo / Matsue) [Friday, 24 Nov]

Day 14: Shimane (Matsue) Tottori (Kurayoshi) [Saturday, 25 Nov]

Day 15: Tottori (Kurayoshi Tottori) [Sunday, 26 Nov]

-----------
Hyogo, Kyoto, Osaka , Nara, Mie (10 days)
Specific thoughts while planning:
  1. Kinosaki Onsen is intentionally designed to be a slow-paced leg to recover [and also to make time to enjoy the onsens].
  2. The limited express train between Kinosaki Onsen and Osaka stops by Himeji thus I thought of resting a night there instead of doing day trips via Osaka.
  3. Osaka itinerary does look sparse but that is in large part because I have already visited most of them in the past. Nevertheless, I would like to experience how different it is in autumn compared to summer [based on those few destinations that I loved going previously].
  4. I have kept one float day to decompress, OR shift to any of the other prefectures (TBC).
  5. There are (multiple) special limited express train by Kintetsu; they're not covered by JR pass but nevertheless I would love to ride on those as an experience. The Kintetsu pass covers the basic fare only but based on my preliminary cost estimate, it is still worth getting it.
  6. Is it feasible to compress Himeji and Kobe to a single day?
  7. The itineraries for Osaka, Kyoto, Nara and Mie are flexible since they're literally beside one another - makes it particularly easy to shift around base on ground situation.

Day 16: Tottori (Tottori) Hyogo (Kinosaki Onsen) [Monday, 27 Nov]

Day 17: Hyogo (Kinosaki Onsen + Northern Kyoto (Amanohashidate) day trip) [Tuesday, 28 Nov]
Day 18: Hyogo (Kinosaki Onsen Himeji) [Wednesday, 29 Nov]
Retire at Himeji for the night.
Day 19: Hyogo (Himeji Kobe) Osaka (Dotonburi) [Thursday, 30 Nov]
Day trip to Kobe, before continuing further down to Osaka.
Day 20: Osaka [Friday, 1 Dec]
Osaka Nostalgia (acid) trip, speedrun edition: revisiting places that I want to go again
Day 21: Osaka (Nara day trip) [Saturday, 2 Dec]
Spend a day in Nara.
Day 22: Osaka (Mie day trip) [Sunday, 3 Dec]
Day trip to Mie.
Day 23: Osaka ('north' Kyoto day trip) [Monday, 4 Dec]
(north) Kyoto day trip.
Whichever choice, return back to Osaka for the night. Look out for Kyoto-specific food such as Yudofu, Saba Sushi, Warabi Mochi, Nishin Soba (にしんそば) etc.
Day 24: Osaka ('south' Kyoto day trip) [Tuesday, 5 Dec]
(south) Kyoto day trip edition (mainly Uji and Fushimi).
Head back to Osaka and retire for the night. Consider doing any other night activities in Osaka if time, and body permits.
Day 25: Osaka (wildcard) [Wednesday, 6 Dec]
Spare day to do whatever I feel like doing OR reallocate this to another prefecture. Intentionally left blank for later planning
-------------
Kanazawa, Gifu+ (4 days)
Specific thoughts while planning:
  1. Is it likely for the skiing season to open around 9~10 December at Shiga Kogen or Nozawa Onsen? Would very much like to try skiing for fun, but am uncertain if the snow condition would be satisfactory by then. Some of the skiing website indicates that these two destinations are usually the first to open. I would like to seek advise on this if possible [never skiied before].
  2. As an additional question to point 1, is 2 days adequate just to get a flavor on skiing?
  3. Kanazawa is a pretty solid jump point to Shirakawago/Takayama via express buses (~1 to 2 hour one way).
  4. My initial planning considered going to Kurobe Gorge (Toyama) but apparently the railways are closed from December onwards. Please correct me if I am mistaken.
  5. Another sightseeing train in Kanazawa that I can fit in nicely in my current plans (花嫁のれん), runs on Mon/Fri/Sat/Sun.
Day 26: Osaka Ishikawa (Kanazawa (Kanazawa cityside)) [Thursday, 7 Dec]
Any outstanding spots not completed today, to be rolled over to the next 2 days (if possible).

Day 27: Ishikawa (Kanazawa cityside) / Gifu (Shirakawago, Takayama) [Friday, 8 Dec]

Day 28: Ishikawa (Kanazawa cityside / outskirts) [Saturday, 9 Dec]
Side trip to Wakura Onsen / Nanao for anime-related sightseeing. (Insomanics after Class, Hanasaku Iroha)
Day 29: Ishikawa (wildcard) [Sunday, 10 Dec]
Spare day to do whatever I feel like doing OR reallocate this to another prefecture. Intentionally left blank for later planning
--------------
Tokyo (~6 days)
Specific thoughts while planning:
  1. Specific interest to target: anime/vtuber stuff, music (piano in particular), bookstores etc.
  2. This is the point in time I should go ham on souvenier purchase if I have not done so. I'll probably get an extra cardboard box or duffel bag to lug with me to the airport to store extra stuff.
  3. Would like to seek recommendation on where I should set my base for the 5~6 days here. For now I am planning to pit at Ginza, subject to availability and cost. My thought is that as long as its along the Yamanote line everything rolls I suppose.
  4. Hard pass on Golden Gai on the Shunjuku leg (I do not drink).
  5. There's way too many to list in terms of what I would like to do in Tokyo, but I have listed items that are of particular interest to me first within the available time frame. If you have strong opinions on specific locations do let me know.
Day 30: Ishikawa (Kanazawa) Tokyo (Ginza) [Monday, 11 Dec]
Day 31: Tokyo (Shibuya, Shinjuku and Nakano) [Tuesday, 12 Dec]
Explore ('west') Tokyo, namely Shibuya, Shinjuku and Nakano.
Day 32: Tokyo (Akibahara, Asakusa and Sky Tree) [Wednesday, 13 Dec]
Day 33: Tokyo (Kamakura day trip OR Ikebukuro) [Thursday, 14 Dec]
EITHER take a day trip Kamakura, OR explore northern Tokyo (Ikebukuro)
Kamakura leg:
Tokyo (Ikebukuro leg):
Day 34: Tokyo (wildcard) [Friday, 15 Dec]
Spare day to do whatever I feel like doing OR reallocate this to another prefecture. Intentionally left blank for later planning

Day 35: Tokyo Home [Saturday, 16 Dec]
END
---------------------
If you're still reading up to this point, here's my own personal ramblings/thoughts on JR pass usage:
I have thought of two ways of doing this for the first 21 days:
a. easy-mode : just get 21 days JR global pass before the price hike at 60450 yen, OR b. hard-mode: get a 7 day JR global pass (to cover the NEX fees, the basic fee on the Sunrise Seto to Shikoku, as well as limited express trains within Shikoku) (29650) + 5 days for JR Okayama Hiroshima Yamaguchi Area Pass (15000) + 4 days for JR Sanin Okayama Area Pass + 5 days for JR Kansai Wide Area Pass (10000) for a total of 59230.
The initial conclusion was to go with option A since that reduces the administrative burden, but I realized the individual passes do have its own perk which truimphs over the global JR pass. For instance, the Sanin Okayama Area Pass provides a (minor) discount for the Adachi Museum of Art; the Kansai Wide Pass covers the Kyotango route between Kinosaki Onsen and Amanohashidate which the global JR pass does not cover, JR Okayama Hiroshima Yamaguchi Area Pass covers JR buses within Hiroshima for free, therefore I am inclined to go with the hell option (option B) as it stands.
For the remaining 14 days, I could also get the global 14 day JR pass at 47250 yen but it is not worth it at all, because I will be relying largely on Kintetsu for the Osaka/Kyoto/Nara/Mie leg which the JR pass most certainly does not cover.
So all in all, there's quite little incentive to get the global JR pass after I worked out my schedule, apart from the initial 7 days for the Sunrise Seto jump which the All Shikoku Pass will not cover.
Through the hodge-podge of multiple area passes, it works out to around 102890 yen for the whole trip of 35 days, contrast with 107700 yen for a 21 + 14 global JR pass. While there's a minor cost saving doing the hard way which sweetens the deal, the additional minor perks associated with the area passes sells it for me, as I would had to pay more out of pocket to cover non-JR pass buses/rails and such which would add up to much greater cost than I would had anticipated. Also, if I did this trip post-price hike in October, the calculus becomes a no-brainer: avoid the global JR pass like the plague.
-----
Thank you very much for your opinions, suggestions and advice in advance!
submitted by wardXn to JapanTravel [link] [comments]


2023.06.09 10:21 EchoJobs SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python]

SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python] submitted by EchoJobs to joblead [link] [comments]


2023.06.09 10:21 EchoJobs SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python]

SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python] submitted by EchoJobs to echojobs [link] [comments]


2023.06.09 10:20 EchoJobs SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python]

SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python] submitted by EchoJobs to CodingJobs [link] [comments]


2023.06.09 10:20 EchoJobs SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python]

SnorkelAI is hiring Software Engineer - Infra USD 155k-215k Redwood City, CA [Machine Learning Docker Kubernetes Python] submitted by EchoJobs to pythonjob [link] [comments]


2023.06.09 07:30 EchoJobs Prove (formerly Payfone) is hiring Senior Software Engineer USD 160k-190k Redwood City, CA [Go]

Prove (formerly Payfone) is hiring Senior Software Engineer USD 160k-190k Redwood City, CA [Go] submitted by EchoJobs to golangjob [link] [comments]


2023.06.09 03:50 EchoJobs Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go]

Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go] submitted by EchoJobs to golangjob [link] [comments]


2023.06.09 03:00 EchoJobs Bear Robotics is hiring Software Engineer – Embedded System USD 120k-215k Redwood City, CA [C++ Bash Docker Python]

Bear Robotics is hiring Software Engineer – Embedded System USD 120k-215k Redwood City, CA [C++ Bash Docker Python] submitted by EchoJobs to pythonjob [link] [comments]


2023.06.09 02:30 EchoJobs Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go]

Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go] submitted by EchoJobs to pythonjob [link] [comments]


2023.06.09 01:45 awjeezrickyaknow Madonna - The Immaculate Collection (1990) Round 6 of 16

You do not cherish Cherish
OONKA CHACKA OONKA CHACKA OONKA OONKA OONKA CHACKA! Get ready for Awesome Mix Vol. 1 from Guardians of the Galaxy!

VOTE

SONGS IN

  • Holiday
  • Lucky Star
  • Borderline
  • Like a Virgin
  • Material Girl
  • Into the Groove
  • Live to Tell
  • Papa Don't Preach
  • Open Your Heart
  • Like a Prayer
  • Express Yourself
  • Vogue

SONGS OUT

Rank Song Votes Against Percentage Runner-up
13 Cherish 6/19 31.6%
14 Crazy for You 11/20 55% 15% (3/20)
15 La Isla Bonita 6/19 31.6% 26.3% (5/19)
16 Justify My Love 6/20 30% 25% (5/20)
17 Rescue Me 12/19 63.2% 10.5% (2/19)

ALBUM INFO

RYM
WIKI
GENIUS

STREAM

APPLE MUSIC
SPOTIFY
JOIN OUR DISCORD
submitted by awjeezrickyaknow to music_survivor [link] [comments]


2023.06.09 01:40 EchoJobs Bear Robotics is hiring Software Engineer – System USD 120k-215k Redwood City, CA [C++ Bash Docker Python]

Bear Robotics is hiring Software Engineer – System USD 120k-215k Redwood City, CA [C++ Bash Docker Python] submitted by EchoJobs to pythonjob [link] [comments]


2023.06.09 01:10 EchoJobs Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go]

Bear Robotics is hiring Software Engineer Intern Redwood City, CA [Machine Learning C++ Java JavaScript Python Go] submitted by EchoJobs to JavaScriptJob [link] [comments]


2023.06.09 00:20 Strict_Dragonfruit32 My (24f) bf (26m) is about to move back to his hometown (different state) after graduating school, says he loves me but doesn’t even want to try a LDR out of fear of resenting each other. What should I do?

Me and my boyfriend have been dating for a little bit over a year (officially) but were seeing each other for 6 months before we made it official. He expressed to me recently that he is doubtful we will make it through a ldr simply due to the stress and hardships that a ldr can bring. He says he has thought about a future of us moving in together if we ever made it through a ldr, but knows it would be a miracle if we ever even worked through it.
He has always been hesitant about ldr through our whole relationship, but I thought things may be different because we truly fell hard for each other over the last year. Things haven’t always been easy, but we have always known he was going to move after he graduated and knowing this I always thought he and I would work through being in a future ldr for at most 1-2 years after he moved.
We have been talking about it for the last 5 days and he says he doesn’t want to do a ldr because he knows it’s going to be a lot of long and difficult days regardless of being in a relationship or not (financial stress, finding a job, passing qualifying exams for work, etc) but I have always seen us working through our hardships together and growing together as a couple and individually while in this ldr. He says we will only be seeing eachother 8-12 times a year and he just wants to be able to hug and touch me on the hard days and be there for support in person and it’s hard to do that over a screen (even with all of the technology we have today…?) I even wrote down a calendar of dates for the rest of the year for us planned out so the idea of us talking about visiting each other had concrete dates, plans, and ideas.
I’ve stated to him many times that I know ldr are not easy, but he is all worth it to me, and we talked about me moving closer to him in a year from now. He still says it won’t work. He does tell he’s scared for the future and doesn’t know what lies ahead from him especially in the next year. I tell him as long as we have each other, we can figure everything else out but I just think he assumes it’s going to turn ugly since we won’t be living in the same city.
He has said he is open to rekindling the relationship in the future once he has more of his life together, but with me living in a different state I just don’t see that being a logical solution, especially if we rekindled to have a ldr. I also know that this is a “what if”, and I really don’t want to be strung along.
What should I do? These last few days I have been heartbroken. I’ve never imagined us breaking up or him not being there on holidays or important moments. I just love him so much and he is my best friend and other half.
If you love something, set it free. If it comes back to you, it was always yours, right?
submitted by Strict_Dragonfruit32 to LDR [link] [comments]


2023.06.08 20:32 Tomolo1997 📢 Suki is hiring a Associate Product Manager!

Company: Suki
Location: Redwood City, CA 📍.
Date Posted: June 08, 2023 📅.
Apply & Description 👉 https://bestaijobs.com/associate-product-manager-suki/10468
submitted by Tomolo1997 to BestAIJobs [link] [comments]


2023.06.08 19:21 EchoJobs Moloco is hiring Android SDK Engineer USD 133k-200k Redwood City, CA US [Android Machine Learning Kotlin Java React Unity Go]

Moloco is hiring Android SDK Engineer USD 133k-200k Redwood City, CA US [Android Machine Learning Kotlin Java React Unity Go] submitted by EchoJobs to ReactJSJobs [link] [comments]


2023.06.08 19:18 iamthatis 📣 Apollo will close down on June 30th. Reddit’s recent decisions and actions have unfortunately made it impossible for Apollo to continue. Thank you so, so much for all the support over the years. ❤️

Hey all,
It's been an amazing run thanks to all of you.
Eight years ago, I posted in the Apple subreddit about a Reddit app I was looking for beta testers for, and my life completely changed that day. I just finished university and an internship at Apple, and wanted to build a Reddit client of my own: a premier, customizable, well-designed Reddit app for iPhone. This fortunately resonated with people immediately, and it's been my full time job ever since.
Today's a much sadder post than that initial one eight years ago. June 30th will be Apollo's last day.
I've talked to a lot of people, and come to terms with this over the last weeks as talks with Reddit have deteriorated to an ugly point, and in the interest of transparency with the community, I wanted to talk about how I arrived at this decision, and if you have any questions at the end, I'm more than happy to answer. This post will be long as I have a lot of topics to cover.
Please note that I recorded all my calls with Reddit, so my statements are not based on memory, but the recorded statements by Reddit over the course of the year. One-party consent recording is legal in my country of Canada. Also I won't be naming names, that's not important and I don't want to doxx people.

What happened initially?

On April 18th, Reddit announced changes that would be coming to the API, namely that the API is moving to a paid model for third-party apps. Shortly thereafter we received phone calls, however the price (the key element in an announcement to move to a paid API) was notably missing, with the intent to follow up with it in 2-4 weeks.
The information they did provide however was: we will be moving to a paid API as it's not tenable for Reddit to pay for third-party apps indefinitely (understandable, agreed), so they're looking to do equitable pricing based in reality. They mentioned that they were not looking to be like Twitter, which has API pricing so high it was publicly ridiculed.
I was excited to hear these statements, as I agree that long-term Reddit footing the bill for third-party apps is not tenable, and with a paid arrangement there's a great possibility for developing a more concrete relationship with Reddit, with better API support for users. I think this optimism came across in my first post about the calls with Reddit.

When did they announce pricing?

Six weeks later, they called to discuss pricing. I quickly put together a small app where I could input the prices and it would output monthly/yearly cost, cost for free users, paid users, etc. so I'd be able to process the information immediately.
The price they gave was $0.24 for 1,000 API calls. I quickly inputted this in my app, and saw that it was not far off Twitter's outstandingly high API prices, at $12,000, and with my current usage would cost almost $2 million dollars per month, or over $20 million per year. That is not an exaggeration, that is just multiplying the 7 billion requests Apollo made last month by the price per request. Could I potentially get that number down? Absolutely given some time, but it's illustrative of the large cost that Apollo would be charged.

Why do you say Reddit's pricing is "too high"? By what metric?

Reddit's promise was that the pricing would be equitable and based in reality. The reality that they themselves have posted data about over the years is as follows (copy-pasted from my previous post):
Less than 2 years ago they said they crossed $100M in quarterly revenue for the first time ever, if we assume despite the economic downturn that they've managed to do that every single quarter now, and for your best quarter, you've doubled it to $200M. Let's also be generous and go far, far above industry estimates and say you made another $50M in Reddit Premium subscriptions. That's $550M in revenue per year, let's say an even $600M. In 2019, they said they hit 430 million monthly active users, and to also be generous, let's say they haven't added a single active user since then (if we do revenue-per-user calculations, the more users, the less revenue each user would contribute). So at generous estimates of $600M and 430M monthly active users, that's $1.40 per user per year, or $0.12 monthly. These own numbers they've given are also seemingly inline with industry estimates as well.
Apollo's price would be approximately $2.50 per month per user, with Reddit's indicated cost being approximately $0.12 per their own numbers.
A 20x increase does not seem "based in reality" to me.

Why doesn't Reddit just buy Apollo and other third-party apps?

This was a very common comment across the topics: "If Apollo has an apparent opportunity cost of $20 million per year, why not just buy them and other third-party apps, as they did with Alien Blue?"
I believe it's a fair question. If these apps apparently cost so much, an easy solution that would likely make everyone happy would be to simply buy these apps out. So I brought that up to them during a call on May 31st where I was suggesting a variety of potential solutions.

Bizarre allegations by Reddit of Apollo "blackmailing" and "threatening" Reddit

About 24 hours after that call with Reddit, I received this odd message on Mastodon:
"Can you please comment publicly about the internal Reddit claim that you tried to “blackmail” them for a $10,000,000 payout to “stay quiet”?"
Then yesterday, moderators told me they were on a call with CEO Steve Huffman (spez), and he said the following per their transcript:
Steve: "Apollo threatened us, said they’ll “make it easy” if Reddit gave them $10 million."
Steve: "This guy behind the scenes is coercing us. He's threatening us."
Wow. Because my memory is that you didn't take it as a threat, and you even apologized profusely when you admitted you misheard it. It's very easy to take a single line and make it look bad by removing all the rest of the context, so let's look at the full context.
I can only assume you didn't realize I was recording the call, because there's no way you'd be so blatantly lying if you did.
As said, a common suggestion across the many threads on this topic was "If third-party apps are costing Reddit so much money, why don't they just buy them out like they did Alien Blue?" That was the point I brought up. If running Apollo as it stands now would cost you $20 million yearly as you quote, I suggested you cut a check to me to end Apollo. I said I'd even do it for half that or six months worth: $10 million, what a deal!
The bizarre thing is - initially - on the call you interpreted that as a threat. Even giving you the benefit of the doubt that maybe my phrasing was confusing, I asked for you to elaborate on how you found what I said to be a threat, because I was incredibly confused how you interpreted it that way. You responded that I said "Hey, if you want this to go away…" Which is not at all what I said, so I reiterated that I said "If you want to Apollo to go quiet, as in it's quite loud in terms of API usage".
What did you then say?
Me: "I said 'If you want Apollo to go quiet'. Like in terms of- I would say it's quite loud in terms of its API usage."
Reddit: "Oh. Go quiet as in that. Okay, got it. Got it. Sorry."
Reddit: "That's a complete misinterpretation on my end. I apologize. I apologize immediately."
The admission that you mistook me, and the four subsequent apologies led me to believe that you acknowledged you mistook me and you were apologetic. The fact that you're pretending none of this happened (or was recorded), and instead espousing a different reality where instead of apologizing for taking it as a threat, you're instead going the complete opposite direction and saying "He threatened us!" is so low I almost don't believe it.
But again, I've recorded all my calls with you just in case you tried something like this.
Transcript of this part of the call: https://gist.github.com/christianselig/fda7e8bc5a25aec9824f915e6a5c7014
Audio of this part of the call: http://christianselig.com/apollo-end/reddit-third-call-may-31-end.m4a
(If you take issue with the call being recorded please remember that I'm in Canada and so long as one participant in the call (me) consents to being recorded, it's legal. If anyone would like the recording of the full call, I'm happy to provide.)
I bring this up for two reasons:

What is an API or an API request anyway?

Some people are confused about this situation and don't understand what an API is. An API (Application Programming Interface) is just a way for an app to talk to a website. As an analogy, pretend Reddit is a bouncer. Historically, you can ask Reddit "Could I have the comments for this post?" or "Can you list the posts in AskReddit?". Those would be one API request each, and Reddit would respond with the corresponding data.
Everything you do on Reddit is an API request. Upvoting, downvoting, commenting, loading posts, loading subreddits, checking for new messages, blocking users, filtering subreddits, etc.
The situation is changing so that for each API request you make, there's a portion of a penny charged to the developer of that app. I think that is very reasonable, provided, well, that the price they charge is reasonable.

Claims that Apollo is "inefficient"

Another common claim by Reddit is that Apollo is inherently inefficient, using on average 345 requests per day per user, while some other apps use 100. I'd like to use some numbers to illustrate why I think this is very unfairly framing it.
Up until a week ago, the stated Reddit API rate limits that apps were asked to operate within was 60 requests per minute per user. That works out to a total of 86,400 per day. Reddit stated that Apollo uses 345 requests per user per day on average, which is also in line with my findings. Thats 0.4% of the limit Reddit was previously imposing, which I would say is quite efficient.
As an analogy (can you tell I love analogies?), to scale the numbers, if I was to borrow my friend’s car and he said “Please don’t drive it more than 864 miles” and I returned the car with 3.4 miles driven, I think he’d be pretty happy with my low use. The fact that a different friend one week only used 1 mile is really cool, but I don't think either person is "inefficient".
That being said, if Reddit would like to see Apollo make further optimizations to get its existing number lower, I’m genuinely more than happy to do so! However the 30 day limit they’ve given me after announcing the pricing to when I will start getting charged significant amounts of money is not enough time to deal with rewriting large parts of my app to lower total requests, while also changing the payment model, transitioning users, and ensuring this is all properly tested and gets through app review.
Further, Reddit themselves said to me that the majority of the cost isn't the server, it's the opportunity cost per user, so the focus on 100 versus 345 calls, rather than the cost per user, doesn't sound genuine. At the very least providing even a bit more time to lower usage to their new targets would be feasible if they've historically provided it, and it's not the majority of the costs anyway.
Me: "Because I assume the majority of it isn't server costs. I assume the majority is the opportunity cost per user."
Reddit: "Exactly."

Why not just increase the price of Apollo?

One option many have suggested is to simply increase the price of Apollo to offset costs. The issue here is that Apollo has approximately 50,000 yearly subscribers at the moment. On average they paid $10/year many months ago, a price I chose based on operating costs I had at the time (server fees, icon design, having a part-time server engineer). Those users are owed service as they already prepaid for a year, but starting July 1st will (in the best case scenario) cost an additional $1/month each in Reddit fees. That's $50,000 in sudden monthly fee that will start incurring in 30 days.
So you see, even if I increase the price for new subscribers, I still have those many users to contend with. If I wait until their subscription expires, slowly month after month there will be less of them. First month $50,000, second month maybe $45,000, then $40,000, etc. until everything has expired, amounting to hundreds of thousands of dollars. It would be cheaper to simply refund users.
I hope you can recognize how that's an enormous amount of money to suddenly start incurring with 30 days notice. Even if I added 12,000 new subscribers at $5/month (an enormous feat given the short notice), after Apple's fees that would just be enough to break even.
Going from a free API for 8 years to suddenly incurring massive costs is not something I can feasibly make work with only 30 days. That's a lot of users to migrate, plans to create, things to test, and to get through app review, and it's just not economically feasible. It's much cheaper for me to simply shut down.

So what is the REAL issue you're having?

Hopefully that illustrates why, even more than the large price associated with the API, the 30 day timeline between when the pricing was announced and developers will be charged is a far, far, far bigger issue and not one I can overcome. Much more time would be needed to overhaul the payment model in my app, transition existing users from existing plans, test the changes, and have users update to the new version.
As a comparison, when Apple bought Dark Sky and announced a shut down of their API, knowing that this API was at the core of many businesses, they provided 18 months before the API would be turned off. When the 18 months came, they ultimately extended it another 12 months, resulting in a total transition period of 30 months. While I'm not asking for that much, Reddit's in comparison is 30 days.

Reddit says you won't get your first bill until August 1st, though!

The issue is the size of the bill, not when it will arrive. Significant, significant charges for the API will start building up with 30 days notice on July 1st, the fact that the bill for those charges being 30 days from then is not important. If you hear that your electricity bill is going up 1,000x and the company tells you, "Don't worry, the bill only comes at the end of the month", I hope you understand how that isn't comforting.

What would be a good price/timeline?

I hope I explained above why the 30 day time limit is the true issue. However in a perfect world I think lowering the price by half and providing a three month transition period to the paid API would make the transition feasible for more developers, myself included. These concessions seem minor and reasonable in the face of the changes.

I thought you said Reddit would be flexible on the timeline?

That was my understanding as well based on what they said on a call on May 4th:
Reddit: "If there's an entity who's like 'Hey I'm showing really good progress', you know trying to like we're trying to get a contract in place, we're trying to do all that type of stuff, I don't think you're going to see us be like, you know, like overly aggressive on that timeline. And I feel pretty confident about that point by the way based on conversations I've heard internally."
However when asking about more time, such as a 90 day transition period to make the changes, they said:
Reddit: "On the 90-day transition, remember that billing doesn't kick in until July 1. So you won't see your first bill from July until the beginning of August, and it won’t be due until the end of August (It’s net 30 day billing). You do, however, have to sign an agreement to get paid level access on July 1."

Did you explicitly ask Reddit for more time?

Yes, my last email to them (including Steve) said:
In terms of timeline, what concerns me most is the short nature of it before I start incurring costs. I have a large amount of users at price points that I won’t be able to afford to support with 30 days notice. For instance, users who subscribed for a year for $10 six months ago when I had no idea any of this was coming, amounts to $0.83 per month or $0.58 after Apple’s cut. Even if I’m able to decrease my API usage down to the number in your charts, that still puts me in the red for everyone of those users for awhile with no recourse. A situation like this is one that is legitimately making me legitimately leaning toward shutting down the app, but one that I could salvage if given more time to transition from the free API to the paid API.
In prior calls you mentioned that provided I kept communicating and progress was being made, the timeline wasn’t an absolute.
Is that still the case, or is it now the case that the date is set in stone?
That was a week ago and I've yet to receive any further contact from Reddit.

Isn't this your fault for building a service reliant on someone else?

To a certain extent, yes. However, I was assured this year by Reddit not even that long ago that no changes were planned to be made to the API Apollo uses, and I've made decisions about how to monetize my business based on what Reddit has said.
January 26, 2023
Reddit: "So I would expect no change, certainly not in the short to medium term. And we're talking like order of years."
Another portion of the call:
January 26, 2023
Reddit: "There's not gonna be any change on it. There's no plans to, there's no plans to touch it right now in 2023.
Me: "Fair enough."
Reddit: "And if we do touch it, we're going to be improving it in some way."

Will you build a competitor? Move to one of the existing alternatives?

I've received so many messages of kind people offering to work with me to build a competitor to Reddit, and while I'm very flattered, that's not something I'm interested in doing. I'm a product guy, I like building fun apps for people to use, and I'm just not personally interested in something more managerial.
These last several months have also been incredibly exhausting and mentally draining, I don't have it in me to engage in something so enormous.

Will you sell Apollo?

Probably not. Maybe if the perfect buyer came along who thought they could turn Apollo into something cool and sustainable, but I'd rather the app just die if it would go to a company that would turn something I worked really hard on into something that would ruin its legacy.
To be clear: I am not threatening anyone in the previous paragraph.

Reddit states that the Twitter comparison is unfair

Reddit stated on the first call that they don't want to be like Twitter:
Reddit: "I think one thing that we have tried to be very, very, very intentional about is we are not Elon, we're not trying to be that, we're not trying to go down that same path. [...] We are trying to do is just use usage-based pricing, that will hopefully be very transparent to you, and very clear to you. Or we're not trying to go down the same path that you may have seen some of our other peers go down."
They now state that the comparison of how close their pricing comes to Twitter is an unfair one, and that when they said that above, they were apparently referring not to the pricing, but to the decision Twitter made to ban third-party apps at a rule level, not a pricing level.
I think regardless of whatever their intent/meaning behind the comparison to Twitter was, the result is the same: the pricing will kill third-party apps, just as Twitter did.
I said this to Reddit, and they responded that they don't think Twitter's pricing is unreasonable, and that if anything, if Twitter reversed the rule about third-party apps, they would probably increase the prices as well.
Just to be clear about how wrong and out of touch that is, without naming names, a formerly very, very high up person at Twitter messaged me on Twitter and said:
"The Reddit api moves are crazy. I’m not sure what choices you have but to move to another network. [...] That pricing is designed to prevent apps like yours forevermore."
So to be clear, even this person thinks this pricing is unreasonable. I do too.

Have you talked to CEO Steve Huffman about any of this?

I requested a call to talk to Steve about some suggestions I had, his response was "Sorry, no. You can give name-redacted a ping if you want."
I've then emailed that person (same person I've been talking to for months) suggestions approximately one week ago about how Apollo could survive this, and I've yet to receive a response.

Do I support the protest/Reddit blackout?

Abundantly. Unlike other social media companies like Facebook and Twitter who pay their moderators as employees, Reddit relies on volunteers to do the hard work for free. I completely understand that when tools they take to do their volunteer, important job are taken away, there is anger and frustration there. While I haven't personally mobilized anyone to participate in the blackout out of fear of retaliation from Reddit, the last thing I want is for that to feel like I don't support the folks speaking up. I wholeheartedly do.
It's been a horrible week, and the kindness Redditors and moderators and communities have shown Apollo and other third-party apps has genuinely made it much more bearable and I am genuinely so appreciative.
I am, admittedly, doubtful Reddit wants to listen to folks anymore so I don't see it having an effect.

Your initial post in April sounded quite optimistic. Are you dumb?

In hindsight, kinda yeah. Many of the other developers and folks I talked to were much less optimistic than I was, but I legitimately had great interactions with Reddit for many years prior to last week (they were kind, communicative, gave me heads up of changes), so when they said they were aiming to have pricing that would be fair and based in reality, I honestly believed them. That was foolish of me in hindsight, and maybe could have had a different outcome if I was more aggressive in the beginning. Sorry. /canadian
(And to be clear, they did indeed say this. They used the word "substantive" and I wanted to make sure we had the same definition of something "having a firm basis in reality and therefore important, meaningful, or considerable")
Reddit: "That's exactly right. And I think, thankfully, the word is exactly the right one. It's going to have a firm basis in reality. I also just looked it up. We're going to try to be as transparent as we can."

Reddit claims they've reached out to developers who were bad users of the API, was Apollo contacted?

On May 31st Reddit posted a chart of large excess usage by some unlabeled API clients, and stated: "We reached out to the most impactful large scale applications in order to work out terms for access above our default rate limits via an enterprise tier."
To be clear, Apollo was never contacted, and I've been told from someone internally that Apollo is indeed not one of the unlabeled API clients.
The only time that Apollo was reached out to by Reddit in any capacity about usage was late last year when we received an email about a 6 minute period where Apollo's server API usage increased by 35% before lowering again. Despite 35% for 6 minutes being a comparatively small blip (the above post references clients that are over by 500000%), we responded within 2 minutes. We offered to jump on a call with Reddit engineers if they needed an answer ASAP, identified the issue within several hours and Reddit thanked us for the fast investigation.
Full email transcript: https://gist.github.com/christianselig/6c71608cf617d2f881cd2849325494c1

Claims that Apollo has made no attempt to be a good user of the API

On the call with moderators, Steve Huffman said:
Steve: "I don't use the app, so I'll give you the best answer I can -- he does scraping so that he can deliver notifications faster, but has done NO EFFORT to be a good citizen of the internet."
First off, Apollo does no scraping, it's purely through authenticated calls to the API and has checks in place to ensure it stays within Reddit's API rate limits. I've open sourced the server code to show this.
Secondly, to say we have made no effort is categorically false. I have so many emails where I've reached out to Reddit expressing concerns about and bugs inefficiencies in the API, or ideas on how to improve things, or significant Reddit bugs that made things hard on us. When Reddit has had questions for us, as discussed above, we immediately jumped into action to get an answer as quickly as possible.
Here's an email of me giving a heads up to Reddit of IP address changes on our server:
Me: "With the new change it'll be maybe like, one IP address. This is all obviously still within the API rate limits as the requests are from individual user accounts that have signed in. Again, long story short the result will be more optimized if anything, I just wanted to give a heads up and ensure that it'd be okay if Reddit suddenly saw the server go from a bunch of different IP addresses to a single one which might cause some confusion if I didn't give a heads up."
Me wanting to make sure we were doing everything as best as we could:
Me: "Everything is going well, we just had a few questions about best practices making sure we’re following any suggestions your team has. Is there any way we could poke someone on your team with a few questions we’ve been having and have a tiny back and forth? We were just seeing some elevated response times, and just thought it would be great if we could maybe describe what we’re doing and see if anything seems off/suboptimal."
Me reporting to Reddit that the API has a serious bug in recording rate limits:
Me: "We obviously respect the rate limit headers and if a user comes close to approaching it (within 50 requests of the 600 every 10 minutes limit) we stop their requests until the refresh period occurs. However we're seeing some users have very, very weird rate limit headers. Things like "requests remaining: 0, requests made: 17,483, reset: 598 seconds left" which indicates they've somehow made over 17 thousand requests in two seconds which seems hard to believe."
Me suggesting to Reddit improvements that could help improve efficiency of notification API calls:
Me: "So like little stuff like that, where even if there's a streaming client or some way to minimize the calls there, I think it would help us both out enormously."
Further, when making suggestions to your own employees, they themselves have expressed concern about how terrible the public API is:
Call on January 26, 2023
Reddit: "I cannot tell you how painful it is to use our API. [...] The API needs to change. Like it's just unusable. I am surprised that you're able to build a functional app on it to be honest."

Claims that third-party apps are not interested in talking

Steve: "Why not work with the third party apps? Their existence is not a priority for us. We don't use them. I don't use them. It's a part of our traffic but not a lot, and it's a lot of work on our side to keep them alive. If I have to choose where to put our effort, we're going to focus internally. I'm kind of open to it, but I haven't – and I can't convince you, but I don't get the sense that they want to work with us either."
I'm genuinely not sure where Steve has got the impression that I don't want to work with him. Despite reaching out multiple times and him declining to talk, I've stated multiple times on calls, literally saying the words "I definitely still want to talk".
Reddit: "What I'm hearing is like, Yeah, great. We have this disagreement on pricing methodology, etc. But any feasible number that we get to, any number that's even in, the zip code of what we're sharing with you is unfeasible from your perspective financially. So it's like arguing around the edges of that price thing is like, it just won't make any sense to you. And I presume also just given the NSFW stuff and the removal of ads that makes it even more trickier." Me: Yeah. I mean, to be very clear, I'm not saying I'm walking away from the negotiation table and taking my basketball and going home and just gonna kick up a storm. That's not my intention at all. I definitely still want to talk. I'm not asking you to lower the price by a hundred times or something. I don't think – depending on what you mean by zip code – I don't think I'm so unreasonable that I'm requiring you to bend over backwards here."
I've also emailed Steve and the other contact directly stating that I'm interested in talking, and including ideas for how we could come to a solution:
Me: "I understand where Reddit's coming from in this. A free API, while appreciated, is not tenable for you especially heading into an IPO, and my only goal here is to come to a solution where we both feel understood. I also hear you that killing third-party clients isn't actually the goal, and in that spirit have been working on how to address your concerns from my end: [...]"
I don't know how you can say I'm not interested in talking when you haven't my most recent email in a week. To say it once more, I was very interested in talking.
On the other side of things, per the transcript, Steve and the other admin on the call don't even know when the discussions with third-party apps began.
Steve: "When did we start talking with them?"
AnAbsurdlyAngryGoose: "What month did you first start?"
Steve: "FlyingLaserTurtles? Do you remember? April or May of this year."
FlyingLaserTurtles: "Maybe late March? But yes."

Claims that Reddit has been talking to developers for months talking about these changes

Steve: "We've been in contact with third party apps for MONTHS, talking about these coming changes."
When you announce that the API will be charging developers, the most important portion of that conversation is what will be charged, which was not available for almost two months after the initial call. From the time developers were told the price, to the time developers will be subject to the price, is 30 days, not "months". Months would have been very helpful, in fact.

What about existing subscriptions?

I've been talking to my rep at Apple, and over the next few weeks my plan is to release something similar to what Tweetbot did (Paul has been incredibly helpful in all of this) where folks can decide if they want a pro-rated refund on any existing time left in their subscription as Apollo will not be able to afford to continue it, or they can decline the refund if they're feeling kind and have enjoyed their time with Apollo.
For the curious, refunding all existing subscriptions by my estimates will cost me about $250,000.

A nice send off at WWDC

Apollo got mentioned a few times during Apple's 2023 WWDC keynote, even by Craig Federighi himself, and even during the Vision Pro announcement showing Apollo as one of the existing apps compatible with the headset (I'm sorry I won't be able to see that happen).
I was lucky enough to be there in person and it felt incredible. Some folks asked if there was any deeper meaning behind that, and while that would be cool, in all reality these things are so well produced that they've been done for a while now, so I'm sure it's just a coincidence, even if it's a really cool one.

Extra icons

A funny amount of people have reached out wondering about all the extra monthly icons I had queued up for Apollo. I love them, was so excited for them, and I'll make them available immediately for the short time left, but if you're curious here's a screenshot of all of them: https://christianselig.com/apollo-end/remaining-icons.png
We ended up with well over 100 custom icons created by incredibly talented designers, and I'm really sorry to those designers who didn't get to see their work launched in the app (to be clear, don't worry, I paid them all – there isn't some bs "exposure" agreement – but it's fun to have your icon launch and I feel bad!)

When is Apollo's last day? What will happen?

In order to avoid incurring charges I will delete Apollo's API token on the evening of June 30th PST. Until that point, Apollo should continue to operate as it has, but after that date attempts to connect to the Reddit API will fail.
I will put up an explainer in the app prior to that which will go live at that date. I will also provide a tool to export any local data you have in Apollo, such as filters or favorites.

Thank you

I want to thank a lot of people who have made this last week bearable. First and foremost, the communities, Redditors, and moderators who have reached out in support of third-party apps, making Reddit's gaslighting a lot more bearable in making me feel like at least someone was understanding me and in my corner.
My girlfriend's been absolutely incredible and supportive. This year was our 10th anniversary, and Monday was her 30th birthday. We're down in California for Apple's WWDC and had a bunch of things planned to do for her birthday afterward, and I feel terrible that we're flying home early to deal with all of this instead of making her 30th special. I'll make it up to her.
André Medeiros worked on the Apollo server component with me for the last two years, and it's been an absolute joy to work with a professional who knows so much on that side of things.
The iOS developer community has been unbelievably kind to me over the past several weeks, I've spent the last week with many of them, even staying at an Airbnb with a bunch of them (they ordered me pizza as I wrote this post!), and I've got so many hugs and condolences haha. Specifically want to thank Paul Haddad of Tweetbot/Tapbots/Ivory, Ryan Jones, Brian Mueller, Curtis Herbert, André Medeiros, Quinn Nelson, Paul Hudson, Majd Taby, Ryan McLeod, Phill Ryu, Larry Hryb, Charlie Chapman, Mustafa Yusuf, Adrian Eves, Devin Davies, Jordan Morgan, Yariv Nassim, Will Sigmon, Barry Hershman, Joe Rossignol, Michael Simmons, Joe Fabisevich, my family, and so, so many more.
Also want to thank everyone at Apple who have gone out of their way to be incredibly kind here (I don't know if I'm allowed to name names but you know who you are).

I'll be fine

No bullshit, I'll be fine. Through pure chance last year I spun off my silly Pixel Pals idea into a separate app, and that actually makes good revenue on the side. I also have savings. Recently (like last week) my city had its worst wildfires in history with over 100 homes destroyed. That's brutal, losing an app is sad, but it's been helpful to me to recognize how much worse it could be just literally down the street from me.
Honestly. Apollo had an incredible run, I met the coolest people, by my last count talked with folks over 15,000 times in our subreddit about Apollo, and raised over $80,000 for my local animal shelter through Apollo. I feel incredibly fortunate.
I think I'll rewatch Ted Lasso though.

Supporting my work

I build a second app called Pixel Pals that I spun off from Apollo that's thankfully done pretty well and I'll be spending more time on going forward. If you like the idea of digital pets it's a really fun app to check out. https://pixelpa.ls

Media

If any media/press folks have any questions, please shoot me an email rather than messaging me on Reddit, I missed a few last week because my inbox was blowing up. My email is [email protected]

AMA

I think I covered everything, but if there's any questions feel free to ask and I'll do my best to answer!
In the event that this post is taken down or you want to link somewhere else, it's also available at https://apolloapp.io
Thanks for everything over these last 8 years,
- Christian
EDIT: Few updates:

Tip Jar

Per many requests I also added back the Tip Jar to the top of settings if you update the app. It's incredibly kind of anyone to even think of that, but please feel no pressure. On one hand I don't want it to feel like I'm profiteering off this event, but on the other hand I imagine people understand it would have been much more profitable/ideal if the app were able to just continue to exist in the first place so that would be really bad profiteering, and the refund thing genuinely is daunting.

What if…

I've seen a lot of questions along the lines of: "What if Reddit gives you a deadline extension because of this post and posts by other developers?" and that's something I truly would have loved for them to have made an effort to communicate earlier. You can't give developers 30 days between when the pricing is announced and when they will start incurring charges, and also wait a week (25% of the time we're given) between replying to emails without so much as a "we hear you're concerned about the short timeline and looking into what we can do". In conjunction with your previous emails, it just appears like you've stopped any desire to communicate with developers, in a period where we have a serious, expensive deadline looming with not that much time to wind down our apps.
And I also just know if I sent another email saying "I'm going to post tomorrow that Apollo is shutting down unless you do something about the timeline", it would be construed as a threat.
Even more than that, Reddit's behavior has been so appalling that for any developer I've talked to it's completely erased the indication that they even want us around.
submitted by iamthatis to apolloapp [link] [comments]


2023.06.08 19:00 EchoJobs Moloco is hiring Senior Software Engineer - Data Platform USD 163k-244k Redwood City, CA US [Java Go Python AWS Spark Machine Learning GCP]

Moloco is hiring Senior Software Engineer - Data Platform USD 163k-244k Redwood City, CA US [Java Go Python AWS Spark Machine Learning GCP] submitted by EchoJobs to golangjob [link] [comments]